keyboard and mouse dead for vhd in virtualBox

[sherry]

Hi,

I have already uninstalled VM additions in VPC, and open this vhd in VirtualBox. But keyboard and mouse are still not working. I have waited for over 1 hr and not useful. I tried several VM images, same problem.

Anybody can give me more suggestion?

Thanks in advance,

[Perryg]

Make sure that you have *NOT* enabled a USB filter for either in the guest settings.

[sherry]

Thanks Perryg,

VPC I use console one, and in setting I could not find any USB setting. In VirtualBox, I already DISABLED USB controller. But keyboard and mouse are still not working.

Any other things I missed?

[Perryg]

Post the guests log file (as an attachment)
Also the following:
From the hosts terminal/command window type VBoxManage showvminfo <VM Name> --details and post here. Replace <VM Name> with the actual name of the VM. Use " " if the name has a space in it.

Note if the host is Windows you need to be in the directory that has VBoxManage.exe for the command to work.

[sherry]

Hi Perryg,

info from the command:
Name: QA
Guest OS: Windows XP
UUID: 683d86cb-b186-44c2-af34-3f95bf43de15
Config file: C:\Users\xxxxxxxxxx\VirtualBox VMs\QA\QA.vbox
Snapshot folder: C:\Users\xxxxxxxxxxx\VirtualBox VMs\QA\Snapshots
Log folder: C:\Users\xxxxxxxxxxxx\VirtualBox VMs\QA\Logs
Hardware UUID: 683d86cb-b186-44c2-af34-3f95bf43de15
Memory size: 2216MB
Page Fusion: off
VRAM size: 16MB
CPU exec cap: 100%
HPET: off
Chipset: piix3
Firmware: BIOS
Number of CPUs: 1
Synthetic Cpu: off
CPUID overrides: None
Boot menu mode: message and menu
Boot Device (1): Floppy
Boot Device (2): DVD
Boot Device (3): HardDisk
Boot Device (4): Not Assigned
ACPI: on
IOAPIC: off
PAE: off
Time offset: 0 ms
RTC: local time
Hardw. virt.ext: on
Hardw. virt.ext exclusive: off
Nested Paging: on
Large Pages: on
VT-x VPID: on
State: running (since 2011-12-12T15:45:26.745000000)
Monitor count: 1
3D Acceleration: off
2D Video Acceleration: off
Teleporter Enabled: off
Teleporter Port: 0
Teleporter Address:
Teleporter Password:
Storage Controller Name (0): IDE Controller
Storage Controller Type (0): PIIX4
Storage Controller Instance Number (0): 0
Storage Controller Max Port Count (0): 2
Storage Controller Port Count (0): 2
Storage Controller Bootable (0): on
IDE Controller (0, 0): C:\VM\QA\Temp\Windows XP SPk2 Excel 2007.vhd (UUID: fca29
c4d-e2f0-da11-8170-e59d41bb6c12)
IDE Controller (1, 0): Empty
NIC 1: MAC: 0800270C0793, Attachment: NAT, Cable connected: on, Trace:
off (file: none), Type: Am79C973, Reported speed: 0 Mbps, Boot priority: 0, Pro
misc Policy: deny
NIC 1 Settings: MTU: 0, Socket (send: 64, receive: 64), TCP Window (send:64, re
ceive: 64)
NIC 2: disabled
NIC 3: disabled
NIC 4: disabled
NIC 5: disabled
NIC 6: disabled
NIC 7: disabled
NIC 8: disabled
Pointing Device: PS/2 Mouse
Keyboard Device: PS/2 Keyboard
UART 1: disabled
UART 2: disabled
Audio: enabled (Driver: DSOUND, Controller: AC97)
Clipboard Mode: Bidirectional
Video mode: 640x480x32
VRDE: disabled
USB: disabled

USB Device Filters:

<none>

Available remote USB devices:

<none>

Currently Attached USB Devices:

<none>

Shared folders: <none>

VRDE Connection: not active
Clients so far: 0

Guest:

Configured memory balloon size: 0 MB
OS type: WindowsXP
Additions run level: 0

Guest Facilities:

No active facilities.


########################
And log file is attached.

[Perryg]

The log shows that VirtualBox is struggling with the already installed drivers.
Are you able to start the guest in safe mode? Then see if the keyboard, mouse works?

[sherry]

I tried on safe mode, no lucky. keyboard and mouse are stuck at login page.

[Perryg]

I don't know what else to tell you except that you should not turn off the usb completely in the guest just make sure that you have not set a filter for the keyboard or mouse.
I also noticed that you have not installed the Extension Pack, so you would need to make sure that the USB2 is not checked in the guest or install the Extension Pack.

[sherry]

I installed extension pack, and enabled USB controller, but not USB2.0. All these could not solve my problem. Frustrated...

[mcbsys]

Sherry,

Did you ever get this resolved, and if so, how? I'm seeing the same thing when I try to open an XP VHD in VirtualBox 4.1.14.

I have no VB extensions installed, no USB filters defined, VPC guest additions uninstalled. XP boots fine (safe mode or normal mode). I can see the logon prompt, but I can't type into it. After a while, I get the screen saver, but clicking on it with the mouse does not bring back the display.

I started with Enable IO APIC unchecked, and I was able to use ACPI Shutdown from the VB menu to gracefully shut down the machine. I read elsewhere that IO APIC should be changed, so I checked it. Now ACPI Shutdown does not do anything.

