1

Hi guys

Running hyper v 2012 did windows update over the weekend and surprise surprise can’t start couple of vms now.

I have two nodes both have same patches applied to it.

I have managed to start all of my vms except 2 I’m keep getting the following errors under cluster events

Event ID : 1254 1205 1069 and 1254

Both nodes can access quorum and shared volumes so don’t know what could be causing the issue any idea guys ?

7 Spice ups
2

If you use PowerShell and use the Start-VM cmdlet, and specify the -Verbose switch - what error messages do you see.?

2 Spice ups
3

Check for .avhd files in the hard disk directory. Your backup software may have created snapshots and they are failing to merge for some reason. You can try and restart the Hyper-V Management service on the host and try and start it again.

1 Spice up
4

When I run Get-vm command it doesn’t show the 2 vms with issue so start-vm doesn’t command work either.

joshkrawczyk - I have restarted VMMS services few times and checked there is no snapshot.I copied the virtual disk to my hyper V test environment and managed to mount it fine.What if I delete the both vm and create new one and add the attached the virtual disk to it.Keep mind one of them is a DC it runs DHCP but doesn’t have any FSMO roles.would there be any sync issue between the two DC’s once this is back online ?

5

That shouldn’t be a problem. Since the VMs are part of a cluster, have you tried moving them to another host?

I came across an issue last week when I had 4 VMs backups start failing after patching them. I attempted live migrating them and got an error saying that the VM was locked. I attempted shutting them down via cluster manager and got the same error. I had to actually reboot the host to get everything to function.

6

Yea I have 2 nodes tried on both can’t start it still start.
I have a feeling the xml file is corrupted and that’s why I can’t see it.

My other current working DC is on another cluster so if I create this one with the issue and mount it there shouldn’t be a problem ?

My concern is the new vm would have new guid and MAC address is something that can cause a problem or na ?

7

That shouldn’t be an issue. The Mac addresses change regularly in a cluster because moving vm’s between nodes will change it. (Unless they are statically set).

8

Thank Josh the server is been online for more than 24 hours now I think I’m gonna give up and just create a new vm and attach the disk to it I’ll let you know how I go.
Thanks for your response man.

9

All good now guys had to build a new vm and add the vdisk.