Created
October 25, 2016 09:04
-
-
Save aidygus/c5336700ecc2aa899a45c39bbaadc64c to your computer and use it in GitHub Desktop.
Console output
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
$ vagrant destroy -f && vagrant up --provider vmware_workstation | |
Diskname or some other argument is missing. | |
==> provisioner: VM not created. Moving on... | |
==> sqlserver: Stopping the VMware VM... | |
==> sqlserver: Deleting the VM... | |
Diskname or some other argument is missing. | |
Diskname or some other argument is missing. | |
Diskname or some other argument is missing. | |
Bringing machine 'sqlserver' up with 'vmware_workstation' provider... | |
Bringing machine 'provisioner' up with 'vmware_workstation' provider... | |
==> sqlserver: Cloning VMware VM: '2012R2'. This can take some time... | |
==> sqlserver: Checking if box '2012R2' is up to date... | |
==> sqlserver: Verifying vmnet devices are healthy... | |
==> sqlserver: Preparing network adapters... | |
==> sqlserver: Fixed port collision for 5985 => 55985. Now on port 2201. | |
==> sqlserver: Fixed port collision for 5986 => 55986. Now on port 2202. | |
==> sqlserver: Fixed port collision for 22 => 2222. Now on port 2203. | |
==> sqlserver: Starting the VMware VM... | |
Vagrant timed out while trying to start the VMware machine. This | |
error is caused by VMware never successfully starting the machine. | |
This can often be fixed by simply retrying. If the error persists, | |
please verify that VMware is functional. This is not a Vagrant | |
issue. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment