Yes, multiple P2Vs with 2003 Ent. Did you retry the P2V system reconfig? Sometimes it doesn't work on the first try.
There's also a new version of P2V v2.1.1 you should try http://www.vmware.com/download/p2v/
We are using the P2V v2.1.1. We also tried to P2V a blade running windows 2000 and got the same results; the VM booted up fine, but the heartbeat alert went red and the keyboard and mouse did not work.
We did not retry the system reconfig. Will give that a try.
Are you running the P2V assistant inside a "helper" VM or on another physical host? Does this make any difference?
Are you running the P2V assistant inside a "helper"
VM or on another physical host? Does this make any
Makes a BIG difference. The VM Helper allows you to mount the vmdk to the helper and perform the system reconfig. In the state that you're in, you can perform the following steps:
\- Down the newly P2V'd VM
\- Attach the vmdk to the helper vm
\- Power on the helper vm
\- Execute P2V
\- Select the task "Perform a System Reconfig..."
\- Select the vmdk you just mounted
\- Select the correct info pertaining to that VM and your ESX version
After the reconfig, down the helper.
Unattach the vmdk from the helper.
Power on the VM.
Well, we tried running the system reconfig again, but the same thing happened. System boots fine, but the keyboard and mouse don't work.
Can you RDP into the server and are you using Virtual Center? If yes and yes, remote into the server, mount the VMtools install and complete the install. That should load your keyboard, mouse and other drivers.
We are using virtual center, but we cannot RDP into the VM. I believe the VM is frozen, since the heartbeat alert for the VM is red in Virtual Center. Also, the network drivers are not installed yet since we can't log into the VM to install them.
I sent a PM...
Just to let you know, I have the same problem with HS20. Most of the time, the OS just freeze at startup.
The weird part is that i have manage to restore one server and its prefectly working... but not more than that (HS20 8832). But ive never manage to restore other blade (HS20 8843).
Im using all the latest version of software P2V and ESX.
Had the same problem as you Dany.
Can't get it to work with 8843 HS20.
I have had it work with an earlier blade (HS20), but I never checked what model it was.
Will try a 8832 model soon to see if i have more success.
If anyone know how to get the 8843's to work please post it here.
Maybe it's just some device that needs to be disabled?
Our blades are all 8843 HS20, with BIOS firmware rev. 1.03. We are using P2V 2.1.1. Has anyone tried using an earlier version of P2V on an 8843 blade? I will try some earlier versions to see if they work any better.
FWIW, I have 10 8843-41U ESX blades with BIOS rev 1.07. I have used VC and P2V from day one. I use both Ghost (w/BartPE) and P2V to migrate servers. If the older P2V versions still produce the same problem, you may want to try a 3rd party imaging solution like Ghost, PowerConvert, etc, to move the image over.
I've never tried to P2V an HS20, but it sounds like Windows is trying to startup a device that is no longer valid. Do you get the same results when you boot into Safe Mode?
Yes - we get the same results booting into safe mode.
Also, has anyone been able to successfully perform a V2P from a Windows 2003 VM to an IBM HS20 blade? I gave it a shot, but immediately after the Windows 2003 splash screen, the system reboots itself.