It reads: "The setup program requires your system's restart to finish the Microsoft VC Redistributable installation. Afterwards, run the setup program again. [...] Click 'Yes' to restart. If you want to restart later, press 'no'." If I hit "Yes", my machine restarts, if I hit "No", setup quits. So, I'm not able to run the setup program. When trying to deploy a 64bits VM from VMware Workstation 16 hosted on a Windows 11 family edition, I have this error message: "VMware Workstation does not support nested virtualization on this host. Module 'HV' power on failed. Virtualized Intel VT-x/EPT is disabled for this ESX virtual machine. You will only be able to run 32-bit nested virtual machines. Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Did you mean:
1 Solution 71 Replies
Same issue here. So the problem is if your Windows 10 gets VBS enabled or you try any Hyper-V functionality on Windows 10, it breaks any and all nested virtualization for VMware Workstation. What we need is information on the minimum steps to turn off, delete, change, whatever is necessary on Windows 10 to re-allow the nested virtualization features, as that is for some of us the most essential function we need. So thank you for pointing us to a document that shows in the details that "by the way this disables your nested virtualization", but what we also need desperately is the information to regain that function of nested virtualization. Michael Fryman Solutions Architect Ciber, Inc. www.ciber.com
https://vinfrastructure.it/2018/06/vmware-workstation-and-windows-10-security/ To disable Device Guard or Credential Guard the first step is the following:
We have a KB but, NGL, it's complete trash and I'm having it rewritten. The reason that nested virtualization doesn't work is because our virtual machine monitor ("vmm", the 'hypervisor' part of the hypervisor) code was designed and optimized to do this, but Hyper-V monitor code is not. We actually test ESXi in Workstation (for linux) VMs in monster CI pipelines. Our stack is obviously more mature, so when using the Hyper-V API's we had to make some compromises. We're working with MS to address the use-case, but we don't have a solid delivery date to communicate just yet. - Michael Roy - Product Marketing Engineer: Fusion & Workstation
I also got the same issue. I was able to get the VM working by disabling Virtualize Intel VT-x/EPT or AMD-V-RI and Virtualize CPU performance counters under VM Settings -> Processors -> Virtualization Engine. This is still a big upset for me because I was using VMs inside VMs sometimes. But since I want to try WSL2, I'm going to live with it for now.
My VMs worked fine with Hyper-V enabled under 15.5.5. However, since upgrading to 15.5.6, I find that VMs created by 15.5.5 will not start: getting the same error as this ticket. VMs created earlier than that are working without problem.
Hi， Thank you for posting your query in community. Actually there is no change in this area between ws15.5.5 and ws15.5.6. BTW, could you please share some information about your steps/vmware.log and vm-support bundle for investigation. Thanks.
Hi, The chain of events, as I remember it, was that after installing 15.5.5, I enabled the Hyper-V features and rebooted. At that time, I had no problems running VMs. I created two new VMs, which were linked clones of an existing VM (Windows Server 2019) and had no problems with them that day. Last Thursday, I installed 15.5.6, but did not reboot. I was still able to run all VMs without problem. On Friday, after a reboot Thursday night, I could run older VMs, but neither of the VMs I had recently created would start: I got the error mentioned previously. Disabling Hyper-V features allowed me to run them as before. Since I rarely use Hyper-V, it's not a big issue, but it would be nice if I could do so without having to reboot. I didn't check the logs at the time, but these seem to be the relevant lines: 2020-06-12T09:08:47.230+01:00| vmx| I005: Module 'MonitorMode' power on failed. 2020-06-12T09:08:47.230+01:00| vmx| I005: VMX_PowerOn: ModuleTable_PowerOn = 0 2020-06-12T09:08:47.230+01:00| vmx| I005: Vix: [mainDispatch.c:4200]: VMAutomation_ReportPowerOpFinished: statevar=1, newAppState=1873, success=1 additionalError=0 2020-06-12T09:08:47.230+01:00| vmx| I005: 2020-06-12T09:08:47.230+01:00| vmx| I005+ Power on failure messages: VMware Workstation does not support nested virtualization on this host. 2020-06-12T09:08:47.230+01:00| vmx| I005+ Module 'MonitorMode' power on failed. 2020-06-12T09:08:47.230+01:00| vmx| I005+ Failed to start the virtual machine. 2020-06-12T09:08:47.230+01:00| vmx| I005+ 2020-06-12T09:08:47.230+01:00| vmx| I005: Vix: [mainDispatch.c:4200]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=1 additionalError=0 2020-06-12T09:08:47.230+01:00| vmx| I005: Transitioned vmx/execState/val to poweredOff 2020-06-12T09:08:47.231+01:00| vmx| I005: Vix: [mainDispatch.c:4200]: VMAutomation_ReportPowerOpFinished: statevar=0, newAppState=1870, success=0 additionalError=0 2020-06-12T09:08:47.231+01:00| vmx| I005: Vix: [mainDispatch.c:4238]: Error VIX_E_FAIL in VMAutomation_ReportPowerOpFinished(): Unknown error
I had the same errors with 15.5.6 (just got the 2020H1 update) and found that I had to edit a setting. One that works is edit the processor setting and turn the virtualisation options on, then edit again and turn off, but any change to the settings seems to help. Then the VMS started fine for me. |
