[Solved] AMD-V Is Disabled In The BIOS Error

AMD-V is AMD’s {hardware} virtualization expertise. If this function is disabled within the BIOS or conflicting applied sciences like Hyper-V are enabled, you’ll encounter the AMD-V is disabled within the BIOS error.

The CPU flag for AMD-V is SVM (Secure Virtual Machine). The BIOS setting goes by the identical identify and also you’ll discover it within the CPU Features part. In most circumstances, enabling SVM will resolve this error.

Disabling different virtualization applied sciences like Hyper-V and adjusting your VM configs may also assist. But you normally gained’t should resort to those as enabling SVM will largely do the trick for you.

Enable AMD-V from the BIOS

All Zen-based AMD processors (Ryzen 1000 and newer) assist AMD-V. So, you don’t want to fret about whether or not your system helps AMD-V.

Instead, deal with discovering the SVM setting. It’ll be positioned elsewhere relying on the motherboard and BIOS UI.

1. Turn on or restart your PC and press the BIOS key (Function keys or Del) on the POST display.
2. In the BIOS, press the important thing proven on the display to change to Advanced Mode.
3. Look for the SVM setting:
   • ASUS – Advanced > CPU Configuration
   • MSI – OC > Advanced CPU Configuration
   • Gigabyte – Tweaker > Advanced CPU Settings
   • ASRock – Advanced > CPU Configuration
4. Set SVM to Enabled. Then, press F10 to avoid wasting the modifications and exit the BIOS.
5. After restarting, attempt operating the VM. It ought to work easily now.

Disable Hyper-V

Windows consists of some native virtualization options like Hyper-V that depend on AMD-V. You should disable these to make sure different hypervisors like VMware and VirtualField can run correctly. 

1. Press Win + R, sort optionalfeatures, and press Enter.
2. Uncheck the next options and press OK:
   • Hyper-V
   • Virtual Machine Platform
   • Windows Hypervisor Platform
   • Windows Subsystem For Linux
3. Check if the VM boots correctly now.

Reduce VM Cores to 1

When {hardware} virtualization (AMD-V) is disabled, attempting to run multicore VMs will trigger this error. In this case, examine if lowering the VM cores to 1 helps.

On Oracle VirtualField,

1. Select the VM from the left pane and click on on Settings.
2. Switch to the System tab and click on on Processor.
3. Change the no. of CPU cores assigned to 1 right here and press OK.
4. Close the Settings window. On the house web page, press Start to launch the VM.

On VMWare Workstation,

1. Select the VM from the left pane and click on on Edit Virtual Machine Settings.
2. In the Hardware tab, click on on Processors. Assign a single core to the VM and press OK.
3. On the house web page, choose the VM and press Power on this digital machine.

Note: Limiting your VM to a single core may cause a bottleneck in some eventualities. So, whereas this methodology works for troubleshooting, I like to recommend enabling AMD-V as the most effective long-term resolution.

Configure PAE/NX Setting (VirtualField)

32-bit structure solely helps a max of 4 GB reminiscence, and the identical is true for VMs. If extreme reminiscence is the explanation for this error, you may have two methods to make things better.

You can allocate 3584 MB or decrease RAM to your VM. But once more, that is prone to trigger a bottleneck and negatively have an effect on efficiency. Instead, I like to recommend enabling PAE/NX, which can can help you allocate as much as 64 GB of RAM.

1. Launch VirtualField and choose your VM.
2. Click on Settings > System > Processor.
3. Enable PAE/NX and click on OK.
4. Check when you can run the VM with out the error now.

Note: If you allow this function with 64-bit visitors, that may result in the AMD-V is disabled within the BIOS error. So, with 64-bit visitors, attempt disabling PAE/NX as a substitute.