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

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!

Dominik H

Posted 2015-12-21T21:08:24.717

Reputation: 83

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

Answers

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/

Christian Matthew

Posted 2015-12-21T21:08:24.717

Reputation: 166

Welcome to superuser and thankyou for your answer, but it may have already been in the updates:- 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! – mic84 – 2017-04-24T08:44:06.093

1@mic84 It wasn’t an answer, however. Answers go in the answer section, not in the question. – Daniel B – 2017-04-24T08:50:23.523

Hi @mic84 and DanielB I really appreciated the op's questions because it was a similiar error... And apparently a lot of people trying to run VB or Gennymotion have the same issue. The obscurity wasn't with my Bios (which I updated) or settings which I kept trying to adjust... or running in 32 bit mode for certain aspects like the OP suggested... But alas JUST make sure Hyper-V is not running which is a default setting since at the very least the Windows 10 Creators update has been issued. That is why I felt an answer with just Hyper V was adequate and hope it helps more people – Christian Matthew – 2017-04-24T14:02:14.507

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.

misha256

Posted 2015-12-21T21:08:24.717

Reputation: 10 292

I will update the information now. And just a quick question: If instead of rebooting, I turn the pc on and off; would this make a difference rather than doing a normal reboot where my pc remains on? – Dominik H – 2015-12-21T21:53:02.813

Also, I would like to note that the Guest OS is 64-bit, BUT has been forced to run in 32-bit mode as Virtualization is apparently "not available" – Dominik H – 2015-12-21T21:56:48.007

@DominikH When you change Virtualization BIOS setting, the requirement is that you power down the PC for the setting to take effect. Just rebooting is not enough. – misha256 – 2015-12-21T22:02:31.040

@DominikH Is your HOST operating system 32-bit or 64-bit? – misha256 – 2015-12-21T22:02:57.153

ahh, now that's something, cheers for letting me know. I will actually power down the system and then try that again! – Dominik H – 2015-12-21T22:03:26.197

my host and guest are both 64-bit – Dominik H – 2015-12-21T22:03:44.860

I did a proper restart this time, and still no luck. So I believe I should turn virtualization off, shut down, start up, turn virtualization on, shut down start up? – Dominik H – 2015-12-21T22:11:30.950

Update: Still no success. – Dominik H – 2015-12-21T22:57:24.880

Sorry for so many comments, but I recreated the VM and it boots up; however the actual interface will not load as its forced to run in 32-bit mode and virtualization is "enabled" – Dominik H – 2015-12-21T23:03:00.523