I'm trying to virtualize an older UNIXWare box that I've managed to run on a physical machine with Windows Server using VirtualBox. My next step is to migrate this setup to the cloud. I created a new virtual machine in Azure using the Standard D2as v4 configuration and installed VirtualBox there. After transferring my VDI files from the physical host, I attempted to launch the virtual machine, but I'm getting an error stating: *WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (VERR_NEM_NOT_AVAILABLE).* It also mentions that *AMD-V is not available.* I installed Hyper-V, but it didn't help, and after reading some threads, I removed it since it might interfere. The physical machine has an Intel processor, while the Azure VM has a virtual AMD processor running Windows 11 Pro. Anyone have tips on how to resolve this issue?
3 Answers
From what I've read, the Dv3 and Ev3 instance types in Azure support nested virtualization, but it's not well documented. If you're using a different VM type, that could be the problem. Make sure your instance meets the requirements for VirtualBox. Also, try running your VM with a different configuration if possible.
Have you looked into enabling nested virtualization for your Azure VM? VirtualBox relies on certain features that need nested virtualization to be available. You can enable it in Azure if you have the right VM types. It's worth checking out what specific configuration you're using and ensuring it supports this setup.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures