Attempting to do nested virtualization

[Coltons]

I am running the public beta of Mac - Big Sur public beta 3. I see that VMWare Fusion has full Big Sur support based on the website. Currently, I'm trying to run nested virtualization on a Ubuntu-20.04 instance and i'm getting the error "VMware Fusion does not support nested virtualization on this host. Module 'HV' power on failed. Failed to start the virtual machine"

I have enabled hypervisor applications in the virtual machine under Processors and memory.

Is there anything I need to do in order to have this run successfully?

Thanks!

[lacierdias]

Good morning people. Would anyone have news of VMWare with feature nested in Big Sur?
In EVE-NG, all images that are qemu still not working. Despair is already hitting. No one speaks.

[bscully]

My nested VMs run since VMware enabled nested virtualization in Fusion.  However, they underperform so poorly as to be unusable.

Incidentally, I tested my VMs on Parallels and experienced the same overwhelming  sluggishness, even using Parallels’ hypervisor.  It appears that this issue with nested virtualization will need to be worked out between Apple and VMware.

[SvenGus]

Personally, in Big Sur, experimenting in Windows 10 VMs with WSL 2 (which is a text-based nested VM), I have had almost normal (as in Catalina) performance in Parallels with their own hypervisor, and almost unusable performance in Fusion with the Apple hypervisor (while in Catalina it worked without problems): the main problem here seems to be the limited nested performance of the Apple hypervisor; and the fact that having nested virtualization enabled also strangely decreases the overall performance of a Windows 10 VM (while macOS and Linux VMs seem to run normally, at least on my machine)...

[bscully]

My experience has been similar to yours, except that my Linux VM (CentOS) with nested virtualization runs horrendously slow when loading nested VMs.  In particular, Cisco CML is unusable in both Fusion and Parallels (bare-metal install), although installing on Parallels is not technically supported.  With CML, running IOS nodes take about 5x as long to respond and the overall CPU utilization hits the ceiling.  With Parallels, I tried their hypervisor and Apple's, but no difference.

I have reached out to Fusion's Support and posted on this forum, but only crickets so far.

I can only hope that one of these 3 will figure out a feasible workaround.

Help us Obi-Wan!

macOS Big Sur 11.0.1 | VMware Fusion Professional Version 12.1.0 (17195230)

[babak1980]

I just last night rolled back to Catalina everything working fine as before. I suggest do same I know it’s painful but worth it. 

[gringley]

I tried VMTools 11.2 to get Metal in the Big Sur VMs, and that seems to work.  The VMs are noticeably slower though (and I am on a Xeon platform) and this 12.1 release overall is disappointing.

[sandervanvugt]

Hi Mikero, thanks for the update! I think you are talking about Fusion 12.1 right? Could it be that it works on some processors only, not all? I have 12.1 installed on Big Sur, and still no luck in running nested virtualization in my Linux machines. Should I expect any further updates on this?

[pramet]

I am experiencing similar issues using Fusion 12.1. I built a fresh VM with Windows 10 20H2 and enable WSL2 with Debian. My host is a MBP 13 2016 core i7 (provide 8Go RAM and 2 cores for the guest in Fusion). Overall performance in WSL2 is very bad (while I was pretty happy with the performance under Catalina). Performances without nested virtualization in Win10 VM are also downgraded, it seems better if I disable VT-x option but WSL2 will no longer work.

[ddung99]

Hi,

I Have the same issue,  Bug Sur + Vmware fusion 12.  When I try to run qemu images the node  crash. Is there any workaround or patch?.

Regards

[m0leX]

the only one that i've found was downgrading to 10.15.7

[ddung99]

Hi M0leX,

Thanks for  your reply, As you say,  seems that the only way is to  downgrade to Catalina.  I'm not sure if the issue is the changes on Big Sur virtualization framework or VMware Fusion. The notes in fusion 12 says that nested virtualization is supported but  in my case doesn't work.

Regards

[m0leX]

