Bugzilla – Bug 358460
sax2: assign unique ids to virtualbox/vmware mouse pointers
Last modified: 2008-05-21 16:39:27 UTC
Some distributions ship with GFX and mouse drivers for virtual products (VMware, VirtualBox etc) by default. This will not only enable us to detect the correct resolution, but also allow the user to freely move the mouse from the virtual OS to the physical OS without special key combinations.
We have vmware/vmmouse (xorg-x11-driver-video/xorg-x11-driver-input) and vboxvideo/vboxmouse (xorg-x11-driver-virtualbox.rpm). What else are you missing?
Created attachment 193014 [details] screenshot Oh cool. I guess the issue then is that they are not activated properly. For instance, when I installed Mandriva in VirtualBox, I got the attached message from VB. When I install openSUSE, I always have to capture/release the mouse pointer. I since wiped Mandriva but I can install it again and provide you with the xorg.conf if that would help?
I think we could make sure that xorg-x11-driver-virtualbox will be installed if such a (software-emulated) hardware device exists by adding the appropriate Supplements line to the specfile. So what's the output of "hwinfo --gfxcard" inside of virtualbox? Adding the video driver support to SaX2 then would be rather easy as well instead of SaX2 using vga/vesa for virtualbox instead. See xorg-x11-driver-video-unichrome for an example. What's still missing is the integration of the vmmouse/vboxmouse in SaX2. But let's begin with vboxvideo.
Created attachment 193020 [details] hwinfo --gfx
So let's add Supplements: modalias(pci:v000080EEd0000BEEFsv*sd*bc*sc*i*) and all the other sax2/hwinfo metadata files to xorg-x11-driver-virtualbox package.
done. The remaining parst for vmmouse/vboxmouse need to be done in SaX2.
Magnus, could you provide the xorg.conf snippets required for vmmwouse/vboxmouse, please?
Created attachment 193120 [details] xorg.conf
Section "InputDevice" Identifier "Mouse1" Driver "vboxmouse" Option "Device" "/dev/mouse" EndSection /dev/input/mice works as well, right? Please also attach the snippet for vmmouse.
I need the vendor/device ID's of the mouse to assign a profile which applies these changes. Could you provide the information of sysp -s mouse thanks
I will add the requested information as soon as I can install from Factory or Alpha2 is available for download.
Dirk, maybe you can provide the requested feedback for virtualbox as well?
Created attachment 195291 [details] VMware xorg.conf I'm attaching an xorg.conf which is configured with VMware tools mblxws01:~ # sysp -s mouse Mouse0 => Protocol : explorerps/2 Mouse0 => Device : /dev/input/mice Mouse0 => Buttons : 5 Mouse0 => Wheel : 1 Mouse0 => Emulate : 0 Mouse0 => Name : ImPS/2 Generic Wheel Mouse Mouse0 => VendorID : 0x0210 Mouse0 => DeviceID : 0x0013 Mouse0 => Profile : <undefined> Mouse0 => RealDevice : <undefined> Mouse0 => NutShell : 0
This is sysp from VirtualBox mblxws01:/home/mboman # sysp -s mouse Mouse0 => Protocol : explorerps/2 Mouse0 => Device : /dev/input/mice Mouse0 => Buttons : 9 Mouse0 => Wheel : 2rpm Mouse0 => Emulate : 0 Mouse0 => Name : ImExPS/2 Generic Explorer Mouse Mouse0 => VendorID : 0x0210 Mouse0 => DeviceID : 0x0025 Mouse0 => Profile : <undefined> Mouse0 => RealDevice : <undefined> Mouse0 => NutShell : 0 Perhaps note worthy is that xorg-x11-driver-virtualbox was not installed (I'm guessing that it should be install for this to work properly). There are problems with this package at the moment (See Bug#362564)
Created attachment 195295 [details] VirualBox xorg.conf Here's an xorg.conf configured by VirtualBox
Unfortunately in both cases a generic standard mouse is provided by the emulators and therefore detected by SaX2. Maybe we can at least make them selectable in SaX2, so we need entries for /usr/share/sax/api/data/cdb/Pointers? >Perhaps note worthy is that xorg-x11-driver-virtualbox was not installed (I'm >guessing that it should be install for this to work properly). There are >problems with this package at the moment (See Bug#362564) Looks like nearly all virtualbox package are currently missing on Alpha2. :-(
Created attachment 195296 [details] sax2-vboxmouse-vmmouse.diff
I have added the suggested data for manual selection. I will reassign this bug to Steffen Winterfeldt maybe he has a method to assign unique id's for the devices in the future
I gave the mouse the id 0x80ee/0x0100 and added virtualbox video & mouse drivers to the installation system.
BTW, Marcus: I've changed hwinfo in sl 11.0 to report the kernel input device ids now.
Thanks, so we have at least unique ids for virtualbox mouse now. Any plans to to assign also unique ids for the vmware mouse?
I have added a vbox-mouse profile, assigned to Steffen because of virtualbox question
Thanks, Marcus. Should be "vmware mouse" question I think.
What's the driver for vmware? vmmouse_drv?
(In reply to comment #24 from Steffen Winterfeldt) > What's the driver for vmware? vmmouse_drv? Exactly. # rpm -ql xorg-x11-driver-input|grep vm /usr/lib64/xorg/modules/input/vmmouse_drv.so
Ok, mouse id is 0x15ad/0x0100.
done
It would, if we do this, be helpful if the vbox mouse driver actually works. Which it currently does not.
(In reply to comment #28 from Steffen Winterfeldt) > It would, if we do this, be helpful if the vbox mouse driver actually > works. Which it currently does not. > See Bug #365374 .
Ok. So the issue is already tracked. Closing as fixed again.
*** Bug 365374 has been marked as a duplicate of this bug. ***
I think this change is the reason factory crashes in virtualbox - and only in virtualbox
(In reply to comment #32 from Stephan Kulow) > I think this change is the reason factory crashes in virtualbox - and only in > virtualbox See Bug #365374.
*** Bug 371553 has been marked as a duplicate of this bug. ***
How's it about the vmmouse part? Is that supposed to be 'autodetected' in a VMware installation? The sad thing about this bug here is that it's two problems tackled in one... and after the issue with the vbox driver, it was considered as closed. the vmware part seems to remain open though. I can see on a Beta3 installation that the mouse has the correct IDs, but it was not auto-selected by sax... which would be very nice.
The vmmouse driver does not work. See Bug #372189.
partially right Stefan, comment #9 in bug #372189 states clearly that vmmouse works in beta 3 and that's also what I have in my installation here.
User did some manual adjustment to get it work. Our configuration didn't work, so we won't enable it. We're not interested into breaking the vmware installation at that time.