Keyboard and Mouse DOA

[dwainew]

I've had this problem since 3.1. My mouse and keyboard are dead once the VM has captured them. This is a fresh install of XP SP3. In fact, the keyboard issue existed even before the OS was installed, so I had to install with VirtualPC and then play with VBox. Sad. VBox has given me much better performance (than VPC) in the past, but if the keyboard/mouse doesn't work that's not worth much.

I'm running Win 7 Ultimate 64 bit on an HP dv7 notebook. Thinking it's driver related, but I'm at the latest builds of all available.

[Sasquatch]

If the keyboard and mouse stop working, is it only inside the Guest, or Host too? If it's both, then remove the USB filters you set, as there is no need for it. Are you logged on automatically in the VM? If so, do you see any driver install question? If not, wait until the driver is installed in the background. Where did you get this installation from in the first place?

[dwainew]

Thanks for the reply.

The Keyboard/mouse don't (ever) work in the guest only. the host key brings them back to the host ok, but nothing in the guest. I've tried with both a "blank" filter and no filter at all. under devices, there are two USB devices, "Broadcom corp HP integrated Module" and "unknown device". I've tried binding each with no luck.

not sure about automatic logon. that's an option in VPC, but don't know where or how this is done in VBox. Never bene able to login under Vbox.

Install is the final XP SP3 install disc from my MSDN subscription... as clean as it gets.

[dwainew]

btw, SUN/Oracle, I'd appreciate a clear explanation of the "VBox versions" required in my profile. I have NO idea what the different selections are. I found the concept of requiring some nonsensical ACRONYMIC information about an app without any explanation and that does not appear in the help/about quite humorous! oh yeah, I'm running the vbox 3.2.2 discombulicatalicious version. That's DCLCL to all u newbies.

[Entegy]

You're running the PUEL version. If you need to ask about the other versions, you're not using them. The open source editions are mainly for Linux.

[Sasquatch]

PUEL is also the only one with USB support and VRDP, so it's even easier to find out. Also, only the pre-build binaries here on the main site are all PUEL. Windows and Mac users will almost always have the PUEL version, unless the build it them self.

Now for the keyboard and mouse thing, you got the MSDN version, so it's an installer and all. Does the keyboard work there? Can you try it with a different OS, like a Linux distribution? You can pick an installer just to test the keyboard, but a live environment will also give you a check for the mouse.
I have little doubt that the keyboard and mouse do work in a different OS environment, but if it doesn't, then it seems that there is something wrong on your system. You're the first that post here that keyboard and mouse don't work at all in a VM.

[dwainew]

Thanks again for your time in helping me with this....

PUEL is also the only one with USB support and VRDP, so it's even easier to find out. Also, only the pre-build binaries here on the main site are all PUEL. Windows and Mac users will almost always have the PUEL version, unless the build it them self.

RE build version.... thanks for the clarification. I had no intent to start secondary discussion, I'm just pointing out that if matters enough to ask a poster to include this info in their profile what "build" they're running, it should probably show up in the help>About for later reference. nuff said, I know now I'm running PUEL

I have little doubt that the keyboard and mouse do work in a different OS environment, but if it doesn't, then it seems that there is something wrong on your system. You're the first that post here that keyboard and mouse don't work at all in a VM.

I'd tend to agree with you except that the exact same VHD file runs fine under VPC! Right out of the box, the installer had no K_M under VBOX, so I installed using VPC. Sorry to say, the windows world keeps my little brain more than occupied, so I haven't had the desire to play with other OSs since the early days of RedHat. My intro to VM technology was using VPC years ago and I discovered Vbox only about a year ago. Initially, under, dare I say it, Vista, I was able to take VHD files I had used for YEARS in VPC and just open them in Vbox and they worked (faster, that's why I'm here lamenting). Since I upgraded to Win7 I've had this issue.

Good news for me is I'm running under VPC, bad news is I'd LIKE to be running under VBox, but if something about hosting on my win 7 / HP environment precludes that, so be it. I just figured a torch bearer for VBox would be concerned enough about that situation that I'd be asked for log files, driver levels, etc.

Thanks again for the help.

[Sasquatch]

I really want to know what the keyboard and mouse do on another OS. There are plenty of choices for small Linux live environments, you boot it, click inside the VM to let it grab the mouse and keyboard and you're done, play away.
I find it really hard to believe it doesn't work for you with VB. I have an HP laptop now too (from work) with Windows 7 and the first VM I created on it had mouse and keyboard working just fine. So unless there is some software on your laptop that prevents access like this, there is no reason it doesn't work. Note: I don't have any of the HP tools on my W7 install. I personally hate all that junk OEMs install for you.

[Jareth]