np

check if your CPU supports VMCS "shadowing" 

more here https://communities.vmware.com/t5/VMware-Fusion-Discussions/Attempting-to-do-nested-virtualization/t...

[sandervanvugt]

With the help of VMware support, I have my issues fixed - yeah. What you should do: Use AppCleaner: https://freemacsoft.net/appcleaner/ to completely remove Fusion 12.0 or 12.1 (notice that this does not remove your VM's). Next, just reinstall Fusion 12.1. For me that was all that was needed to get nested virtualisation working again. And I have no complaints about the performance. 

[pramet]

Here is the both (Host and Guest) parts regarding VMCS in my wmware.log. VMCS seems only enabled on the Host...

```

2020-12-02T09:51:36.034+01:00| vmx| I005: Host VT-x Capabilities:
2020-12-02T09:51:36.034+01:00| vmx| I005: Basic VMX Information (0x00da040000000004)
2020-12-02T09:51:36.034+01:00| vmx| I005: VMCS revision ID 4
2020-12-02T09:51:36.034+01:00| vmx| I005: VMCS region length 1024
2020-12-02T09:51:36.034+01:00| vmx| I005: VMX physical-address width natural
2020-12-02T09:51:36.034+01:00| vmx| I005: SMM dual-monitor mode yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Advanced INS/OUTS info yes
2020-12-02T09:51:36.034+01:00| vmx| I005: True VMX MSRs yes
2020-12-02T09:51:36.034+01:00| vmx| I005: VMCS memory type WB
2020-12-02T09:51:36.034+01:00| vmx| I005: True Pin-Based VM-Execution Controls (0x0000007f00000016)
2020-12-02T09:51:36.034+01:00| vmx| I005: External-interrupt exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: NMI exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Virtual NMIs {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Activate VMX-preemption timer {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Process posted interrupts { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: True Primary Processor-Based VM-Execution Controls (0xfff9fffe04006172)
2020-12-02T09:51:36.034+01:00| vmx| I005: Interrupt-window exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Use TSC offsetting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: HLT exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: INVLPG exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: MWAIT exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: RDPMC exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: RDTSC exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: CR3-load exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: CR3-store exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: CR8-load exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: CR8-store exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Use TPR shadow {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: NMI-window exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: MOV-DR exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Unconditional I/O exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Use I/O bitmaps {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Monitor trap flag {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Use MSR bitmaps {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: MONITOR exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: PAUSE exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Activate secondary controls {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Secondary Processor-Based VM-Execution Controls (0x00115cef000000a2)
2020-12-02T09:51:36.034+01:00| vmx| I005: Virtualize APIC accesses {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Enable EPT { 1 }
2020-12-02T09:51:36.034+01:00| vmx| I005: Descriptor-table exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Enable RDTSCP {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Virtualize x2APIC mode { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: Enable VPID { 1 }
2020-12-02T09:51:36.034+01:00| vmx| I005: WBINVD exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Unrestricted guest { 1 }
2020-12-02T09:51:36.034+01:00| vmx| I005: APIC-register virtualization { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: Virtual-interrupt delivery { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: PAUSE-loop exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: RDRAND exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Enable INVPCID {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Enable VM Functions { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: Use VMCS shadowing {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: ENCLS exiting { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: RDSEED exiting {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Enable PML { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: EPT-violation #VE { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: Enable XSAVES/XRSTORS {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Mode-based execute control for EPT { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: Use TSC scaling { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: Enable ENCLV in VMX non-root mode { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: Enable EPC Virtualization Extensions { 0 }
2020-12-02T09:51:36.034+01:00| vmx| I005: True VM-Exit Controls (0x01ffffff00036dfb)
2020-12-02T09:51:36.034+01:00| vmx| I005: Save debug controls {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Host address-space size {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Load IA32_PERF_GLOBAL_CTRL {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Acknowledge interrupt on exit {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Save IA32_PAT {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Load IA32_PAT {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Save IA32_EFER {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Load IA32_EFER {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Save VMX-preemption timer {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: True VM-Entry Controls (0x0003ffff000011fb)
2020-12-02T09:51:36.034+01:00| vmx| I005: Load debug controls {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: IA-32e mode guest {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Entry to SMM {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Deactivate dual-monitor mode {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Load IA32_PERF_GLOBAL_CTRL {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Load IA32_PAT {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: Load IA32_EFER {0,1}
2020-12-02T09:51:36.034+01:00| vmx| I005: VPID and EPT Capabilities (0x00000f0106334141)
2020-12-02T09:51:36.034+01:00| vmx| I005: R=0/W=0/X=1 yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Page-walk length 3 yes
2020-12-02T09:51:36.034+01:00| vmx| I005: EPT memory type WB yes
2020-12-02T09:51:36.034+01:00| vmx| I005: 2MB super-page yes
2020-12-02T09:51:36.034+01:00| vmx| I005: 1GB super-page yes
2020-12-02T09:51:36.034+01:00| vmx| I005: INVEPT support yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Access & Dirty Bits yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Advanced VM exit information for EPT violations no
2020-12-02T09:51:36.034+01:00| vmx| I005: Type 1 INVEPT yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Type 2 INVEPT yes
2020-12-02T09:51:36.034+01:00| vmx| I005: INVVPID support yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Type 0 INVVPID yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Type 1 INVVPID yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Type 2 INVVPID yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Type 3 INVVPID yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Miscellaneous VMX Data (0x000000007004c1e7)
2020-12-02T09:51:36.034+01:00| vmx| I005: TSC to preemption timer ratio 7
2020-12-02T09:51:36.034+01:00| vmx| I005: VM-Exit saves EFER.LMA yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Activity State HLT yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Activity State shutdown yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Activity State wait-for-SIPI yes
2020-12-02T09:51:36.034+01:00| vmx| I005: CR3 targets supported 4
2020-12-02T09:51:36.034+01:00| vmx| I005: Maximum MSR list size 512
2020-12-02T09:51:36.034+01:00| vmx| I005: Allow all VMWRITEs yes
2020-12-02T09:51:36.034+01:00| vmx| I005: Allow zero instruction length yes
2020-12-02T09:51:36.034+01:00| vmx| I005: MSEG revision ID 0
2020-12-02T09:51:36.034+01:00| vmx| I005: Processor trace in VMX yes
2020-12-02T09:51:36.034+01:00| vmx| I005: VMX-Fixed Bits in CR0 (0x0000000080000021/0x00000000ffffffff)
2020-12-02T09:51:36.034+01:00| vmx| I005: Fixed to 0 0xffffffff00000000
2020-12-02T09:51:36.034+01:00| vmx| I005: Fixed to 1 0x0000000080000021
2020-12-02T09:51:36.035+01:00| vmx| I005: Variable 0x000000007fffffde
2020-12-02T09:51:36.035+01:00| vmx| I005: VMX-Fixed Bits in CR4 (0x0000000000002000/0x00000000003767ff)
2020-12-02T09:51:36.035+01:00| vmx| I005: Fixed to 0 0xffffffffffc89800
2020-12-02T09:51:36.035+01:00| vmx| I005: Fixed to 1 0x0000000000002000
2020-12-02T09:51:36.035+01:00| vmx| I005: Variable 0x00000000003747ff
2020-12-02T09:51:36.035+01:00| vmx| I005: VMCS Enumeration (0x000000000000002e)
2020-12-02T09:51:36.035+01:00| vmx| I005: Highest index 0x17
2020-12-02T09:51:36.035+01:00| vmx| I005: VM Functions (0x0000000000000000)

```

