AMD-V is disabled

42 views
Skip to first unread message

Mahmood Naderan

unread,
Mar 14, 2018, 12:29:07 PM3/14/18
to vagra...@googlegroups.com
Hi, the vagrant up command aborts with the following error

==> m1: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "09ccbab9-8c49-422d-9b30-80e92fd0a1f1", "--type",
"headless"]

Stderr: VBoxManage: error: AMD-V is disabled in the BIOS (or by the
host OS) (VERR_SVM_DISABLED)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005),
component ConsoleWrap, interface IConsole



I know about that feature in VirtualBox. But I don't know how to
enable that through vagrant. Any help?

Regards,
Mahmood

Mitchell Hashimoto

unread,
Mar 14, 2018, 12:35:23 PM3/14/18
to vagra...@googlegroups.com
Hey Mahmood,

This is an OS or BIOS level setting, and can’t be set by Vagrant or VirtualBox. Please check for help for your specific OS on enabling AMD-V, and also check your BIOS settings on boot.

Best,
Mitchell
--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CADa2P2Wzd%2Bh%3DicXV-5oyk2QnYZ9eyYVrCeGtDd_rCP_s%3DPNgZg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
Reply all
Reply to author
Forward
0 new messages