[HYPER-V] Sudden problem with Hyper-V Machines

[Disease]

Hi all,

 

Had a sudden problem start on one of my Hyper-V hosts.

 

3 of the VM's fail their Veeam backup as they are now unable to create check points, when you try to create a checkpoint on the Hyper-V for the VM it just fails with just a generic error:

 

 

When I try and make a new virtual machine I get the following error:

 

 

Other than that the existing VMs run fine and can be rebooted fine and looking through event viewer doesn't really shed any further light.

 

Anyone able to offer any advice?

 

TIA

[round2it]

Clustered?

[Steve21]

Normally that suggests the default HyperV filestore folder is missing. What's it set to in hyperV and does it still exist ok/permissions etc?

 

Steve

[Disease]

Clustered?

 

Used to be but the VMs are no longer highly available, the host is still a node in the cluster though.

[Disease]

Normally that suggests the default HyperV filestore folder is missing. What's it set to in hyperV and does it still exist ok/permissions etc?

 

Steve

 

I noticed that the path for the VHD was to a different folder that the VM folder I changed it and am now able to make VM's again, for now . Just the checkpoint issue now.

[Steve21]

I mean checkpoints can be a lot of things, but the main few to check normally would be, the real event logs linked to VMMS service to see the error details.

 

Are the integration/VSS services running within the VM if it's using app aware within Veeam?

 

Based on the wrong folder being used for hyperv, have permissions been changed around on the VM folders at all? As you may need to reset VM permissions back to create AVHDXs again

 

Steve

[Disease]

I mean checkpoints can be a lot of things, but the main few to check normally would be, the real event logs linked to VMMS service to see the error details.

 

Are the integration/VSS services running within the VM if it's using app aware within Veeam?

 

Based on the wrong folder being used for hyperv, have permissions been changed around on the VM folders at all? As you may need to reset VM permissions back to create AVHDXs again

 

Steve

 

Thanks Steve, not sure if I am honest I have deleted and recreated the VMs a couple of times from the VHDs, some of the VM folders have checkpoint folders with check points in but these are from the old VM IDs before I re-created them no VM's show as having any checkpoints in hyper-v

[Steve21]

So like if you look at the security on the folder for that VM it should have a long GUID like S-15-3... and a Virtual Machines permission set

 

Then on the individual VHDXs etc it should have the VM guids e.g. Get-VM 'MYVM' | Select-Object VMID

 

Steve

[Disease]

So like if you look at the security on the folder for that VM it should have a long GUID like S-15-3... and a Virtual Machines permission set

 

Then on the individual VHDXs etc it should have the VM guids e.g. Get-VM 'MYVM' | Select-Object VMID

 

Steve

 

All seems to match up apart from on the VHD which has a missing GUID which I assume is from the old VM id before I re-created it.

[Disease]

The permissions are screwed on some for example this shows the vm having only read permissions to the VHDX file:

 

 

When I try and give the VM id full control I just get this error:

 

 

 

Is there anyway to reset the permissions on the VM's without rebuilding Hyper-V on the server?

[Steve21]

That SID isn't an old one - S-1-15-3-1024-2268835264-3721307629-241982045-173645152-1490879176-104643441-2915960892-1612460704 etc that's a prebuilt HyperV one that should exist

 

You should be able to use icalcs to reset the one you're talking about, but if you're missing the other HyperV SID it looks like something odds happened to that server...

 

icacls "E:\...\Disk-C.vhdx" /grant "NT VIRTUAL MACHINE\MY_VM_GUID":(F)

[Disease]

That SID isn't an old one - S-1-15-3-1024-2268835264-3721307629-241982045-173645152-1490879176-104643441-2915960892-1612460704 etc that's a prebuilt HyperV one that should exist

 

You should be able to use icalcs to reset the one you're talking about, but if you're missing the other HyperV SID it looks like something odds happened to that server...

 

icacls "E:\...\Disk-C.vhdx" /grant "NT VIRTUAL MACHINE\MY_VM_GUID":(F)

 

Thanks Steve, will do some research on how to add that SID back in if possible otherwise I may have to remove hyper-v and reinstall it.