```

2020-12-02T09:51:37.056+01:00| vmx| I005: Guest VT-x Capabilities:
2020-12-02T09:51:37.056+01:00| vmx| I005: Basic VMX Information (0x00d8100000000001)
2020-12-02T09:51:37.056+01:00| vmx| I005: VMCS revision ID 1
2020-12-02T09:51:37.056+01:00| vmx| I005: VMCS region length 4096
2020-12-02T09:51:37.056+01:00| vmx| I005: VMX physical-address width natural
2020-12-02T09:51:37.056+01:00| vmx| I005: SMM dual-monitor mode no
2020-12-02T09:51:37.056+01:00| vmx| I005: Advanced INS/OUTS info yes
2020-12-02T09:51:37.056+01:00| vmx| I005: True VMX MSRs yes
2020-12-02T09:51:37.056+01:00| vmx| I005: VMCS memory type WB
2020-12-02T09:51:37.056+01:00| vmx| I005: True Pin-Based VM-Execution Controls (0x0000003f00000016)
2020-12-02T09:51:37.056+01:00| vmx| I005: External-interrupt exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: NMI exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Virtual NMIs {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Activate VMX-preemption timer { 0 }
2020-12-02T09:51:37.056+01:00| vmx| I005: Process posted interrupts { 0 }
2020-12-02T09:51:37.056+01:00| vmx| I005: True Primary Processor-Based VM-Execution Controls (0xf7f9fffe04006172)
2020-12-02T09:51:37.056+01:00| vmx| I005: Interrupt-window exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Use TSC offsetting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: HLT exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: INVLPG exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: MWAIT exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: RDPMC exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: RDTSC exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: CR3-load exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: CR3-store exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: CR8-load exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: CR8-store exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Use TPR shadow {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: NMI-window exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: MOV-DR exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Unconditional I/O exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Use I/O bitmaps {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Monitor trap flag { 0 }
2020-12-02T09:51:37.056+01:00| vmx| I005: Use MSR bitmaps {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: MONITOR exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: PAUSE exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Activate secondary controls {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Secondary Processor-Based VM-Execution Controls (0x00111cfe00000000)
2020-12-02T09:51:37.056+01:00| vmx| I005: Virtualize APIC accesses { 0 }
2020-12-02T09:51:37.056+01:00| vmx| I005: Enable EPT {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Descriptor-table exiting {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Enable RDTSCP {0,1}
2020-12-02T09:51:37.056+01:00| vmx| I005: Virtualize x2APIC mode {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Enable VPID {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: WBINVD exiting {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Unrestricted guest {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: APIC-register virtualization { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: Virtual-interrupt delivery { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: PAUSE-loop exiting {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: RDRAND exiting {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Enable INVPCID {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Enable VM Functions { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: Use VMCS shadowing { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: ENCLS exiting { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: RDSEED exiting {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Enable PML { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: EPT-violation #VE { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: Enable XSAVES/XRSTORS {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Mode-based execute control for EPT { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: Use TSC scaling { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: Enable ENCLV in VMX non-root mode { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: Enable EPC Virtualization Extensions { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: True VM-Exit Controls (0x003fffff00036dfb)
2020-12-02T09:51:37.057+01:00| vmx| I005: Save debug controls {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Host address-space size {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Load IA32_PERF_GLOBAL_CTRL {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Acknowledge interrupt on exit {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Save IA32_PAT {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Load IA32_PAT {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Save IA32_EFER {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Load IA32_EFER {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Save VMX-preemption timer { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: True VM-Entry Controls (0x0000f3ff000011fb)
2020-12-02T09:51:37.057+01:00| vmx| I005: Load debug controls {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: IA-32e mode guest {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Entry to SMM { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: Deactivate dual-monitor mode { 0 }
2020-12-02T09:51:37.057+01:00| vmx| I005: Load IA32_PERF_GLOBAL_CTRL {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Load IA32_PAT {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: Load IA32_EFER {0,1}
2020-12-02T09:51:37.057+01:00| vmx| I005: VPID and EPT Capabilities (0x00000f0106114041)
2020-12-02T09:51:37.057+01:00| vmx| I005: R=0/W=0/X=1 yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Page-walk length 3 yes
2020-12-02T09:51:37.057+01:00| vmx| I005: EPT memory type WB yes
2020-12-02T09:51:37.057+01:00| vmx| I005: 2MB super-page yes
2020-12-02T09:51:37.057+01:00| vmx| I005: 1GB super-page no
2020-12-02T09:51:37.057+01:00| vmx| I005: INVEPT support yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Access & Dirty Bits no
2020-12-02T09:51:37.057+01:00| vmx| I005: Advanced VM exit information for EPT violations no
2020-12-02T09:51:37.057+01:00| vmx| I005: Type 1 INVEPT yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Type 2 INVEPT yes
2020-12-02T09:51:37.057+01:00| vmx| I005: INVVPID support yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Type 0 INVVPID yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Type 1 INVVPID yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Type 2 INVVPID yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Type 3 INVVPID yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Miscellaneous VMX Data (0x00000000400401e0)
2020-12-02T09:51:37.057+01:00| vmx| I005: TSC to preemption timer ratio 0
2020-12-02T09:51:37.057+01:00| vmx| I005: VM-Exit saves EFER.LMA yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Activity State HLT yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Activity State shutdown yes
2020-12-02T09:51:37.057+01:00| vmx| I005: Activity State wait-for-SIPI yes
2020-12-02T09:51:37.057+01:00| vmx| I005: CR3 targets supported 4
2020-12-02T09:51:37.057+01:00| vmx| I005: Maximum MSR list size 512
2020-12-02T09:51:37.057+01:00| vmx| I005: Allow all VMWRITEs no
2020-12-02T09:51:37.057+01:00| vmx| I005: Allow zero instruction length yes
2020-12-02T09:51:37.057+01:00| vmx| I005: MSEG revision ID 0
2020-12-02T09:51:37.057+01:00| vmx| I005: Processor trace in VMX no
2020-12-02T09:51:37.057+01:00| vmx| I005: VMX-Fixed Bits in CR0 (0x0000000080000021/0x00000000ffffffff)
2020-12-02T09:51:37.057+01:00| vmx| I005: Fixed to 0 0xffffffff00000000
2020-12-02T09:51:37.057+01:00| vmx| I005: Fixed to 1 0x0000000080000021
2020-12-02T09:51:37.057+01:00| vmx| I005: Variable 0x000000007fffffde
2020-12-02T09:51:37.057+01:00| vmx| I005: VMX-Fixed Bits in CR4 (0x0000000000002000/0x00000000003727ff)
2020-12-02T09:51:37.057+01:00| vmx| I005: Fixed to 0 0xffffffffffc8d800
2020-12-02T09:51:37.057+01:00| vmx| I005: Fixed to 1 0x0000000000002000
2020-12-02T09:51:37.057+01:00| vmx| I005: Variable 0x00000000003707ff
2020-12-02T09:51:37.057+01:00| vmx| I005: VMCS Enumeration (0x000000000000005a)
2020-12-02T09:51:37.057+01:00| vmx| I005: Highest index 0x2d
2020-12-02T09:51:37.057+01:00| vmx| I005: VM Functions (0x0000000000000000)

```

