HYPER-V move the folder and Virtual Disks (temporarily)

[Koldov]

Just wanted to check how involved this might be...

 

I want to format the VM Host's data disk from MBR and switch it to GPT... there isn't much else on the disk luckily, but it does have the Hyper-V folder.

 

Am I going to get away with shutting down the Hyper-V machines, copying the whole folder somewhere else, wiping and formatting the disk into GPT, copying the folder back and starting the machines...?

 

Or does there need to be something more involved such as detaching disks, stopping services etc?

Edited January 8, 2023 by Koldov

[Bedders]

If it were me, I'd Export the virtual machine(s) from within Hyper-V, onto a SAN or other external storage.

Then wipe the server, reinstall Windows and the Hyper-V role, then Import the VM(s).

[chaplic]

Ive shuffled Hyper-V VMs between various disks and the like when sorting out disk space issues in my lab, never had any drama. I think your plan is fine, obviously assuming you dont have directly mapped disks.

[Koldov]

If it were me, I'd Export the virtual machine(s) from within Hyper-V, onto a SAN or other external storage.

Then wipe the server, reinstall Windows and the Hyper-V role, then Import the VM(s).

 

It's on a separate data disk to the OS.

 

Ive shuffled Hyper-V VMs between various disks and the like when sorting out disk space issues in my lab, never had any drama. I think your plan is fine, obviously assuming you dont have directly mapped disks.

 

Maybe there is a point in-between that doesn't involve completely reinstalling the Server OS, but also doesn't actually cause me to feel slightly hot and dizzy when neither VM starts due to errors....

 

Bit of a close call... turns out you should choose a copy/move method that retains all permissions on the VHDx!

 

https://learn.microsoft.com/en-US/troubleshoot/windows-server/virtualization/hyper-v-virtual-machine-not-start-0x80070005

[msi_school]

It's on a separate data disk to the OS.

 

 

 

Maybe there is a point in-between that doesn't involve completely reinstalling the Server OS, but also doesn't actually cause me to feel slightly hot and dizzy when neither VM starts due to errors....

 

Bit of a close call... turns out you should choose a copy/move method that retains all permissions on the VHDx!

 

https://learn.microsoft.com/en-US/troubleshoot/windows-server/virtualization/hyper-v-virtual-machine-not-start-0x80070005

 

Been there its not a nice feeling but is fairly simple to fix.