Resolution path for fixing Hyper-V VM migraton from a host in one domain to a host in another domain

VMware ESX admins have to pay attention to host swap file sizes because you can overcommit on memory. With Hyper-V, you can't overcommit on memory - for example, you can't take a host with 16gb of ram and start up 8 guests with 4gb of ram each. There's pros and cons to that approach. In a nutshell, though, you're right in saying it shouldn't need a host file - as long as you don't run anything on the host other than Hyper-V guests. If you remote desktop in and run things, or if you run third party backup or antivirus software on the host, you should set up a page file just to be safe. I've seen instances where people RDP into the host and run a backup software console written in Java, for example, and it needs gigs of memory in order to start & run a restore operation.

I've read that it is supported too but never had any luck with it, myself. Sorry I'm no help there. Instead, I had to do this to migrate VMs from VS2005 to Hyper-V:

1. Uninstall the integration bits from the VM on VS2005. Plan this out because you lose mouse control.

2. Shut down VM in VS2005.

3. Create new VM with the same CPU, memory, name, and no disks in Hyper-V.

4. Copy the VHD file(s) from VS2005 to the new VM directory on the Hyper-V server.

5. Edit the VM in Hyper-V to point to the VHD file(s).

6. Start the VM in Hyper-V and immediately install the integration bits.

This isn't anything magical - a VM in VS2005 and Hyper-V is simply made up of an XML config file and the VHD files. Moving a VM manually like this works fine between VS2005 and Hyper-V and also between Hyper-V servers when you either don't have SCVMM or can't for some reason use the Hyper-V import/export feature (it does seem to fail sometimes). I've actually found that learning how to do a manual move is a good practice - you learn a lot about how things work under the hood so you are better able to deal with emergencies.

I know this isn't the solution you were looking for and you can probably find more comprehensive explanations of manual moves via Google, but perhaps it will be of some assistance. Good luck.