re: VMC to Hyper-V Import Tool

Chuck vdL — Wed, 24 Sep 2008 22:49:47 GMT

Any chance we'll see something to do the reverse? there are times when testing that I'd love to take a vm snapshot, export it, discard or condense all the other snapshots, and be able to hand it off as something the developer can run under Virtual-PC

of course yes having to uninstall integration components etc.

(I guess I just need to lobby the dev manager to get them their own hyper-v host system, then I could just use the export/import capabilities to make them a copy of my VM..

re: VMC to Hyper-V Import Tool

KeBugCheck(42); — Fri, 26 Sep 2008 07:29:30 GMT

Slightly off topic but I have uncovered a sure fire way to get Physical to Hyper-V without all the HAL stuff.

1. Ghost (or Acronis) Physical box to files.

2. Run up VS 2005 and copy the image files to say the "E" drive on any NTos VM - say XP/2000/2003 running under VS 2005.

3. Boot the VS 2005 to Ghost/Acronis and "Image to disk" from E to C and D typically.

4. STOP !!! - Do NOT try and run up your VS 2005 VM - Instead, copy the vhd's to Hyper-V.

5. Create appropriate VM and "use existing" VHD's - copied from VS 2005

6. Start Hyper-V VM and WOW it just works!! :-)

7. Add integration services & Re-Activate OS with Microsoft if required. Be sure to shut down physical box and take home for the kids to play on...

I am having fun rescuing Small Business Server 2003’s from my clients failing hardware using this method.

Ben, see any traps with this? It just keeps working for me – all sorts of weird physical boxes just work when I use this method. And they keep on working…!

Details here: http://easterndigitalsoftware.com/p2v/p2v.htm