WilliamLam.com

  • About
    • About
    • Privacy
  • VMware Cloud Foundation
  • VKS
  • Homelab
    • Resources
    • Nested Virtualization
  • VMware Nostalgia
  • Apple
You are here: Home / Nested Virtualization / vSphere 8.0 Update 1c resolves Windows VBS performance & Hyper-V Generation 2 Nested VM running on AMD CPU

vSphere 8.0 Update 1c resolves Windows VBS performance & Hyper-V Generation 2 Nested VM running on AMD CPU

07.28.2023 by William Lam // 1 Comment

🆕 vSphere 8.0 Update 1c is now available! Includes support for TKr 1.25.7 🥳

📔RN
VC https://t.co/4y2s91PcKY
ESXi https://t.co/RYI0gz7vtf
TKr https://t.co/KiarKzkQs0

💿 DL
VC https://t.co/w0cyBErTiC
ESXi https://t.co/MuCPqieXY3

— William Lam (@lamw.bsky.social | @*protected email*) (@lamw) July 28, 2023

vSphere 8.0 Update 1c was just released and one of the resolved issues mentioned in the ESXi release notes is the following:

Nested virtual machines on AMD CPUs with operational systems such as Windows with virtualization-based security (VBS) might experience performance degradation, timeouts, or unresponsiveness due to an issue with the virtualization of AMD's Rapid Virtualization Indexing (RVI), also known as Nested Page Tables (NPT).

UPDATE (10/11/23) - This is also resolved in the ESXi 7.0 Update 3o release

There are two scenarios in which this fix resolves:

  1. Running Windows Server VM with a Hyper-V enabled Generation 2 VM (Nested Virtualization) on AMD CPU
  2. Running Windows Server VM with VBS Enabled (Non-Nested VM) on AMD CPU

The original issue that was reported in the VMTN Community, which I had filed an internal bug report with Engineering, is related to the first scenario. The reported issue was that when a user would power on a Hyper-V Generation 2 VM (Nested) running in a Windows Server VM hosted on an AMD CPU, the inner-VM would not boot and simply show a blank screen.


If the user switched to a Generation 1 Hyper-V VM, then the VM would boot up properly. Furthermore, this issue was not observed when using an Intel CPU and both Generation 1 and 2 Hyper-V VMs were functional.

In the second scenario, we also had reports from some customers that they had noticed a performance degradation when running a Windows Server VM with just Microsoft Virtualization Based Security (VBS) enabled and they were not running any Hyper-V VM inside.

Both scenario 1 and 2 are related since the way VBS is implemented by Microsoft, it is actually using a Hyper-V VM and this is also why you may have noticed Virtual Hardware Virtualization (VHV) setting automatically enabled when you configure a Windows VM with the VBS setting.

For customers that are on vSphere 8.x and affected by this issue, you can resolve this by installing the latest ESXi 8.0 Update 1c patch. For customers on vSphere 7.x, a similiar fix will also be available in a future ESXi patch update, so stay tuned.

More from my site

  • Quick Tip - Virtualized Intel VT-x/EPT or AMD-V/RVI is not supported on this platform for VMware Workstation
  • Quick Tip: New Hyper-V guestOS identifier in vSphere 5.5
  • Will Intel’s VMCS Shadowing Feature Benefit VMware’s Nested Virtualization?
  • ESXi on GMKtec EVO-X1 with AMD Ryzen AI Pro 300 Series (formally Strix Point)
  • Refresher on Nested ESXi Networking Requirements

Categories // Nested Virtualization, vSphere 8.0 Tags // AMD, hyper-v, nested virtualization, VBS, vSphere 8.0 Update 1c

Comments

  1. *protectedJim VS says

    07/30/2023 at 8:21 am

    If you get "Hardware precheck of profile ESXi-8.0U1c-22088125-standard failed with errors: <CPU_SUPPORT ERROR: The CPU in this host is not supported by ESXi 8.0.1.", it may be because "allowLegacyCPU=true" is missing from the kernelopts line in one or both BOOTBANK boot.cfg files. After I added that back to the file(s), the CLI update completed as expected. I didn't need to reboot for the fix to take effect. This worked on two pairs of Intel NUCs and an AMD FX-8350 YMMV

    Reply

Thanks for the comment!Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Thank Author

Author

William is Distinguished Platform Engineering Architect in the VMware Cloud Foundation (VCF) Division at Broadcom. His primary focus is helping customers and partners build, run and operate a modern Private Cloud using the VMware Cloud Foundation (VCF) platform.

Connect

  • Bluesky
  • Email
  • GitHub
  • LinkedIn
  • Mastodon
  • Reddit
  • RSS
  • Twitter
  • Vimeo

Recent

  • VMUG Connect 2025 - Minimal VMware Cloud Foundation (VCF) 5.x in a Box  05/15/2025
  • Programmatically accessing the Broadcom Compatibility Guide (BCG) 05/06/2025
  • Quick Tip - Validating Broadcom Download Token  05/01/2025
  • Supported chipsets for the USB Network Native Driver for ESXi Fling 04/23/2025
  • vCenter Identity Federation with Authelia 04/16/2025

Advertisment

Privacy & Cookies: This site uses cookies. By continuing to use this website, you agree to their use.
To find out more, including how to control cookies, see here: Cookie Policy

Copyright WilliamLam.com © 2025

 

Loading Comments...