This means changing our VMM to run at user level instead of in privileged mode, as well modifying it to use the WHP APIs to manage the execution of a guest instead of using the underlying hardware directly. To fix this Hyper-V/Host VBS compatibility issue, VMware’s platform team re-architected VMware’s Hypervisor to use Microsoft’s WHP APIs. Any attempt to run VMware’s traditional VMM fails because being inside Hyper-V the VMM no longer has access to the hardware’s virtualization support. When a Windows host enables Virtualization Based Security (“ VBS“) features, Windows adds a hypervisor layer based on Hyper-V between the hardware and Windows. VMware Workstation traditionally has used a Virtual Machine Monitor (VMM) which operates in privileged mode requiring direct access to the CPU as well as access to the CPU’s built in virtualization support (Intel’s VT-x and AMD’s AMD-V). How does VMware Workstation work before version 15.5.5?
At VMworld 2019 San Francisco, VMware and Microsoft together made an announcement that we have jointly developed a project that adopts Microsoft Windows Hypervisor Platform (WHP) APIs.In order to satisfy our customers, VMware and Microsoft started a collaboration with the goal of fixing this problem. Since the introduction of Hyper-V, including Credential Guard and Device Guard, enabling any of these features prevented VMware Workstation from launching virtual machines.You can also check out Microsoft’s blog here. With the release of VMware Workstation/Player 15.5.5, we are very excited and proud to announce support for Windows hosts with Hyper-V mode enabled! As you may know, this is a joint project from both Microsoft and VMware.
0 kommentar(er)