Should I start a new thread, or continue here if it is the same symptoms?

Mark

[michaln]

If there are drivers for Virtual PC (for example) installed in the image, and those drivers are bad enough to load even when not running on Virtual PC while blocking keyboard/mouse functionality, there's really not much we can do about it. You have to get those drivers off of the image.

[mcbsys]

Michaln,

Thanks for your reply. I chose my simplest XP SP3 VM for this initial test. It's my "base image" with almost no software installed. A list of installed programs and a partial screen shot of the Device Manager are below.

When booted in VPC, Device Manager says it's expecting a PS/2 mouse and keyboard. My physical keyboard is PS/2 attached through a KVM that converts to USB. The mouse is USB, not through the KVM. VPC seems capable of converting these USB devices to PS/2--will VB do the same?

I've tried lots of settings today with no luck. Details below. Log file attached. Is there a clue in there as to what device is conflicting?

Thanks for your help,

Mark

Guest Installed Programs.png (4.01 KiB) Viewed 7889 times

Guest Device Manager 2.png (14.78 KiB) Viewed 7889 times

VirtualBox XP testing

Unchecked "Enable IO APIC".
-> cannot type, cannot move mouse
-> again able to shut down using Machine > ACPI shutdown

Unchecked "Enable absolute pointing device"
-> cannot type, cannot move mouse

Checked "Enable absolute pointing device" again
Started in VPC, uninstalled "Virtual PC Guest Bus Driver"
-> cannot type, cannot move mouse

Unchecked "Enable absolute pointing device"
Disabled audio
Disabled USB controller
Disabled Network
-> cannot type, cannot move mouse

Reduced Video memory from 18MB to 16MB to match VPC setting ("non-optimal" for VB)
Disabled Nested Paging
Disabled VT-x/AMD-V
-> Blue screen as soon as logon prompt appears, faulting driver intelppm.sys

intelppm.sys info:
- "This is actually a power-management process provided by Microsoft Windows. It throttles the CPU to save power." (can't post link)
- How to disable: (can't post link)

Enabled VT-x/AMD-V
-> no blue screen, but cannot type, cannot move mouse
-> ACPI shut down no longer works

Enabled Nested Paging
-> cannot type, cannot move mouse
-> ACPI shut down works again

Re-start machine in VPC
-> Found New Hardware "Virtual PC Guest Bus Driver". Aborted installation.
-> Uninstalled Microsoft Security Essentials, rebooted, shut down.

Re-start in VB
-> cannot type, cannot move mouse

Re-start in Safe Mode in VB (note I can use keyboard pre-boot)
-> cannot type, cannot move mouse

Remove VBox additions virtual CD from IDE secondary master device.
-> cannot type, cannot move mouse

Re-enable Network
-> cannot type, cannot move mouse
-> PC not listed in router's Device List, so network probably not starting

[mcbsys]

One more test: I thought maybe if I could get past the logon prompt under VB, XP would start telling me which devices it was installing, or trying to. So I set up automatic logon. But now I just get to the "must re-activate Windows within 3 days" prompt, and since I can't click Yes or No, it's stuck there. ACPI Shutdown does not work at this point.

Mark

[mpack]

I don't know why you keep throwing logs and screenshots at us. The problem is plain: you need to remove VPC mouse and keyboard drivers and replace them with standard drivers. We are not VPC users and can't tell you the best way to do that. A VPC forum might be more helpful. Or, booting off a Windows Setup CD and telling it to repair the installation might work.

[mcbsys]

Dear mpack,

With regards to your assertion that the problem is non-standard mouse and keyboard drivers in my VPC image... One reason I posted the screen shot is so you could see the mouse and keyboard drivers. Here are the details from the VPC:

kbdclass.sys 5.1.2600.5512 (xpsp.080413-2108) 24,576 bytes modified 4/14/2008 12:09am
mouclass.sys 5.1.2600.5512 (xpsp.080413-2108) 23,040 bytes modified 4/14/2008 12:09am
i8042port.sys 5.1.2600.5512 (xpsp.080413-2108) 52,480 bytes modified 4/14/2008 12:48am

These file dates and versions match 100% with those on a physical XP Pro machine I have here.

Today I installed a fresh copy of XP SP3 into a brand new VirtualBox VM, with USB disabled so it would have to use PS/2. Mouse and keyboard work fine, and sure enough, the mouse and keyboard drivers are 100% identical to those used in the VPC image. To me it looks like the mouse and keyboard drivers are not the issue. However, there are several other System device differences, starting from the processor presented by VB to the guest. This is the Device Manager under the fresh VirtualBox VM (no guest additions installed):

VB native guest Device Manage.png (15.32 KiB) Viewed 7869 times

Did I misunderstand that part of the purpose of VirtualBox natively supporting VHD drives was to allow for easier transitions from a VPC environment? If Microsoft said they support VDI drives but I couldn't get a VDI-based VM to load in VPC, I would be posting in a Microsoft forum. Since this seems like a VirtualBox feature that is not working as expected, I posted here. I had hoped that a VB expert might see an issue in the logs that I do not. But even if you don't personally have the answer, maybe another user does (which is why my initial post addressed the OP). If there is a definitive guide on migrating an XP VM from VPC to VB, I'd be glad to see it.

Thanks,

Mark