Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vagrant 1.6.2 tries to use HyperV instead of Virtualbox as before #3896

Closed
alexeyOnGitHub opened this issue May 23, 2014 · 21 comments
Closed

Vagrant 1.6.2 tries to use HyperV instead of Virtualbox as before #3896

alexeyOnGitHub opened this issue May 23, 2014 · 21 comments

Comments

@alexeyOnGitHub
Copy link

@alexeyOnGitHub alexeyOnGitHub commented May 23, 2014

I have a Vagrant setup created couple months ago. it uses Virtualbox provider.
now I installed Vagrant 1.6.2 on a new computer and started it for the first time in the folder where I keep my Vagrant configuration files (provisioning and Vagrantfile): "vagrant up".
for some reason it's trying to use HyperV instead of Virtualbox:

$ vagrant up
Bringing machine 'default' up with 'hyperv' provider...
==> default: Verifying Hyper-V is enabled...

had to stop it using CTRL_C because it seems to be frozen.

I'm using Virtualbox 4.3.12

@mitchellh
Copy link
Member

@mitchellh mitchellh commented May 23, 2014

This is probably due to the VirtualBox bug that was introduced in 4.3.12. 1.6.3 will fix this.

@alexeyOnGitHub
Copy link
Author

@alexeyOnGitHub alexeyOnGitHub commented May 23, 2014

is there a workaround for now?

@mitchellh
Copy link
Member

@mitchellh mitchellh commented May 23, 2014

Yeah, set VBOX_MSI_INSTALL_PATH to the value of VBOX_INSTALL_PATH

@alexeyOnGitHub
Copy link
Author

@alexeyOnGitHub alexeyOnGitHub commented May 23, 2014

I assume you mean environment variable?

$ export VBOX_MSI_INSTALL_PATH="C:\Program Files\Oracle\VirtualBox"
$ vagrant up
Bringing machine 'default' up with 'hyperv' provider...
==> default: Verifying Hyper-V is enabled...

also, once I stop it using CTRL+C, I can't run Vagrant anymore, have to logout each time. don't know which process is stuck...

@mitchellh
Copy link
Member

@mitchellh mitchellh commented May 23, 2014

You reversed each!

@alexeyOnGitHub
Copy link
Author

@alexeyOnGitHub alexeyOnGitHub commented May 23, 2014

ok, this works:
export VBOX_INSTALL_PATH="C:\Program Files\Oracle\VirtualBox"

the original advice sounded a bit ambiguous to me, sorry

@ryanoboril
Copy link

@ryanoboril ryanoboril commented Jun 14, 2014

"also, once I stop it using CTRL+C, I can't run Vagrant anymore, have to logout each time. don't know which process is stuck..."

killing ruby.exe worked for me after using CTRL+C

@UltCombo
Copy link

@UltCombo UltCombo commented Jan 22, 2015

the original advice sounded a bit ambiguous to me, sorry

The usual grammar is SET <var name> TO <value>, so I also understood it the other way around.

Anyway, thanks for help! Setting the VBOX_INSTALL_PATH env var solved the issue for me as well.

@UltCombo
Copy link

@UltCombo UltCombo commented Jan 22, 2015

By the way, I'm using Vagrant 1.7.2 with VirtualBox 4.3.20 and still experienced this issue.
Was this issue actually fixed in Vagrant?

@UltCombo
Copy link

@UltCombo UltCombo commented Jan 22, 2015

Oh, looks like the issue is only reproducible when running vagrant up from msysGit Bash.

@angrychimp
Copy link

@angrychimp angrychimp commented Mar 9, 2015

I'm still seeing this same behavior with a fresh install of Vagrant 1.7.2 and VirtualBox 4.3.22 on Windows 7. I've tried using the standard Windows command prompt, and Cygwin. As with the others above, I'm able to work around the issue using the adjusted environment variable.

Is this expected to be fixed at this point? Or is it possible this is a new bug?

@possibly
Copy link

@possibly possibly commented Mar 14, 2015

@angrychimp me too.

VirtualBox 4.3.24 for Windows hosts x86/amd64 and Vagrant 1.7.2 for Windows 7. I'm using standard Windows cmd.exe. Deleting VBOX_MSI_INSTALL_PATH system variable and setting VBOX_INSTALL_PATH to C:\Program Files\Oracle\VirtualBox solved this issue, as it has with everyone else.

@angrychimp
Copy link

@angrychimp angrychimp commented Mar 19, 2015

@mitchellh - can you please review this issue again and confirm if it should be reopened? Or should a new issue be created?

@jchristman
Copy link

@jchristman jchristman commented Apr 1, 2015

@angrychimp, I had this same problem after:

  1. Installed vagrant for the first time on Windows 7
  2. Installed VirtualBox for the first time (on this machine)

I confirm that VirtualBox still installs with the VBOX_MSI_INSTALL_PATH as of 4.3.26 (released 16 March, 2015). Using the steps provided by @possibly, I renamed the system variable to VBOX_INSTALL_PATH and had no issues thereafter.

@braneof
Copy link

@braneof braneof commented Jan 26, 2016

Just ran into this issue with the latest versions: VirtualBox 5.0.10 and Vagrant 1.8.1. Changing VBOX_MSI_INSTALL_PATH to VBOX_INSTALL_PATH worked, but this is an annoying issue and it's still not fixed.

@uttamanand
Copy link

@uttamanand uttamanand commented Jul 27, 2017

you can give command as -:

vagrant up --provider virtualbox

@apournaras
Copy link

@apournaras apournaras commented Nov 1, 2017

I did delete VBOX_MSI_INSTALL_PATH and created VBOX_INSTALL_PATH and set it to C:\Program Files\Oracle\VirtualBox but I vagrant still tries to use Hyper-v instead of Virtualbox on Windows 8.1. I use vagrant 2.0.0 and virtualbox 5.2.0

@uttamanand
Copy link

@uttamanand uttamanand commented Nov 1, 2017

@apournaras
Copy link

@apournaras apournaras commented Nov 1, 2017

@uttamanand thanks for the help. The problem was that vagrant can use virtualbox version <5.1 while I had the 5.2 version. Now it runs even without the —provider virtualbox

@uttamanand
Copy link

@uttamanand uttamanand commented Nov 1, 2017

@ghost
Copy link

@ghost ghost commented Mar 31, 2020

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.

@hashicorp hashicorp locked and limited conversation to collaborators Mar 31, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants