3 added 1 character in body
source | link

After rebooting a couple of times, I decided to try my luck launching "VMware Fusion" before invoking the vagrant up command.

It indeed work;works; vagrant up does not start VMWare fusion, and so, you have to be running it for vagrant up to be able to deploy a VM.

Ultimately, the error message could be more elucidative.

After rebooting a couple of times, I decided to try my luck launching "VMware Fusion" before invoking the vagrant up command.

It indeed work; vagrant up does not start VMWare fusion, and so, you have to be running it for vagrant up to be able to deploy a VM.

Ultimately, the error message could be more elucidative.

After rebooting a couple of times, I decided to try my luck launching "VMware Fusion" before invoking the vagrant up command.

It indeed works; vagrant up does not start VMWare fusion, and so, you have to be running it for vagrant up to be able to deploy a VM.

Ultimately, the error message could be more elucidative.

2 deleted 2 characters in body
source | link

After rebooting a couple of times, I decided to try my luck launching "VMware Fusion" before invoking the vagrant up command.

It indeed work; vagrant up does not start VMWare fusion, and so, you have to beenbe running it for vagrant up to be able to deploy a VM.

Ultimately, the error message could be more elucidative.

After rebooting a couple of times, I decided to try my luck launching "VMware Fusion" before invoking the vagrant up command.

It indeed work; vagrant up does not start VMWare fusion, and so, you have to been running it for vagrant up to be able to deploy a VM.

Ultimately, the error message could be more elucidative.

After rebooting a couple of times, I decided to try my luck launching "VMware Fusion" before invoking the vagrant up command.

It indeed work; vagrant up does not start VMWare fusion, and so, you have to be running it for vagrant up to be able to deploy a VM.

Ultimately, the error message could be more elucidative.

1
source | link

After rebooting a couple of times, I decided to try my luck launching "VMware Fusion" before invoking the vagrant up command.

It indeed work; vagrant up does not start VMWare fusion, and so, you have to been running it for vagrant up to be able to deploy a VM.

Ultimately, the error message could be more elucidative.