Keyboard and Mouse not working WinXP on Win7

[Trickle]

Hello,
I am having trouble with getting the mouse and keyboard to be detected in my XP guest system, I have created a VHD using disk2VHD of an XP 32bit machine. I am using WIndows 7 64 Bit VB 4.3.15 and on start up the operating system but the keyboard and mouse would not work at the login prompt, In safe mode or in normal mode. Attached is the startup log.

Keyboard works at boot
I have installed Guest Permissions
VT-x is enabled in my host bios
There are no filters in the USB settings for the host
I have tried VB 4.3.12 with the same issues

Does anyone have any suggestions? Would really appreciate the help

[mpack]

You are using a test build of VirtualBox, I'm afraid we can't support you in the regular forums with that.

1. I suggest that you revert to 4.3.12.
2. Install the 4.3.12 Extension Pack on the host.
3. Double check that no filters are set in the VM settings | USB.
4. Attach a zip containing the .vbox file for your VM.
5. Include an updated log file in the zip.

[Trickle]

Thanks for your response mpack.
The same issue occurs with this version, Ext pack 4.3.12 installed, no USB filters.
Attached is the Vm Folder with all the info that you requested.

[mpack]

Actually, I asked for one log only. Giving me four times the (unpaid) work isn't always entirely welcome.

Incidentally, the Guest Additions are probably not installed, though you do still have a GAs ISO attached to the VM.

The latest log with 4.3.12 doesn't seem very useful - it's shut down in less than a minute. The VM could be unresponsive for lots of reasons for much longer than that. What exactly was the reason for shutting it down so quickly?

I'm assuming that since this was a P2V project, the problem will eventually turn out to be an incompatibility between some weird keyboard and mouse you had on the physical host, versus what's used in the VM. The puzzling thing is why plug and play doesn't detect the new devices right away.

Do you know what mouse and keyboard type was in use? Anything unusual?
How do you know the lack of mouse/kbd response isn't due to high CPU or I/O burden? What do you see that makes you think the guest hasn't locked up?

[Trickle]

As you say the guest additions are mounted and I have tried installing during runtime of the VM but there is no indication that anything is installed. How do I know for sure?
Shutting it down quickly was not done for any reason other than I have ran this VM many times now for various lengths of time with no success. I have ran it for longer and attached 1 log file for viewing if you feel like some extra work .
The previous computer is a laptop HP Compaq nx6120 and the host computer is a HP Elitebook 8540. I have the host on a docking station with USB connected mouse and keyboard both Microsoft. I have tried disconnecting from the docking station but there is no difference.
Interesting you suggest the CPU overload, how do I find out the load on the Guest CPU? I have noted that the image colour of the CPU hard disk in the bottom of the Vm is flashing green and red, is the red any indication of lockup. After I leave the VM for 5 min it will show the screen saver which jumps around the WindowsXP image and I need to select the Machine drop down selector menu and APCI Shutdown to get the login window back up. Pressing it again shuts down the machine.

I do appreciate the help thanks.

[mpack]

I asked about the nature of the keyboard and mouse on the original PC this VHD was made from. I don't need to know much about the host, since it's hardware didn't define the VM.

To check for a locked up VM, look at the tasklist on your host. Look for a VirtualBox process occupying a high and static portion of CPU. On a quad core host like you have, perhaps the VBox process will show as using 25% CPU. There will actually be two VBox processes running, the VM itself (VirtualBox.exe), and the background service process, VBoxSVC.exe. Check both.

Ultimately, P2V projects are not guaranteed to succeed. Mostly that's down to the flexibility of the guest OS involved, and particular drivers you might have installed - it doesn't really have much to do with VirtualBox.

Incidentally, did you prepare this XP prior to migration? Some of potential XP migration issues are discussed here. Ignore the obsolete step by step imaging instructions - Disk2VHD is better.