The VM might crashes with BSOD when Windows 10 host wake up after sleep for several hours.Some known issues in the VMware Workstation 20H1 Technology Preview build 15679048 when operating in Host VBS Mode: Powering on virtual machines with vPMC enabled will fail on Hyper-V enabled Windows 10 host as vPMC is not supported.However, if cpuid.enableMPX = TRUE, but the hardware version of the VM is below the minimum supported hardware version for MPX (version 13), power-on will succeed but MPX will not be exposed to the VM. When cpuid.enableMPX = TRUE, power-on will fail unless the host supports MPX. VM is not exposed to this capability, unless requested by the new config option cpuid.enableMPX. x86 memory protection extension (MPX) feature that was introduced in Skylake processors is deprecated.The workaround is to disable Hyper-V in host and power on VMs with x86 virtualization features.
Consequently, a guest that uses these features – notably, Windows VBS or most hypervisors – will not be able to power on. VM cannot access x86 virtualization features (Intel VT / AMD-V) if host VBS is enabled.
If you’re using VMWare Workstation, and also need to use Hyper-V, you can now run VMWare Workstation and Hyper-V concurrently together in Windows 10, beginning from Windows Update (Version 2004 Build 19041), codenamed 20H1. Thus, most hosted hypervisors, including the popular VMWare Workstation, require Hyper-V to be disabled, which also disable all Windows 10 features that rely on Windows Hypervisor Platform. With the reliance on windows Hypervisor Platform, it means that other hosted hypervisors that are using Intel VT-x or AMD-V virtualization instructions no longer have access to it as Windows OS is now essentially a virtual machine running on Hyper-V level 1 hypervisor, and thus no longer able to run successfully or optimally. Windows 10 and its server OS (namely Windows Server 2016 and Windows Server 2019 or later) has included more and more goodies that require Windows Hypervisor aka Hyper-v virtualization support, such as Credential Guard, Device Guard, Windows Defender Application Guard, Windows Sandbox, Windows Subsystem for Linux 2 (WSL 2), Windows Server Containers and Virtualization Based Security (VBS).
0 kommentar(er)
