When moving around vhdx-files for Hyper-V machines the machine might get in a disconnected mode. Words like catastrophic failure and disconnected state where thrown around.
Well, Ive removed the files. I know nothing important is missing and I just want the vm gone from my HyperV Manager Console.
Didn’t work with powershell, remove-vm –name “bloodymachine” , gets error about state. This worked though:
- Stop Hyper-V services from HyperV Manager
- Go to : C:\Programdata\microsoft\windows\hyper-v\virtual machines and delete the GUID that is associated with the machine. If you don’t know find the GUID, just check created date. Really only recommended in a lab-environment.
- Start Hyper-V services and the menacing machine is vanquished
For really finding out GUID check out references
References:
http://blogs.technet.com/b/m2/archive/2008/07/04/how-to-get-the-bios-guid-from-a-hyper-v-vm.aspx?ppud=4&wa=wsignin1.0 – finding out GUID HyperV
http://www.petri.co.il/get-hyper-v-virtual-machine-process-id-and-guid.htm – more GUID exploration guides.
No comments:
Post a Comment