Learn how to fix VirtualBox’s “AMD-V is not available (VERR_SVM_NO_SVM)” error. Our Windows Support team is here to help you with your questions and concerns.

How to Fix the “AMD-V is not available (VERR_SVM_NO_SVM)” Error in VirtualBox

You’re not alone if you run into the error “AMD-V is not available (VERR_SVM_NO_SVM)” while trying to start a virtual machine in VirtualBox.

This is a common problem faced by users trying to run 64-bit virtual machines, especially on systems with AMD processors.

Today, we will break down what this error means, why it happens, and how you can fix it.

The error message “AMD-V is not available (VERR_SVM_NO_SVM)” indicates that the system’s hardware virtualization support is either:

• Not enabled in BIOS, or
• Not supported by your CPU, or
• Blocked by other software like Hyper-V or Windows security features

AMD-V (SVM or Secure Virtual Machine) is AMD’s hardware-assisted virtualization feature, similar to Intel VT-x. It must run 64-bit virtual machines and enable features like multiple virtual cores.

Common Causes Behind the Error

Here are the most frequent reasons behind this error:

1. Older AMD processors may not entirely support AMD-V. So, check the processor specs on AMD’s website or use tools like CPU-Z.
2. Even if the CPU supports AMD-V, the BIOS/UEFI may turn it off. Look for options like SVM Mode or Virtualization under CPU features.
3. Despite the virtualization enabled in BIOS, features like Hyper-V, Windows Sandbox, Core Isolation, or Credential Guard can block VirtualBox from accessing AMD-V.

For a deeper dive into how Hyper-V affects virtualization, check out our blog on the role of Microsoft Hyper-V for virtualization in Windows Server 2008.

How to Fix the Error

1. Turn Off Hyper-V

1. First, open an elevated Command Prompt (Run as Administrator) and enter:

   bcdedit /set hypervisorlaunchtype off
2. Then, restart your computer.

If you’re working with nested virtualization, such as running a Windows VM under VMware ESXi, check out our guide on installing the Hyper-V role in Windows 10 VM under VMware ESXi.

2. Disable Virtualization-Based Security

1. Open Group Policy Editor (`gpedit.msc`).
2. Then, go to Computer Configuration > Administrative Templates > System > Device Guard > Turn on Virtualization-Based Security.
3. Next, set it to Disabled.
4. Now, do the same for Credential Guard.

3. Check Core Isolation in Windows Security

1. First, go to Windows Defender Security Center.
2. Then, click on Device Security > Core Isolation Details.
3. If Memory Integrity is on, turn it off.

If it’s greyed out, open the Registry Editor and go to

`HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\DeviceGuard\Scenarios\HypervisorEnforcedCodeIntegrity`

Then, set the value to `0` and reboot the system.

4. Uninstall Conflicting Windows Features

Some clients have reported that enabling Windows Sandbox or Hypervisor Platform can trigger this error.

Our Experts fixed this with these steps:

1. Go to Control Panel > Programs > Turn Windows features on or off.
2. Then, uncheck:
   • Hyper-V
   • Windows Sandbox
   • Windows Hypervisor Platform
3. Finally, reboot the PC.

Still having trouble with virtualization features conflicting in Windows? Our detailed fix for Windows error code 0xc004f211 might offer more context for resolving related configuration issues.

5. Enable SVM in BIOS

If not already done, enter the system BIOS (usually by pressing `Del`, `F2`, or `F10` at boot), and:

1. Go to Advanced > CPU Configuration.
2. Then, look for SVM Mode or Virtualization Technology.
3. Set it to Enabled.
4. Finally, save and exit BIOS.

This setting may be called SVM on AMD systems and VT-x on Intel.

6. For VMware Users – Enable Nested Virtualization

If we are running VirtualBox inside a VMware hypervisor like ESXi, we need to enable nested virtualization.

• Option 1 – SSH into the ESXi host and edit the config:

  vhv.enable = "true"
• Option 2 – Use vSphere to set this in the VM’s advanced settings.

Additional Fixes – “AMD-V is not available (VERR_SVM_NO_SVM)”

Here are some additional fixes if the above tips did not resolve the error:

• Try disabling Windows Sandbox and Hyper-V, then rebooting.
• You can also try disabling and re-enabling SVM in BIOS.
• Sometimes, tweaking registry keys due to greyed-out settings in Windows Security can help.

Similar root causes trigger other common Windows errors like the “driver_irql_not_less_or_equal” error, where driver conflicts or security features cause unexpected behavior. These problems often share similar fixes.

[Need assistance with a different issue? Our team is available 24/7.]

Conclusion

The “AMD-V is not available (VERR_SVM_NO_SVM)” error is usually caused by disabled BIOS settings or interference from Windows security and virtualization features.

In brief, our Support Experts demonstrated how to fix VirtualBox’s “AMD-V is not available (VERR_SVM_NO_SVM)” error.