I am also experiencing this problem. I am using the PEUL 3.2.4 version on a windows 7 home premium host and xp sp 3 guest. The guest system was built with vmware converter to make a vmdk file. I am replacing the xp sp 3 with the win 7 system and wanted to retain the orginal build within a vm environment. Everything boots fine until it gets to windows, and an activation screen pops up saying it cannot verify the system anymore, which is fine since it is a cloned copy. But I cannot use mouse or keyboard. Unfortunately I do not have any ps/2 input devices at my current location.

I am however experienced with versions of Linux and will try and create a linux vm with VB and see if that solves it. Also I did not release 3.2.4 was such a recent release, would it be an idea to try installing 3.2.0 instead and going form there? I'd really like to get the old system virtualized without installing everything from scratch.

Thank you,

Jareth

[Jareth]

UPDATE:::::

Although Ubuntu crashed somewhere during installation, I did have full access to mouse and keyboard via a live disk. Also used the live disk on the same VM machine that was having troubles. Everything appears to work fine until Windows GUI gets control of the system, ie I can select boot in safe mode and what not. I do remember having a problem similar to this in the past with Window XP not accepting inputs after a major system change, but never resolved the problem only reformat and installation worked.

I'm going to look more extensively into Microsoft's support as I do not think this is a VB issue. Will update any findings here.


Jareth

[Sasquatch]

Jareth, your issue is entirely different. You move an existing system with it's own drivers (keyboard and mouse included) to a virtual system. It's only normal that the keyboard and mouse don't work, because it needs to install the new ones. As long as you stay on the logon screen, you just have to wait for the drivers to be installed in the background.
It is not advised to install a previous release from a major version (e.g. go from 3.2.4 to 3.2.0), because a lot of bugs are fixed in the newer releases. One can go to 3.1.8 if he/she really wants to.

[commorancy]

Sasquatch,

First, Windows 2000 doesn't seem to automatically install missing drivers on the login screen. At least, not that I've found. Second, shouldn't a PS2 Mouse and Keyboard simply just 'work'? I mean, if VirtualBox is emulating hardware PS2 input devices, they should just appear and start working as soon as Windows starts (no drivers necessary). The keyboard works on the BIOS screen and on the 'Press F8' screen, but not in Windows. Like any PS2 device, these devices should simply be activated as soon as Windows starts up. Why isn't Virtualbox doing this? This is how VMWare player works. I can see no reason for the PS2 keyboard and mouse to not work on Windows startup. If the user wants to convert to emulating a USB Keyboard and Mouse later, that should be a simple settings change. So, why is it that VirtualBox PS2 input devices don't just work?

With some creative administration, I even managed to get VBoxAdditions installed using /S on the keyboardless and mouseless Windows 2000 guest. The funny thing is, I saw the installer load the vboxmouse.sys file, yet neither the mouse nor the keyboard is working after a reboot. If I drag size the screen, the video driver is working, though. I know the vboxadditions got installed. So, I'm at a loss at this behavior. In fact, I can't even see a reason for a PS2 mouse or keyboard not to work in any operating system that supports PS2 devices. So, there must be something in VirtualBox that is preventing Windows from seeing these PS2 devices or activating them.

--
Brian

[Sasquatch]

First, Windows 2000 doesn't seem to automatically install missing drivers on the login screen. At least, not that I've found.

Correct, not that you have found, but it does install it in the background. I'm 1000% sure about that. Even Windows NT does it I think.

Second, shouldn't a PS2 Mouse and Keyboard simply just 'work'? I mean, if VirtualBox is emulating hardware PS2 input devices, they should just appear and start working as soon as Windows starts (no drivers necessary). The keyboard works on the BIOS screen and on the 'Press F8' screen, but not in Windows. Like any PS2 device, these devices should simply be activated as soon as Windows starts up.

Then I'd like you to test the same scenario on a native system. Get a keyboard and mouse from one set, let windows install the drivers and all, then get a completely different set, preferably a set with more features like multimedia keys and additional mouse buttons. Big chance that it won't work on the logon screen right away. The devices are activated, but Windows still needs to install the drivers for it to operate properly. The POST (what you call 'BIOS') and the F8 menu don't depend on drivers, they just accept keycodes. Windows does the same, but needs to translate them to the proper character or action.

This is how VMWare player works.

Newsflash: This isn't VMware, this is VirtualBox. Different program, different company behind it, different results.

If the keyboard and especially the mouse isn't working after waiting for a while or even installing the Guest Additions one way or another, there is something wrong with the system. Is it a clean install, or did it come from a VMWare environment? Are the tools removed prior to moving it to VB? If not, then the tools will cause conflicts, getting you to where you are now: without input devices. Safe mode should work no matter what, unless of course VMWare made their drivers so that it overwrites the default drivers and render others useless.

[adamf663]

The solution I discovered is to reinstall windows (win2k) over the top.
Don't hit R at the first prompt, but hit enter. At the next prompt it'll discover the existing instalation, hit "r" then.