"nogui" error Vmware Fusion 6 - cannot start VMs

[Andrew Diller]

I'm getting this nogui error using Vagrant 1.4.3 and now 1.5.4 with vmware Fusion 6.

This is on a Mac w/ 10.9, vmware fusion 6.0.3. These are pretty basic VMs that I'm trying to start.

1.4.3:

========================================

Successfully added box 'puppet-centos6-fusion-64-10' with provider 'vmware_fusion'!

[node1] Cloning VMware VM: 'puppet-centos6-fusion-64-10'. This can take some time...

[node1] Verifying vmnet devices are healthy...

[node1] Preparing network adapters...

[node1] Starting the VMware VM...

An error occurred while executing `vmrun`, a utility for controlling

VMware machines. The command and output are below:

Command: ["start", "/Volumes/fusion/vagrant_home/vagrant-centos-cluster/.vagrant/machines/node1/vmware_fusion/f4330b15-ec7b-49d2-8b00-bfa867e1bcee/centos-64-x64-fusion503.vmx", "nogui", {:notify=>[:stdout, :stderr]}]

Stdout: 2014-05-05T15:37:17.574| ServiceImpl_Opener: PID 32615

Error: Unknown error

===========================================================

1.5.2:

=============================================================

[11:17][dillera@MassivePro:~/fusion/vagrant_home/vagrant-centos-cluster(master)]$ vagrant up

Bringing machine 'node1' up with 'vmware_fusion' provider...

Bringing machine 'node2' up with 'vmware_fusion' provider...

==> node1: Verifying vmnet devices are healthy...

==> node1: Preparing network adapters...

==> node1: Starting the VMware VM...

An error occurred while executing `vmrun`, a utility for controlling

VMware machines. The command and output are below:

Command: ["start", "/Volumes/fusion/vagrant_home/vagrant-centos-cluster/.vagrant/machines/node1/vmware_fusion/f4330b15-ec7b-49d2-8b00-bfa867e1bcee/centos-64-x64-fusion503.vmx", "nogui", {:notify=>[:stdout, :stderr]}]

Stdout: 2014-05-06T11:17:25.131| ServiceImpl_Opener: PID 34196

Error: Unknown error

Stderr: 

===================================================================

[Mitchell Hashimoto]

This "unknown error" is 100% always an issue with VMware itself. It is
unfortunate they don't have a more descriptive error message. One way
to get the real error message to surface is to enable GUI mode. VMware
usually pops up a message telling you what went wrong.

Best,
Mitchell

> --
> You received this message because you are subscribed to the Google Groups
> "Vagrant" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to vagrant-up+...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

[Andrew Diller]

OK, you are, of course, correct.

Setting

v.gui = true

and I see vmware has this error:

Version mismatch with vmmon module: expecting 279.0, got 271.0.

which is answered here:

https://communities.vmware.com/thread/456399

Basically, you need to do this to fix the MacOSx vmmon module...

sudo rm -rf /System/Library/Extensions/vmmon.kext

sudo cp -pR /Applications/VMware\ Fusion.app/Contents/Library/kexts/vmmon.kext /System/Library/Extensions/t

sudo kextunload /System/Library/Extensions/vmmon.kext

sudo kextutil /System/Library/Extensions/vmmon.kext

and the error is resolved.

thx!