This arrangement is still being developed and isn't 100% yet. But your PC is of the type and OS where Virtualbox can attempt to run the guest using the Hyper-V engine. This is because a service that uses Microsoft Hyper-V is running on your host PC. You might notice in the guest window's Status Bar the green turtle: The choice of animal is appropriate: Your guest is running, just really slow.
NEM: WHvCapabilit圜odeHypervisorPresent is TRUE, so this might work. Aside from re-installing VirtualBox (I have a macOS VM that took ages to get working), what can I do about this? TwistyTurtleFish Posts: 4 Joined: 8. I recently updated the Windows host to 2004, but I don't see why this should affect VirtualBox. My existing VMs do not boot and freeze in the same way.
Sometimes moving the mouse causes a slight spike in CPU usage, but no change shows on the screen. If I disable Hyper-V in the paravirtualization option and choose anything else, the VM does not get past the Windows logo and freezes. Yesterday I tried installing Windows but got a blue screen error on the guest but the VM never got to restart because it stopped doing anything at 100% on the blue screen. Pausing and unpausing the VM kicks it back into working for a few seconds (occasionally enough time for the percentage to go up slightly) but then stops again. The session manager shows no resource usage whatsoever. It finishes copying files but then stops doing anything. I'm trying to install Windows 10 using an ISO created with the Windows Media Creation Tool for Windows 10 version 2004.
0 kommentar(er)
