7
1
I enabled virtualization in the bios yesterday and the virtual machine worked yesterday. Today, I double checked in the bios and virtualization is still enabled. But the virtual machine is giving me this error when I tried to start it up:
Failed to open a session for the virtual machine Ubuntu 15.04.
AMD-V is not available (VERR_SVM_NO_SVM).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
What's causing this, and what do I do?
My motherboard is a Gigabyte GA-78LMT-USB3
My CPU is an AMD FX-6300 3.5GHz 6-Core Processor Black Edition
Update: After installing a 32-bit version of Ubuntu on the virtual machine, it worked fine. However, that still doesn't explain why VirtualBox doesn't detect that I have AMD-V, I tried running ubuntu on vmware and that tells me that I have to turn Hyper-V off, so my virtualization is definitely on, it's just that virtualbox does not detect it.
Update 2: Ubuntu launches, but it keeps flickering non-stop; this means that VirtualBox is not detecting my Hyper-V.
Update 3: Hyper-V was installed on the system, Hyper-V apparently causes a conflict between other virtual machines, I'm turning this off now and letting windows restart.
Update 4: IT WORKS!
Hope, other users will quickly provide you a solution over here. – MWiesner – 2015-12-21T21:17:07.187
@MWiesner Hey again, I hope so too; really need this to be solved. – Dominik H – 2015-12-21T21:17:45.520
1Do you have any other hypervisors running? – Ƭᴇcʜιᴇ007 – 2015-12-21T21:22:32.780
@Ƭᴇcʜιᴇ007 nope, only virtualbox, if that's what you're asking? – Dominik H – 2015-12-21T21:24:35.690
I have that issue sometimes, and a reboot helps. for some reason, something seems locked from the previous run. I guess you had that idea already; if not, try reboot to clean the locking of the AMD-V – Aganju – 2015-12-21T21:27:46.750
@Aganju I wish it was as easy a fix as that, unfortunately, no difference. – Dominik H – 2015-12-21T21:29:05.480
Assuming your guest OS is 32-bit, LongMode must be disabled. This can be done by command line:
VBoxManage modifyvm <vmname> --longmode off
– misha256 – 2015-12-21T21:31:15.193@misha256 I've never used the command line for VBox before, where do I do this? – Dominik H – 2015-12-21T21:38:12.373
@DominikH Just open your Terminal and enter the command. Of course, replace <vmname> with something sensible. – misha256 – 2015-12-21T21:40:54.480
@misha256 This doesn't seem to work either. – Dominik H – 2015-12-21T21:51:04.470
@Ƭᴇcʜιᴇ007 Guess what! Apparently I had Hyper-V installed and running too, no wonder it hadn't worked... – Dominik H – 2015-12-22T00:58:29.503
Disabling Hyper-V worked for me as well. – Brendan Abel – 2017-01-21T06:37:39.610