[pramet]

I tried to clean uninstall/reinstall Fusion, but without success. The nested virt WSL2 in Win20H2 is still very slow.

[pramet]

Here is the cpu info (sysctl -a | grep machdep.cpu) :

```

machdep.cpu.max_basic: 22
machdep.cpu.max_ext: 2147483656
machdep.cpu.vendor: GenuineIntel
machdep.cpu.brand_string: Intel(R) Core(TM) i7-6660U CPU @ 2.40GHz
machdep.cpu.family: 6
machdep.cpu.model: 78
machdep.cpu.extmodel: 4
machdep.cpu.extfamily: 0
machdep.cpu.stepping: 3
machdep.cpu.feature_bits: 9221960262849657855
machdep.cpu.leaf7_feature_bits: 43806655 0
machdep.cpu.leaf7_feature_bits_edx: 2617255424
machdep.cpu.extfeature_bits: 1241984796928
machdep.cpu.signature: 263907
machdep.cpu.brand: 0
machdep.cpu.features: FPU VME DE PSE TSC MSR PAE MCE CX8 APIC SEP MTRR PGE MCA CMOV PAT PSE36 CLFSH DS ACPI MMX FXSR SSE SSE2 SS HTT TM PBE SSE3 PCLMULQDQ DTES64 MON DSCPL VMX SMX EST TM2 SSSE3 FMA CX16 TPR PDCM SSE4.1 SSE4.2 x2APIC MOVBE POPCNT AES PCID XSAVE OSXSAVE SEGLIM64 TSCTMR AVX1.0 RDRAND F16C
machdep.cpu.leaf7_features: RDWRFSGS TSC_THREAD_OFFSET SGX BMI1 HLE AVX2 SMEP BMI2 ERMS INVPCID RTM FPU_CSDS MPX RDSEED ADX SMAP CLFSOPT IPT MDCLEAR TSXFA IBRS STIBP L1DF SSBD
machdep.cpu.extfeatures: SYSCALL XD 1GBPAGE EM64T LAHF LZCNT PREFETCHW RDTSCP TSCI
machdep.cpu.logical_per_package: 16
machdep.cpu.cores_per_package: 8
machdep.cpu.microcode_version: 220
machdep.cpu.processor_flag: 6
machdep.cpu.mwait.linesize_min: 64
machdep.cpu.mwait.linesize_max: 64
machdep.cpu.mwait.extensions: 3
machdep.cpu.mwait.sub_Cstates: 286531872
machdep.cpu.thermal.sensor: 1
machdep.cpu.thermal.dynamic_acceleration: 1
machdep.cpu.thermal.invariant_APIC_timer: 1
machdep.cpu.thermal.thresholds: 2
machdep.cpu.thermal.ACNT_MCNT: 1
machdep.cpu.thermal.core_power_limits: 1
machdep.cpu.thermal.fine_grain_clock_mod: 1
machdep.cpu.thermal.package_thermal_intr: 1
machdep.cpu.thermal.hardware_feedback: 0
machdep.cpu.thermal.energy_policy: 1
machdep.cpu.xsave.extended_state: 31 832 1088 0
machdep.cpu.xsave.extended_state1: 15 832 256 0
machdep.cpu.arch_perf.version: 4
machdep.cpu.arch_perf.number: 4
machdep.cpu.arch_perf.width: 48
machdep.cpu.arch_perf.events_number: 7
machdep.cpu.arch_perf.events: 0
machdep.cpu.arch_perf.fixed_number: 3
machdep.cpu.arch_perf.fixed_width: 48
machdep.cpu.cache.linesize: 64
machdep.cpu.cache.L2_associativity: 4
machdep.cpu.cache.size: 256
machdep.cpu.tlb.inst.large: 8
machdep.cpu.tlb.data.small: 64
machdep.cpu.tlb.data.small_level1: 64
machdep.cpu.address_bits.physical: 39
machdep.cpu.address_bits.virtual: 48
machdep.cpu.core_count: 2
machdep.cpu.thread_count: 4
machdep.cpu.tsc_ccc.numerator: 200

```

[m0leX]

i'd like to get some sort of official note from VMware regarding this solution. i won't take the risk of making my Mac basically unusable

[gringley]

Agreed.  AppCleaner deleted a lot of files but I was not prompted for Privacy or the driver so not sure it really was a clean uninstall either?  I saw no difference in performance.

[m0leX]

are we going to see some official note from VMware on this issue?

[mlippold1]

Are we going to get someone from VMWare to officially confirm that this is a real problem (I assure you that it is) or should everyone that uses nested vms/virtualization based security start heading to another product?