VMM 2022 vmswitch.sys and BSOD

Latif Yahya 31 Reputation points
2023-03-17T13:04:35.3733333+00:00

We've encountered an issue with the PowerEdge R730xd running Windows Server 2022 DC as a Hyper-V host as a first host, where the server crashes and reboots due to logical switch settings in System Center Virtual Machine Manager 2022.

The host has four onboard NICs (2 x Intel Gigabit 4P X540/I350 & 2 x Intel 10GB 4P X540/I360).

Two Gigabit ports are teamed and used as host NICs, while the two 10GB ports are connected to a switch as trunked NICs with LACP enabled.

After configuring the logical switch and assigning it to the Host, powering up the VM causes the host to blue screen with a 'vmswitch.sys' issue.

Unless the VM is configured not to restart, it continuously blue screens and reboots.

We've ensured the NIC's are running the latest BIOS and all other server components are up-to-date with the latest drivers from Dell, but the issue persists.

Currently only way to get this to work is if we configure the LACP on the local host and get VMM to use this instead on VMM taking over and managing the teaming.

I would be interested to know how this should be configured if what I am doing is not correct as with the previous versions of VMM, this is pretty much how we have been configuring this.

Thanks.

System Center Virtual Machine Manager
Windows Server
Windows Server
A family of Microsoft server operating systems that support enterprise-level management, data storage, applications, and communications.
12,119 questions

3 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Deleted

    This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

    Comments have been turned off. Learn more

  2. Gabrie van Zanten 5 Reputation points
    2023-05-26T06:56:01.0766667+00:00

    @joshlangley Wow, that made a change. Think it works now. At least I can use new-vmswitch to create a new switch. This usually caused a BSOD when running that command. Will be testing this with VMs now.

    Would you have some more info on why this is needed? In my UCS NIC profile I also have VMQ enabled, should I disable it there as well?

    For others: I used this command to disable VMQ:

     get-NetAdapterAdvancedProperty | Where-Object {$_.RegistryKeyword -like "*VMQ*"} | Set-NetAdapterAdvancedProperty -DisplayName "Virtual Machine Queues" -RegistryValue 0 

    1 person found this answer helpful.
  3. Robert Eriksson 1 Reputation point
    2023-11-10T10:19:18.3733333+00:00

    Hi, we had similar problem this week, on a 2019 server tho. After patching MS October patches 2023-10 the server BSOD pointing to vmswitch.sys.
    MS Support found that RSS had been enabled on one of our NICs. setting that to 0 we could enable VMQ again without BSOD. No RCA yet.
    Server is a HPE Proliant DL360 Gen10 with 10Gb 2p 535FLR-T nic.

    Regards
    Rob