by socratis » 25. Aug 2019, 10:55
@fth0: So far it isn't clear if VirtualBox runs "correctly" with NEM. The reports have been mostly negative so far, see
VirtualBox 6.0 and Hyper-V.
But then again
- How many users do you know that are going to login and post a success story? Most of the posts will be failures, by definition...
- The MS API for calling into their Hyper-V infrastructure is less than a year old (officially), ever changing (so, what's new) and the VirtualBox calls have to be adjusted with every release. For example, with the latest 1903, the Sandbox feature caused major headaches, just search for "VERR_NEM_VM_CREATE_FAILED".
@Sloan
00:00:02.205456 HM: HMR3Init: Attempting fall back to NEM: VT-x is not available
00:00:02.258228 NEM: WHvCapabilityCodeHypervisorPresent is TRUE, so this might work...
It seems that you have a Hyper-V component enabled. You can tell if this is true from the status bar where the "slow" icon (

) shows. Look at the topic "
I have a 64bit host, but can't install 64bit guests" for some Hyper-V enablers that we're aware of so far. Most probably the Sandbox feature was enabled, and now you have to resort to the command line and the "bcedit" command, see the article above for details.
If VirtualBox is running without Hyper-V enabled, where proper,
hardware virtualization is actually available, then the standard virtualization icon (

) would show.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.