Other possible reasons include system updates that alter BIOS settings or conflicting software settings, like Hyper-V being enabled in Windows. In this article, we will discuss solutions to this problem.
1. Enable AMD-V in the BIOS settings
Enabling AMD-V in your BIOS activates your CPU’s built-in virtualization features. This is important because VirtualBox needs these features to efficiently run 64-bit operating systems and manage workloads using multiple CPU cores. Without AMD-V enabled, you might encounter issues when trying to set up or run virtual machines that require these capabilities. However, the process to access BIOS varies based on the motherboard manufacturer. During initial startup, press the Setup key—typically one of the F keys (F2, F4, F8, F10, F12) or the Del key (for Dell machines). If you cannot find the Setup key, look for a prompt during the startup sequence or search for instructions specific to your motherboard brand. After entering BIOS, locate the Secure Virtual Machine Mode entry and make sure it’s set to Enabled. This option is typically found under Advanced > CPU Configuration. Save your changes and exit BIOS. Note: The precise location of this option might differ depending on your motherboard model. If you cannot find Secure Virtual Machine Mode, look for AMD IOMMU and switch it to Enabled within the AMD I/O Virtualization Technology menu for users with Acer motherboards. Remember that a simple restart won’t enforce the change; a cold boot is required. Power off your machine completely and allow it to boot from the beginning. After rebooting, open the previously affected virtual machine within VM VirtualBox to check if the error has been resolved.
2. Disable Windows Hyper-V
Hyper-V, a virtualization tool in Windows, can prevent other programs like VirtualBox from accessing hardware virtualization, causing the AMD-V error. Disabling Hyper-V allows VirtualBox to use your system’s virtualization features, which is important for running 64-bit virtual machines.
3. Change the number of CPU cores to 1
By reducing the number of virtual CPU cores to 1, you can avoid needing AMD-V, which is necessary for using multiple cores in VirtualBox. Even without hardware virtualization, VirtualBox can still run a virtual machine with a single core.
4. Change the Version to Windows 7 or Windows 2003 (if applicable)
When you set the version to Windows 7 or Windows 2003 in VirtualBox, it adjusts the virtual machine to work without needing advanced features like hardware virtualization (AMD-V). These older operating systems require less from the system and don’t depend much on AMD-V, which might be turned off in your BIOS.
