MS Virtual Server files to Hyper-v

[Guest Briano]

I have read and re-read the GroovyPost concerning migrating VS 2005 R2 VMs to Hyper-v. Unfortunately I seem to have lots of problems. I have been successful a couple of times but in general I can't get it to work. Also new machines will set up OK.

 

This is a full enterprise version of Server 2008. KB949219 is installed. Also the new refresh of the beta Hyper-v just released this week (May 19/08) In general, the error is described below. I have made no attempt to pre-condition the VHD files while they are operating in the VS 2005 environment. They are production files and I don't want more problems. So I have simply copied them to the new server and I am attempting to get them to operate.

 

Error is: The server encountered an error while configuring memory on (Virtual Server name). Wizard failed in rolling back the created virtual machine. Please delete it manually afterwards. Failed to add device "Microsoft Synthetic Ethernet Port".

 

The VM actually gets created but it won't boot and fails to start with a Boot failure error.

 

Hopefull someone has an idea what the problem might be. I would sure appreciate it.

 

Thanks, Brian

Edited November 8, 2008 by Briano

[Guest Briano]

I tried to pre-condition the file I am trying to move by deleting the Virtual Server additions.

 

The file I am using had 2 network adapters and using 'Network not connected" options I was getting 'failed to add device - Microsoft Synthetic Ethernet Port'

 

So I choose the two virtual network adapters I had set up. Now I am getting errors 'failed to power on with error - the specified network resource is no longer available'.

 

As I said previously, I would sure appreciate any help I can get.

 

Thanks

 

Brian

[Steve Krause]

 

As I said previously, I would sure appreciate any help I can get.

Thanks

 

Brian

 

Hi Brian,

 

Hopefully I can give you a hand however, without a copy of the VM's it's going to be hard to troubleshoot this for you but I'll do my best.

 

What OS is the .VHD file your migrating? I assume it's Windows 2003 SP2? Also, the errors you encounter, is it on "Startup" of the VM? Will the VM not start? Have you tried to start the VM with no Network Adapters?

 

 

Without those questions answered, try the following:

 

The first step is to take a good backup of the VM so we can play around with the config. You should also remove all the variables by uninstalling as much as you can before the migration.

 

On the VS 2005 R2 Host:

1) Shut down the guest VM and take a full backup of the Guest VM. This includes all the Virtual HD's (.vhd) and Config (.vmc) files.

2) With the Virtual Machine turned off, remove the network card from the VS 2005 R2 Console.

3) Boot up the Virtual Machine and uninstall the Virtual Machine Additions

 

So now, take the .vhd file only and copy it to your Hyper-V server and begin walking through the process of THIS groovyPost. You should be able to start on Step 1. All your doing is created a new VM on Hyper-V and using an existing .VHD file (the one you just prepped).

 

Let me know

 

Thanks!

[Guest Briano]

Thanks for your reply. I followed your instructions but every step of the way involving Hyper-V I was getting error after error. At one point I simply tried to establish a new VM with almost nothing attached, and still got errors, and I could not even delete it once it was created. I finally began to think along the lines that something was fundamentally wrong, maybe the Hyper-V was corrupted somehow or the install not finished properly, or whatever.

 

So I started fresh. New drive, new OS from an image, - same results. I began to have serious doubts about the viability of Hyper-V.

 

I placed the problem on the virtualserver newsgroup and a reply from a Microsoft MVP indicated he had similar problems with Microsoft's antivirus program. Then it struck me. My server images all contain a copy of TrendMicro OfficeScan, ver 8.0. I stopped the AV program, and all my problems immediately went away.

 

I have searched for an answer for over 2 weeks and never did I come across any reference to AV products causing this much difficulty. So, I have really learned something from this exercise. Hopefully, others will read this posting, and maybe save themselves a whole bunch of time and frustration.

 

Thanks again, for your post.

 

Brian

[Steve Krause]

I placed the problem on the virtualserver newsgroup and a reply from a Microsoft MVP indicated he had similar problems with Microsoft's antivirus program. Then it struck me. My server images all contain a copy of TrendMicro OfficeScan, ver 8.0. I stopped the AV program, and all my problems immediately went away.

Brian

 

Congrats & nice find.

 

Thanks for sharing, VERY good information!