Hi everyone,
I'm hoping to get some help that might point me in the right direction to solve a big problem with one of my host Hyper-V servers.
My host has 4 NICs and three out of the four are assigned to be used in Hyper-V. The other day, I needed to add a VM to that host and I assigned an unused NIC (vNIC2) to the new VM. I found the VM could not get on-line so I started digging deeper. The other 3 NICs are working fine. Only vNIC2 is non-functional. Hyper-V isn't showing any issue with it, but it doesn't pass any data. Eventually I got around to checking the Device Manager of the host. Under network adapters, I find two issues:
1)Hyper-V Virtual Switch Extension Adapter
This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)
An object ID was not found in the file.
2) Microsoft Hyper-V Network Switch Default Miniport
An object ID was not found in the file.
I tried to reload drivers but it tells me the best driver is already installed.
I had read somewhere to try and remove the virtual switch from the virtual switch manager and then re-add it. I got a blue screen of the host each time I tried to remove a vNIC from the virtual switch manager. That was real bad. I have 4 production VMs on this host that I can't afford to lose. All the VMs use local storage and one is a mail server with 1TB of data. I don't think it's safe to do a live migration of the mail server to allow me to take this host off-line and rebuild Hyper-V. So, I'm looking to fix it in place. Does anyone have experience with this?
Hyper-V host is a Supermicro server with 3 different RAID 10 arrays. 1- Host OS 2- VMs 3- Mail store
64 GB of memory, 2 processors, 16 cores each @ 2.6GHZ
Server 2012R2 - fully updated
I did run bluescreen view and got
driver: ntoskrnl.exe
Address: ntoskrnl.exe+14f9a0
I don't think that show anything that is helpful so I zipped the dump files in case anyone knows how to read them.
I really appreciate the help.