Daniele, thanks for the reply! just to confirm:
- I do not have Hyper-V service running on Windows (I checked through control panel-> Turn Windows Features on and off) - I do not have Docker installed - VT-x is not disabled from BIOS Well, everything was working all right until this morning. The crush of vagrant is of no apparent reason. The only suspect to me here, is a Windows update which might have broken something. Since otherwise I did not install/update anything myself in the last few days. Anyways, nothing helped, and eventually I had to destroy the VM, uninstall Oracle Virtual Box, and Vagrant Hashicorp, then installed the two, rebooted the computer, and the error with *vagrant up* was gone. This is an utterly undesirable workaround, as a lot of set-up goes away, and I need to start from the scratch. It would be most helpful, if one can point out - what are the (other) potential causes of the aforementioned error ? - how to fix the error without uninstall/reinstall ? Many thanks, Hayk Other possible causes are: - You have Docker installed (in this case Docker might be the one that enabled the Hyper-V service). - You have VT-x disabled in your machine BIOS (unlikely, but worth a shot if nothing of the above works) On Tuesday, 7 August 2018 11:45:56 UTC+4, [email protected] wrote: > > Hi there, > > From the error you are getting it seems that something is locking access > to VT-Hardware in your machine. > > This often means that you have Hyper-V service enabled in Windows. > If this is the case Hyper-V will lock access to VT resources to avoid > stability/performance issues. > > If you do not need it you can disable the Hyper-V service and see if it > helps but be aware that this will prevent you from running Hyper-V VMs > until you re-enable the service. > > Other possible causes are: > > - You have Docker installed (in this case Docker might be the one that > enabled the Hyper-V service). > - You have VT-x disabled in your machine BIOS (unlikely, but worth a > shot if nothing of the above works) > > Hope this helps. > > Daniele > > -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/f2f0e858-771e-4cec-bd7f-e293057d1d05%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
