I have had the provider specified, but it did not help. I reinstaled vagrant, vbox to no avail. But anyway I gave up and switched off hyperV and set back to VBox completely.
On Tuesday, March 17, 2020 at 4:54:26 PM UTC+1, Jeff Bonhag wrote: > > Hi there, > > Vagrant doesn't require VirtualBox, but if you have Hyper-V and VirtualBox > installed at the same time, it will prioritize VirtualBox over Hyper-V. > This means that running `vagrant up` will try to bring up a > VirtualBox-backed machine when both providers are installed. (Note that you > can request a specific provider like `vagrant up --provider hyperv`). > > It sounds like you may still have a VirtualBox-backed VM on your Windows > machine. Can you please check the output of `vagrant global-status`? > > If you see something like: > > 0eedc3c default virtualbox poweroff C:/Users/vagrant/vbox-test > > then Vagrant is going to keep trying to use VBoxManage to interact with > that VM. I'd suggest that you reinstall VirtualBox, run a `vagrant destroy` > on the VirtualBox-backed machine, and then uninstall VirtualBox again. > > Hope this helps! > > Jeff > > On Tue, Mar 17, 2020 at 5:27 AM zveratko <martin...@gmail.com > <javascript:>> wrote: > >> Does vagrant need VirtualBox to run? >> I have switched to WIN10 and I am forced to run hyperV. I found out that >> VBox will not work with hyperV enabled so I decided to remove it. But now >> I'm getting >> >> Vagrant could not detect VirtualBox! Make sure VirtualBox is properly >> installed. >> Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and >> requires >> this to be available on the PATH. If VirtualBox is installed, please find >> the >> `VBoxManage` binary and add it to the PATH environmental variable. >> >> Why is that? Does vagrant have dependency on VBox even when I am using >> 'hyperv' provider? >> >> -- >> This mailing list is governed under the HashiCorp Community Guidelines - >> https://www.hashicorp.com/community-guidelines.html. Behavior in >> violation of those guidelines may result in your removal from this mailing >> list. >> >> GitHub Issues: https://github.com/mitchellh/vagrant/issues >> IRC: #vagrant on Freenode >> --- >> 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 vagra...@googlegroups.com <javascript:>. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/vagrant-up/6d799979-657b-41d1-ae2e-08d7d2b44021%40googlegroups.com >> >> <https://groups.google.com/d/msgid/vagrant-up/6d799979-657b-41d1-ae2e-08d7d2b44021%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/e3376020-a450-47d9-8033-d43629b6f8e4%40googlegroups.com.
