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/4764188d-f782-4d6e-b2c2-575194732a75%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
