Hello,
Been using VMWare WS Pro for a number of years, have multiple VMs running simultaneously. Do use snapshot on one VM consistently.
With latest Win-11 Pro, it seems that one has to install WHP to run VMWare WS Pro.
Running VMware with WHP enabled means one is essentially running a Type 2 hypervisor (Workstation) on top of a Type 1 hypervisor (Hyper-V). This nested virtualization adds a performance hit that is completely eliminated when using Hyper-V directly, as it runs closer to the hardware.
From - VMware Workstation 15.5 Now Supports Host Hyper-V Mode
"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). When a Windows host enables Virtualization Based Security (“VBS“) features, Windows adds a hypervisor layer based on Hyper-V between the hardware and Windows. 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."
So unless one is bound by whatever reason/need to run VMWare WS, there is no need to do that. My case is the latter. I can certainly move to Hyper-V instead of all the gymnastics that are needed to disable CredentialGuard etc or run type-2 over type-1.
Curios what would be the reason to stick with VMWare WS. I guess the above is the reason why Broadcom made it free
Question
mfessler 0
Been using VMWare WS Pro for a number of years, have multiple VMs running simultaneously. Do use snapshot on one VM consistently.
With latest Win-11 Pro, it seems that one has to install WHP to run VMWare WS Pro.
Running VMware with WHP enabled means one is essentially running a Type 2 hypervisor (Workstation) on top of a Type 1 hypervisor (Hyper-V). This nested virtualization adds a performance hit that is completely eliminated when using Hyper-V directly, as it runs closer to the hardware.
From - VMware Workstation 15.5 Now Supports Host Hyper-V Mode
"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). When a Windows host enables Virtualization Based Security (“VBS“) features, Windows adds a hypervisor layer based on Hyper-V between the hardware and Windows. 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."
So unless one is bound by whatever reason/need to run VMWare WS, there is no need to do that. My case is the latter. I can certainly move to Hyper-V instead of all the gymnastics that are needed to disable CredentialGuard etc or run type-2 over type-1.
Curios what would be the reason to stick with VMWare WS. I guess the above is the reason why Broadcom made it free
Link to comment
Share on other sites
0 answers to this question
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.