AMD-V is disabled in BIOS (VERR_SVM_DISABLED)

Multiple users report that they receive the error message AMD-V is disabled in the BIOS (or by host operating system) (VERR_SVM_DISABLED) when they try to start a virtual machine using VM VirtualBox. Although this particular problem is mostly reported on Windows 7, Windows 8 and Windows 10, there are various reports of it happening on Linux distributions.

AMD-V is disabled in BIOS (VER_SVM_DISABLED)

Note: If the VT-X is not available, error VERR_VMX_NO_VMX, follow this troubleshooting guide (here).

What is causing AMD-V to disable in a BIOS error?

We investigated the issue by looking at various user reports. From what we were able to collect, there are several scenarios that will trigger the emergence of this particular topic. Here is a list of common culprits that several other affected users have managed to identify:

• AMD-V is disabled in BIOS setup: in essence, the error code VERR_SVM_DISABLE tells you that your PC is AMD-V compatible, but the host BIOS setting is currently disabling it.

• Microsoft Hyper-V is interfering with AMD-V technology: if Hyper-V is enabled, automatically means that the embedded virtualization technology has been disabled. In this case, you will have to disable it to allow AMD-V to be used.

• BIOS version does not support as many CPU cores: It turns out that VM VirtualBox could generate the problem if the software is forced to create a virtual machine with more than 1 CPU core. To do this, requires hardware virtualizations and will throw the error if the feature is disabled or unavailable.

• Error de VM VirtualBox: there are multiple reports of this bug on machines capable of supporting hardware virtualization technology. In this case, the problem can usually be solved by modifying some specific virtual machine settings.

If you are currently having difficulty resolving this particular error message, this article will provide you with various troubleshooting guides. Here is a collection of methods that other users in a similar situation have used successfully to solve the problem.

Note that the possible solutions below are ordered by efficiency and severity, so follow them in order until you find a method that is effective in solving the problem.

Method 1: enable AMD-V from BIOS setup

AMD-V is the recognized brand for Secure Virtual Machine Mode (SVM). The main reason why AMD-V is disabled in BIOS (or by host operating system) (VERR_SVM_DISABLED) an error occurs is because AMD-V technology is disabled in BIOS setup.

Although this option is enabled by default on most machines, third party interference or manual modification could mean it is disabled on your computer.

Fortunately, you can re-enable AMD-V by entering BIOS setup and re-enabling safe virtual machine mode from CPU settings.

But keep in mind that the steps to enter the BIOS will be different depending on your motherboard manufacturer. To access your BIOS, you will need to press the Setup key during the initial startup procedure. Normally, the Settings key is one of the F keys (F2, F4, F8, F10, F12) or the Supr (for Del machines). If you can't find out the setup key yourself, be on the lookout during the initial startup procedure for any mention of it or look for specific steps depending on your motherboard manufacturer.

Press the BIOS key during the boot procedure

Once you have successfully entered your BIOS, look for an entry called Secure Virtual Machine Mode and make sure it is enabled. In the most popular version of BIOS, can be found in Advanced> CPU configuration. Once there, make sure secure virtual machine mode is enabled, then save the settings and exit your BIOS.

Make sure secure virtual machine mode is enabled

Note: The exact location of this input may vary depending on your motherboard model. If Secure Virtual Machine Mode is not available to you, look for specific steps according to your manufacturer. On an Acer motherboard, you can re-enable AMD-V by setting AMD IOMMU to Enabled (can be found in the Virtualization Technology menu of E / S the AMD).

Please note that for the change to take effect, it is not enough to reboot the machine. You will need to perform a cold start. This means that you will have to shut down the machine completely and then allow it to start from scratch.

Once the next boot is complete, open the virtual machine that was showing you the message inside VM VirtualBox and see if the problem is resolved. If you still see that AMD-V is disabled in the BIOS (or by host operating system) (VERR_SVM_DISABLED) error, scroll down to next method below.

