Forum Discussion
Server 2k19 Hyper-V VMs no longer start
LainRobertson No luck here.
I removed 2 NICs from the NIC team (all 4 NICs were added).
Created a new virtual switch, reassigned the NIC on the VM and tried starting it.
Same errors. 3062 for the V-Worker and 15130 for V-WMMS.
I also did recreate the vSwitch using the Multiplexor Driver as it was previously configured...
Still not go.
Last thing I tried was set the NIC of one of the VM to "Not Connected" and attempted to start... same error.
Yeah, fair enough.
As an aside, setting the NIC to disconnected won't do anything. You'd want to remove the NIC from the configuration and create a new one.
That's how I've resolved issued when using a plain old copy process to migrate guests from an old Hyper-V host to a new.
Again, it may not help in your case, but that's what I was referring to, not simply disconnecting the existing NIC.
For testing purposes, you could even try creating a new internal switch and hooking up a guest to that. If nothing else, that would serve to confirm there's nothing wrong with your multiplexor switch (i.e. if you still get the same error on the internal switch.)
Cheers,
Lain