跳转至

Running VMware workstation on a Hyper-V enabled host

  • 分类: Clippings

  • 标签: hyper-v, vmware_workstation Windows 11上启用Hyper-V可能与VMware Workstation产生兼容性问题。用户在启用Hyper-V及其附加功能时，无法在VMware Workstation中启动虚拟机，出现“虚拟化AMD-V/RVI在此平台上不受支持”的错误。虽然VMware声称其新版本已支持Hyper-V模式，但用户仍面临选择：要么启用Hyper-V并运行非嵌套虚拟机，要么禁用Hyper-V以运行嵌套虚拟机。解决方案包括禁用某些处理器设置或使用命令行切换Hyper-V的启动类型。

  • Windows 11启用Hyper-V与VMware Workstation兼容性差。

  • 启用Hyper-V后，VMware Workstation无法启动虚拟机。
  • 需要禁用虚拟机设置中的虚拟化特性才能使VMware与Hyper-V共存。
  • VMware版本需为15.5.5或以上，Windows版本需为Win 10 20H1或Win 11。
  • 用户可以通过命令行切换Hyper-V的启动类型来临时启用或禁用它。

Hi,

Windows contains a few features which requires Hyper-V or a part of Hyper-V to be enabled (things like Credential Guard, Device Guard, WSL, the upcoming Android subsystem on Win 11, ...)

This introduces issues on a host which is running VMware Workstation. Issues which are, to my understanding, already resolved as VMware states in their blog and also in some of their KB's:

https://blogs.vmware.com/workstation/2020/05/vmware-workstation-now-supports-hyper-v-mode.html

At the moment I'm trying to achieve a situation where Hyper-V and VMware Workstation coexist on my PC, however without any luck so far.

My system is running Windows 11 21H2, VMware Workstation 16.2.2 and an AMD Ryzen 5600X.

So with Hyper-V disabled, all is working fine and I'm able to boot VM's inside VMware Workstation.

As soon as I try to enable the Hyper-V feature on my host machine and also the extra required feature 'Windows Hypervisor Platform (WHP)', I'm receiving the message 'Virtualized AMD-V/RVI is not supported on this platform' when trying to boot a VM inside VMware Workstation.

VMware Workstation version 15.5.5 and anything above should be compatible to run together with Hyper-V as long as the 'Windows Hypervisor Platform' is also enabled, as VMware Workstation is then able to use these API's to work alongside Hyper-V.

See method 6 in this guide:

https://www.nakivo.com/blog/virtualization-applications-with-hyper-v-device-guard-and-credential-guard/

The funny thing is that VirtualBox seems to have no issues at all and is able to coexist with Hyper-V after enabling the Windows feature 'Windows Hypervisor Platform (WHP)'

The system acceleration status of a VM inside VirtualBox confirms that Hyper-V Paravirtualization is active after enabling WHP on a Hyper-V enabled host and VM's are able to boot inside VirtualBox.

So I wonder what I'm missing. Any ideas?

Comments

PeterFnet • 3 points • 2022-02-19

On the VM settings for processor, are any of the check boxes for virtualizing features to be passed through enabled? I wonder if that is why it works without hyperv, but when they coexist, some of those features are unavailable.

w3sii • 6 points • 2022-02-20

You are right.

So it seems that, right now, if you want to run VMware Workstation on a Hyper-V enabled host

  • The minimum required Windows 10 version is Windows 10 20H1 build 19041.264 or just use Windows 11 (for the host)
  • VMware Workstation/Player minimum version is 15.5.5.
  • Windows features 'Hyper-V' and 'Windows Hypervisor Platform' (WHP) set to enabled.
  • Additionally the VM inside VMware Workstation needs to have the setting 'Virtualize Intel VT-x/EPT or AMD-V/RVI' disabled (Virtual Machine Settings > Processors)

This will allow you to boot a VM inside Workstation.

There's one downside to this: You will lose the option to run nested VM's inside VMware Workstation as it seems that the Hyper-V API doesn't support nested virtualization right now.

For now it seems we need to choose between:

  • Hyper-V enabled and running non-nested VM's in VMware Workstation
  • Hyper-V disabled and being able to run nested VM's in VMware Workstation

No idea if the nested part will ever be supported in the future.

https://docs.vmware.com/en/VMware-Workstation-Pro/16.0/com.vmware.ws.using.doc/GUID-778DD0ED-6FC9-415F-B071-0CEC127BE719.html

Not ideal but instead of uninstalling Hyper-V every time you would want to run a nested VM inside VMware Workstation, you could play with the following options (powershell, run as admin):

  • bcdedit /set hypervisorlaunchtype off
  • bcdedit /set hypervisorlaunchtype auto

Switching between these 2 commands should prevent launching Hyper-V in situations where you, maybe temporarily, want to run a nested VM inside Workstation and allow you to run Hyper-V in situations where you don't need nested VM's inside Workstation.

I'm just not sure if, when switching back to auto, it will also re-enable things like WSL in case this was active before switching the launch type to off. Haven't played around with that yet.

Solved

NeatPicky310 • 3 points • 2023-05-22

As you've found out, VMWare working in "Windows Hypervisor Platform" mode does not have all the features, including virtualizing the virtualization extensions (Intel VT-x & AMD-V), which is needed for nested virtualization. If you need that, you'll need to disable the Windows hypervisor and force VMWare to use its own hypervisor.

Hyper-V itself does support nested virtualization, but Windows likely did not expose that functionality on the API for third party. Microsoft is likely to be blamed. (Although I did not study the API, Virtualbox users ran into the same problems and Windows is highly suspect).

Microsoft wanted to push virtualization based security (memory integrity, Application Guard) and some developer features (Windows Sandbox, WSL2). And that means third party hypervisors are not compatible and can no longer be used. Microsoft basically strong armed every vendor into supporting "Windows Hypervisor Platform" and abandon their own hypervisor implementation by default in order to do what Microsoft wants. But the API supposedly had inputs from vendors are still not on feature parity. Such is the world we live in.

zwarte_piet71 • 1 points • 2022-02-19

I have a case running on this with support. Currently it is not supported, should be fixed in ‘a future version’…

Ahindre • 1 points • 2022-02-20

What in particular is not supported?

The_real_Hresna • 1 points • 2022-02-20

I ran into that problem in like 2019 and kept watching for the fix…

So I run with the tpm thingy disabled… there was a weird command line for it. Now my i9-9900k workstation is stuck at “doesn’t meet the minimum requirements for windows 11”, which I’m just fine with. But annoying that hyper-v breaks. And that it’s necessary to do in the first place. Why MS can’t just cooperate with a company as big as VMware for something this simple is very obnoxious. I thought for sure it had been fixed by now.

cylaer • 2 points • 2022-02-20

Although I agree with you that that should work by now, I'm not sure it is exclusive to VMware... Last time I've tried (around 4 or 5 months ago) the issue also occurred with VirtualBox.

The_real_Hresna • 1 points • 2022-02-20

Yeah I’m actually surprised there isn’t more of an outcry on this anti-competitive position of Microsoft’s. I guess the user base that wants hyper-v and other hypervisors on the same non-server hardware is fairly small.

[deleted] • 1 points • 2022-02-22

Don't trust that Virtualbox is actually running ok with HyperV.. it can and will corrupt VMs without any warning while HyperV is running.