Method 2: deshabilitar Windows Hyper-V

Multiple users who encountered the error AMD-V is disabled in the BIOS (or by host operating system) (VERR_SVM_DISABLED) have managed to resolve the problem by disabling the Microsoft Hyper-V role from the Windows Add / Remove Features screen.

Microsoft Hyper-V is Microsoft's proprietary virtualization technology that is automatically activated in the latest versions of Windows. This creates a problem because every time Hyper-V is activated, embedded hardware technology shuts down (in this case (AMD-V). Since VM VirtualBox needs AMD-V or VT-X to run a virtual machine, you will get an error message instead of the actual virtual machine.

Fortunately, You can easily fix this problem by following a series of simple instructions to help you disable Microsoft Hyper-V technology.. This is what you have to do:

1. Press the Windows key + R to open a Run dialog. Then type »appwiz.cpl» and hit Enter to open Programs and Features. Run dialog: appwiz.cpl

2. In Programs and Features, use the menu on the right to click on Turn Windows Features On or Off. In Programs and Features, click Turn Windows Features On or Off

3. On the Windows Features screen, look for a Hyper-V entry and make sure the box associated with it is unchecked. Then click OK to save the changes. Uncheck the box associated with Hyper-V

4. Reboot the machine and see if the error is resolved on the next boot.

If you still find AMD-V disabled in BIOS (o by host operating system) (VERR_SVM_DISABLED) when you turn on your virtual machine, scroll down to the next method.

Method 3: change the number of CPU cores to 1

If you have used the above methods to ensure that your machine has all the requirements to achieve hardware virtualization and the problem continues to occur, AMD-V technology is most likely not compatible with your current configuration.

Fortunately, you can still correct the error with a few simple instruction steps. But first, Let's go over what's causing the problem: even if you have not customized the settings of the virtual machine showing the error, the default settings could create the problem.

What happens is that the software allocates more than 1 CPU in system settings, which forces the system to use hardware virtualization to start the virtual host. However, if your machine doesn't support it (has a quad core AMD or something similar), the procedure will not complete successfully and you will see that the AMD-V is disabled in the BIOS error message (or by operating system host) (VERR_SVM_DISABLED) instead.

Fortunately, You can work around this problem by changing the number of CPUs allocated to 1. This will probably solve the problem once and for all. This is what you have to do:

1. Abra Oracle VM VirtualBox, right-click on the machine displaying the error, and then click Settings. Right-click on the affected machine and click Settings

2. On the Settings tab of your virtual machine, go to the System tab (using the submenu on the left) and go to the Processor tab. Later, drag the slider associated with the Processors to 1 CPU and click OK to save. Go to System> Processor and set the Processor slider to 1 CPU

3. Close the settings menu and restart your virtual machine. It should boot without AMD-V being disabled on a BIOS error (or by host operating system) (VERR_SVM_DISABLED).

Method 4: change the version to Windows 7 o Windows 2003 (if appropriate)

Multiple Ubuntu users (Linux) using VM VirtualBox to run Windows XP or Windows 10 they were also getting the error AMD-V is disabled in the BIOS (or by host operating system) (VERR_SVM_DISABLED). The way they managed to solve the problem is by changing the guest OS settings so that the specified version is set to Windows 2003 o Windows 7.

Although there is no explanation for the success of this solution, seems to have helped many users to regain normal functionality of their virtual machines. Here is a quick guide to change the specified version of your virtual machine:

1. Abra VM VirtualBox, right click on the machine displaying the error and choose Settings. Right-click on the affected machine and click Settings

2. In the Settings menu, go to the General submenu and then click on the Basic tab. Then change the version using the drop down menu to Windows 2003 o Windows 7 and press Ok to save the changes. Change the image version to Windows 7 o Windows 2003

3. Start the virtual machine again and see if the boot procedure is successful without AMD-V being disabled in the BIOS (or by host operating system) (VERR_SVM_DISABLED) error