I used P2V to transfer a 2003 Windows server to a virtual machine. It works and will boot up but I can't interact with it at all. Sending a ctrl-alt-del from the VM menu does nothing. The mouse and keyboard will not work either. I have tried this in VMWare server and workstation. I can't get into bios to check settings because the keyboard will not interact with the machine. HELP!
Does the Dell have a PS/2 input for a keyboard and mouse? If so, could you try plugging them in instead of the USB and try reimaging/re-P2V'ing the machine?
It might be related to a phenomenon that affects Windows 2003 and USB controllers.
What was your source machine? Did it happen to be a Blade with a USB mouse and keyboard?
A possible workaround is to try to go into the VM via RDP so that you can fix the mouse and keyboard and install VMware Tools.
Refer to this discussion thread for more information.
http://www.vmware.com/community/thread.jspa?messageID=461337񰨙
No, it is not a blade server. I had already tried what that post offered but it didn't help. Thanks
What happens when you boot up the VM in Safe Mode? Are you able to get a mouse and keyboard?
I can't get it to safe mode without the keyboard. Or is there a way to do it wothout the keyboard?
Thanks
Hmmm... I was wondering if they came up and then disappeared. Something you could try is (take a backup of the VM/virtual disk first) booting up the VM with a Windows 2003 Install CD and try to repair the OS.
No they do not come up and then disappear. I tried to boot from cd, but it won't. I have no idea what to do here. Thanks
Can you provide the following information regarding the original machine being P2V'ed?
1. What was the HAL? (you can go into Device Manager-> Computer)
2. What was the keyboard and mouse type? USB or PS/2?
3. What SP level was Windows 2000?
Thanks.
1. ACPI Multiprocessor PC
2. USB HID Mouse and Keyboard
3. Windows Server 2003 R2 Service Pack 1
It is a Dell GX620 Intel P4 3.00 Ghz, 2.99 Ghz 504 MB RAM
Thanks
Does the Dell have a PS/2 input for a keyboard and mouse? If so, could you try plugging them in instead of the USB and try reimaging/re-P2V'ing the machine?
It might be related to a phenomenon that affects Windows 2003 and USB controllers.
No, it only has USB.
No, it only has USB. It is plugged into a KVM device so the keyboard and mouse go through 1 USB. I can bypass the KVM device and plug in a keyboard and mouse directly and them re-image it. Do you think that might help?
I'm hoping that the KVM device might be it and plugging in directly might work.. If you have time to reimage it would be good to know.
I wish I could tell you that doing this made a difference, but it didn't. I removed the KVM and plugged a USB keyboard and mouse in and then re-imaged it. I brought the new machine up and I still can't interact with it.
Thanks
Can you verify which target platform you selected in P2V during the System Reconfiguration (Workstation, GSX Server, or ESX Server)?
Can you also verify what platform(s) you brought up the VM?
I was able to get into the Bios and to the boot menu. I am now repairing the os from disk. Will let you know if it comes back up with keyboard and mouse.
The first time I did the default, the top ESX selection. The second and third time I used the GSX selection. I brought it up in Windows 2003 Standard.
IT WORKS!!! I was able to do a repair from cd and now the keyboard and mouse work. Thanks for all you help.
Hi,
Can you please tell us in detail the steps you took to get it to work?
At the time when keyboard and mouse were frozen, did the target platform on which VM was running had mouse/keyboard connected via USB port or PS2 port?
When you selected GSX instead for the target platform, how was the mouse and keyboard connected on the machine running GSX?
I'm guessing that selecting GSX Server as the target worked because GSX Server supports USB, whereas ESX Server does not. With ESX Server, it appears P2V assumes a PS/2 keyboard and mouse. I am going to request that subsequent versions of P2V handle USB, but for now if you have a USB input device I'm going to recommend you choose Workstation or GSX Server and import the file into ESX Server as a workaround.
