Tuesday, April 21, 2009

Scenarios I faced between Hyper-V R2 Beta and Hyper-V v1

While testing out Windows Server 2008 R2 Beta with Hyper-V in our environment, we noticed a few scenarios that had some incompatibilities.

  1. We had 3 VMs in a Saved State on a server with Hyper-V v1 and proceeded to upgrade the OS. After the upgrade was sucessfully complete, the VMs could not be recovered from its Saved State. The Saved State had to be deleted. Once that was done, the VMs started out fine
  2. We Exported a VM from a Hyper-V v1 server. The VM contained snapshots and proceeded to Import it into the Hyper-V R2 Beta server. The VM would not import and contain errors. We proceeded to remove the snapshot and imported it again
  3. We Exported a VM from a Hyper-V v1 server. The VM did not contain any snapshots and was in an Off state. When we imported it to the Hyper-V R2 Beta server, the VM could start but when Connecting to the VM, the screen was simply black. We proceeded to create a new VM with the exisiting Hard Disk and it worked fine
  4. After Importing a VM into Hyper-V R2 server from a Hyper-V v1 server, the Network connection was Disabled. Enabling it would not work. We proceeded to Re-install the Integration Services and the Network connection was working again. I suspect it was because of a different version of Integration Services.

I will be adding to this list as I go along. I hope these issues will be fixed at RTM.

No comments: