“AMD-V is not available” even when Virtualization is enabled in the bios

6

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!

ubuntu
bios
virtualization
asked on Super User Dec 21, 2015 by Dominik H • edited Mar 1, 2016 by Hennes

2 Answers

4

Make sure Hyper-V is disabled.

This is the command you should run in cmd.exe as an administrator

dism.exe /Online /Disable-Feature:Microsoft-Hyper-V-All

Full instruction set is listed here

http://www.poweronplatforms.com/enable-disable-hyper-v-windows-10-8/

answered on Super User Apr 24, 2017 by Christian Matthew
0

When you enabled Virtualization in your BIOS settings, the reason why your Virtual Machine worked perfectly fine is because the BIOS setting didn't actually kick in until you powered off your PC and powered it back on.

Assuming your guest OS is 32-bit, LongMode must be disabled. In some cases it isn't, which is just bad. To fix this for a particular VM, open Terminal and enter:

VBoxManage modifyvm <vmname> --longmode off

Don't forget to replace <vmname> with the name of your virtual machine.

For some reason your issue only comes up when hardware assisted virtualization is enabled in the BIOS. Anyway, if this does not fix the issue, then I would put my money on your CPU or motherboard not providing a fully compatible hardware virtualization implementation, in which cause you'll just have to disable the BIOS feature.

Incidentally you might want to update your question with more details about your motherboard and CPU, that may give us more clues as to what's going on.

answered on Super User Dec 21, 2015 by misha256

User contributions licensed under CC BY-SA 3.0