The export/import story provided by Hyper-V by default seems to be rather restrictive.

What if the Host A has a hardware failure? I will want to transplant the hard disks where the VHDs and config files reside into Host B, right?

But then there is seemingly no way to get those guests loaded back into the Hyper-V management console. The import tool just barfs when directed to the files.

Is this a joke or am I missing something?

  • 1
    I loved "gracefully" – Pitto Feb 18 '11 at 15:43

Agreed. It's easier to just create a new VM, and mount the old guest's VHDs to the new VM.

  • 1
    I've done that in the past though and it's totally DESTROYED the network adapter configuration. Sometimes its got into an unrecoverable state where all networking connectivity is lost and no matter how many times you try to reinstall the Hyper-V NIC drivers or whatever, it is no good. – nbevans Feb 18 '11 at 15:39
  • yep, there is a way around that: windowsitpro.com/article/virtualization/… – Malnizzle Feb 18 '11 at 15:54
  • The XML hacking solution wouldn't be so bad if the file was organised in such a way that I could use a File Merge tool like P4Merge or BeyondCompare on it. But it seems every file has a wildly different schema composed of lots of GUIDs. Merging is pretty much impossible. – nbevans Feb 18 '11 at 16:24
  • I do this a lot and have never bothered with the XML editing solution. I just create the new VM without a NIC at first and boot, delete the hidden old NIC from Device Manager, then shut down, add a new NIC to the VM and boot and configure it properly. This works reliably. It seems it shouldn't be necessary to start with no NIC and delete the old one but sometimes windows seems to hang if I don't. – icky3000 Feb 18 '11 at 18:08

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.