-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Stderr: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX) #10056
Comments
Hello Ethan, You should stop in your host's BIOS, and enable two settings in CMOS: Best Regards, |
@ZoranStojsavljevic Hi, Thanks for your reply. actually, i plan to use vagrant in the cloud platform of centos7 system, i think for this cloud platform, it is not a real machine.. how to enable the BIOS setting? Is it possible? |
hashicorp/vagrant issue 10045, my latest comment there:
#10045 (comment)
Zoran
…On Tue, Jul 24, 2018 at 2:04 PM, EthanLXGu ***@***.***> wrote:
@ZoranStojsavljevic <https://github.com/ZoranStojsavljevic> Hi, Thanks
for your reply. actually, i plan to use vagrant in the cloud platform of
centos7 system, i think for this cloud platform, it is not a real machine..
how to enable the BIOS setting? Is it possible?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#10056 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AbOzZT4Vo3r7_Grbxyws_1a41X0CxFMBks5uJw1IgaJpZM4Vb7S5>
.
|
@EthanLXGu - I believe the only cloud that supports enabling VT-X right now is GCE? There are instructions here if that's what you're using centos-7 on: https://cloud.google.com/compute/docs/instances/enable-nested-virtualization-vm-instances Otherwise, you won't be able to bring up VMs if VT-X is disabled. I'll go ahead and close this issue, but if you want further help enabling VT-X or finding another solution feel free to email the Vagrant mailing list. Thanks! |
Hello, I have Ubuntu 16.04, 32 bit system. Steps: On vagrant up i got error:
Can you please guide? Thanks, |
@apoorva-shah - you need to go into your bios and enabled virtualization. |
Hello @briancain , Thanks, |
Hello @briancain , Thanks, |
@apoorva-shah - it depends on who makes your computer, but this guide might work: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/5/html/virtualization/sect-Virtualization-Troubleshooting-Enabling_Intel_VT_and_AMD_V_virtualization_hardware_extensions_in_BIOS |
Just wanted to ask if there are any changes to this ever since |
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. |
Please note that the Vagrant issue tracker is in priority reserved for bug reports and enhancements. For general usage questions, please use the Vagrant mailing list:
https://groups.google.com/forum/#!forum/vagrant-up. Thank you!
Tip: Before submitting your issue, don't hesitate to remove the above introductory text, possible empty sections (e.g. References), and this tip.
Vagrant version
Vagrant 2.1.2
Host operating system
Centos7 cloud platform.
Guest operating system
Centos7
Vagrantfile
Please note, if you are using Homestead or a different Vagrantfile format, we
may be unable to assist with your issue. Try to reproduce the issue using a
vanilla Vagrantfile first.
Debug output
Provide a link to a GitHub Gist containing the complete debug output:
https://www.vagrantup.com/docs/other/debugging.html. The debug output should
be very long. Do NOT paste the debug output in the issue, just paste the
link to the Gist.
Expected behavior
Vagrant up should start this vm
Actual behavior
There was an error while executing
VBoxManage
, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "b4293ed5-0a7a-4fb2-bd62-23d47fe87557", "--type", "headless"]
Stderr: VBoxManage: error: VT-x is not available (VERR_VMX_NO_VMX)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole
Steps to reproduce
References
Are there any other GitHub issues (open or closed) that should be linked here?
For example:
The text was updated successfully, but these errors were encountered: