vmware-vmx does not detect vmplayer version and refuses to clone

[fcerbell]

/home/Jaspersoft/DemoVM/packer $ packer --version
Packer v0.5.2
/home/Jaspersoft/DemoVM/packer $ vmplayer -v
VMware Player 6.0.1 build-1379776
/home/Jaspersoft/DemoVM/packer $ LANG=C time packer build -force -only vmware-vmx demovm.json
vmware-vmx output will be in this color.

==> vmware-vmx: Cloning source VM...
==> vmware-vmx: Deleting output directory...
Build 'vmware-vmx' errored: Cloning is not supported with Player 5. Please use Player 6+.

==> Some builds didn't complete successfully and had errors:
--> vmware-vmx: Cloning is not supported with Player 5. Please use Player 6+.

==> Builds finished but no artifacts were created.
Command exited with non-zero status 1
0.05user 0.02system 0:00.06elapsed 114%CPU (0avgtext+0avgdata 6040maxresident)k
256inputs+0outputs (1major+9838minor)pagefaults 0swaps

[veshi]

I am having this issue on Ubuntu 12.04.4 LTS using Packer v0.6.0 and VMware Player 6.0.3 build-1895310.

Any chance that there is a known work-around?

[tehranian]

I'm seeing this too with Packer v0.6.0 and Workstation 10.0.0 & Workstation 10.0.3 on SLES 11 SP3.

[tehranian]

Here's a link to the debug log, although I didn't find anything useful in it:
https://gist.github.com/tehranian/0371fc6f91cfea704575

[tehranian]

@veshi Hi Adrian,

Do you literally only have Played 6.0.x installed directly, or did you get Player installed by way of having Workstation 10.0.x installed? I have a hunch as to what's happening here...

Dan

[veshi]

I definitely only have Player and VIX installed.
On Jul 9, 2014 6:49 PM, "Dan Tehranian" notifications@github.com wrote:

@veshi https://github.com/veshi Hi Adrian,

Do you literally only have Played 6.0.x installed directly, or did you get
Player installed by way of having Workstation 10.0.x installed? I have a
hunch as to what's happening here...

Dan

—
Reply to this email directly or view it on GitHub
#972 (comment).

[tehranian]

@veshi - Ok so your problem is a bit different than mines AFAICT. Take a look at: https://github.com/mitchellh/packer/tree/master/builder/vmware/common . There's a driver for Player 5 ("drier_player5.go"), but no driver implemented for Player 6. And of course the Clone() method in that Player 5 driver raises the error: https://github.com/mitchellh/packer/blob/master/builder/vmware/common/driver_player5.go#L25

I think my problem is a bit different... I have WS 10 installed (which includes Player 6). For some reason, Packer wants to use this Player 5 driver instead of the WS 10 driver even though I have WS 10 installed.

[tehranian]

Aaah I figured out my issue. I'd never licensed the copy of WS10 on the build slave that this was running on. Adding a license key and re-running got me going.

I figured this out by digging through the driver's Verify() code. Strangely, the workstationCheckLicense() method seems to return/log errors about not being licensed but they never appeared in the output. See: https://github.com/mitchellh/packer/blob/master/builder/vmware/common/driver_workstation_unix.go#L17-L28

My feedback is that the logging around the WS driver selection & verification steps could be better.

[adamenger]

@tehranian thanks for that message, installing the license also fixed my build.

[bivas]

I'm having this issue with Packer 0.7.5 and VMware Player 6.0.3 on Ubuntu Server 14.
I've installed VMware Player bundle without Workstation (with VIX SDK):

$ vmware-vix.bundle --list-products

Product Name         Product Version
==================== ====================
vmware-player        6.0.3.1895310
vmware-vix           1.13.0.1295980

Getting the same Cloning is not supported with VMWare Player version 5. Please use VMWare Player version 6, or greater. when running vmware-vmx builder.

[bhumikajain1234]

Any update on above?
i also installed the below drivers on linux
==================== ====================
vmware-vix 1.17.0.6661328
vmware-player 6.0.1.1379776
but still getting error ,
Build 'vmware-vmx' errored: Cloning is not supported with VMWare Player version 5. Please use VMWare Player version 6, or greater.

please let me know what need to be done to fix this?

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.