CODEWITHSUNDEEP
virtual-machinevmwarevagrantvmware-fusion
Jack7890
Jack7890

Reputation: 1371

Indecipherable VMware/Vagrant error message

My company uses Vagrant within VMware for development. Everyone else (10+ people) has the setup running smoothly, but I've run into a confounding problem that none of us can solve.

After adding a vagrant box with vagrant box add sgvm http://files.vagrantup.com/precise64_vmware.box I try to start vagrant with vagrant up seatgeek --provider=vmware_fusion. This throws this error:

An error occurred while executing `vmrun`, a utility for controlling
VMware machines. The command and output are below:

Command: ["start", "/Users/jack/Sites/sg/seatgeek-vm/.vagrant/machines/seatgeek/vmware_fusion/f2e2bebf-e1cb-4bc1-862b-9cb957e13065/precise64.vmx", "nogui", {:notify=>[:stdout, :stderr]}]

Stdout: 2014-02-06T09:20:29.661| ServiceImpl_Opener: PID 20276
Error: The operation was canceled

Stderr:

I got in touch with VMware support. They said that they can't support it, but they would confirm that vmrun was working properly. They asked me to run vmrun -T fusion start and verified that the output was expected. Based on this, they said it was a Vagrant problem. I have tried to contact Vagrant support but they have been non-responsive.

Anyone have any idea what might cause this? Or ideas about other things I should investigate?

Upvotes: 5

Views: 5055

Answers (4)

UC57
UC57

Reputation: 459

you may need to change the vm.box name, currently it downloaded the x86 but you need something like arm64. Also after change this, you need to delete the .vagrant directory and then run vagrant up. It should work.

Upvotes: 0

Simon Rose
Simon Rose

Reputation: 421

Another possible source of this error is that the vagrant box may have the wrong architecture. I had unintentionally downloaded an x86 box on my M2 mac, which gave this error. When I switched to using an arm64 box, the VM started correctly.

Upvotes: 2

Mukul Sharma
Mukul Sharma

Reputation: 1

Screenshot

Enabled my gui and found out that the error was coming due to the VMWare version being incompatible with Mac M1.

Upvotes: 0

phs
phs

Reputation: 11061

I saw this when I tried to dial the memory on my vm too high. After a certain limit, fusion doesn't even try. See the memsize line of my block below.

config.vm.provider 'vmware_fusion' do |provider, override|
  # provider.gui = true
  override.vm.box_url = 'http://files.vagrantup.com/precise64_vmware.box'
  provider.vmx['memsize'] = '3072'  # VMware refuses to start for anything larger
  provider.vmx['numvcpus'] = '1'    # http://superuser.com/q/505711/96477
end

Upvotes: 4

Related Questions