Ticket #6845 (closed defect: obsolete)

Opened 8 years ago

Last modified 22 months ago

VBoxMouse causes BSOD when the same instance is running on a physical machine

Reported by: igrnow Owned by:
Priority: minor Component: guest additions
Version: VirtualBox 3.0.8 Keywords: VBoxMouse
Cc: Guest type: Windows
Host type: Linux

Description (last modified by aeichner) (diff)

This problem is similar to one fixed in

I have a Windows XP instance that I run from a physical disk in a VirtualBox VM. The guest additions are installed and everything is ok inside VM (including the mouse).

However, since the XP installation is on a physical disk, I also can boot into it and run it as a physical machine. The only issue that I could not overcome with some other configuration tricks is the virtual mouse driver.

It seems that the VBoxMouse driver is installed in a way that causes it (or some of its components) to load in any hardware profile even if the virtual mouse is not available (in a physical boot). In a physical instance VBoxMouse cause a BSOD shortly after the user is logged in and the desktop is displayed. A workaround is to remove VBoxMouse from UpperFilter in HKLM\System\CurrentControlSet\Control\Class\{4D36E96F-E325-11CE-BFC1-08002BE10318} However, this disables the mouse integration in a virtual mode.

It would be nice to have the VBoxMouse driver either to be assigned to a hardware profile or to be automatically inactive if the virtual hardware is not present. I could not

Change History

comment:1 Changed 22 months ago by aeichner

  • Status changed from new to closed
  • Resolution set to obsolete
  • Description modified (diff)

Please reopen if still relevant with a recent release of the guest additions.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use