This isn't a Vagrant issue. VT-x is.a BIOS setting (on your computers Motherboard) that allows for virtualization. You will need to restart your machine, get into the BIOS settings and then look for the VT-x settings that will allow you to move forward (usually a checkbox). The location for the settings are different for every motherboard
On Tuesday, July 4, 2023 at 8:36:32 AM UTC-4 Akinola Akinbusola wrote: > i am having the error running Vagrant up, it is showing > > There was an error while executing `VBoxManage`, a CLI used by Vagrant > for controlling VirtualBox. The command and stderr is shown below. > > Command: ["startvm", "9ce2d19c-eb2a-4fe1-9a1f-69c30f9c81db", "--type", > "headless"] > > Stderr: VBoxManage.exe: error: Not in a hypervisor partition (HVP=0) > (VERR_NEM_NOT_AVAILABLE). > VBoxManage.exe: error: VT-x is disabled in the BIOS for all CPU modes > (VERR_VMX_MSR_ALL_VMX_DISABLED) > VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component > ConsoleWrap, interface IConsole > -- 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/hashicorp/vagrant/issues Discuss: https://discuss.hashicorp.com/c/vagrant/24 --- 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/3ed0099c-9b10-442f-9e0d-94e3f0fa65e4n%40googlegroups.com.
