Bug 492606 - The Xen virtual keyboard/mouse combination device confuses the X server
The Xen virtual keyboard/mouse combination device confuses the X server
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel-xen (Show other bugs)
All Linux
low Severity medium
: rc
: ---
Assigned To: Markus Armbruster
Red Hat Kernel QE team
Depends On:
Blocks: 458302
  Show dependency treegraph
Reported: 2009-03-27 13:10 EDT by john.haxby@oracle.com
Modified: 2009-07-31 10:44 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-07-31 10:34:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Patch to split the combo xen virtual keyboard/pointer device into two virtual devices (4.41 KB, patch)
2009-04-02 08:33 EDT, john.haxby@oracle.com
no flags Details | Diff

  None (edit)
Description john.haxby@oracle.com 2009-03-27 13:10:04 EDT
Description of problem:

While its possible to configure the X server to use the Xen virtual keyboard and mouse combination device (see other bugs referenced in the next comment) it is fraught with problems because the X server only half-believes that you can have a device that is both a keyboard and a mouse. In particular you must have exactly one CorePointer and one CoreKeyboard and, although this is not stated explicitly, they cannot be the same device.   It gets worse, though, because the Xen virtual keyboard (which is also a pointer) must have exactly the same Xkb configuration as the normal keyboard because which Xkb settings are on a per-device basis, this isn't reflected through utilities like setxkbmap.  There's more detail in the bugs I'm about to enter and refer to later.

Later kernels, for example, Fedora 9's kernel, split the virtual keyboard and pointer into two separate devices.   This makes configuration much easier and doesn't run into logical problems with the X server configuration.

Having said that, this is a "nice to have" because we can configure the Xen pointer and keyboard combo device in a way that is transparent to most users.

Version-Release number of selected component (if applicable):kernel-xenU-2.6.9-82 (and other, earlier kernels).

How reproducible:

Steps to Reproduce:
1. Attempt to configure the Xen virtual pointer so that you get proper mouse tracking in a Xen guest VNC console.
Actual results:

Without fixing xorg-x11 and rhpl to understand more of this combo device you can't do this.  Well, you can, so long as you don't mind losing either the keyboard or the mouse or sometimes both.

Expected results:

With the relatively new evdev driver in the xorg-x11 server this should be a piece of cake, but it's not because the evdev driver wants to be both a keyboard and a mouse and this confuses X.

Additional info:

I've attached a patch which does the trick.  But see also the rhpl and xorg-x11 patches.
Comment 1 john.haxby@oracle.com 2009-03-27 13:53:05 EDT
See bug 492610 for the xorg-x11 changes needed to add xkb support to the evdev driver.  The changes in 492610 are useful for people who don't yet want to update their kernel and can be applied to older RHEL4 versions.
Comment 2 john.haxby@oracle.com 2009-03-27 14:55:52 EDT
See bug 492621 for details of integrating this change (and coping when its not there) into rhpl and thence system-config-display and the installation image.
Comment 3 john.haxby@oracle.com 2009-04-02 08:33:45 EDT
Created attachment 337794 [details]
Patch to split the combo xen virtual keyboard/pointer device into two virtual devices

Sorry, forgot to actually attach the patch before.
Comment 5 Markus Armbruster 2009-07-31 10:34:15 EDT
The bug as reported is about the difficulties to manually configure X
in a certain way, to get proper pointer tracking.  It is certainly
valid.  However, the real problem users care about is that pointer
tracking works very poorly (mouse hits invisible wall).

Upstram, we solved the problem by fixing numerous issues in various
places to make it work out of the box, from Fedora 11 on.

The patches proposed by the reporter solve the problem by making
manual configuration work.  They are unrelated to the upstream

Like the upstream solution, they're fairly invasive: they touch the
kernel and several user space packages.  This is a significant risk.
Moreover, splitting the device is an ABI change.  The question is
whether there are benefits to justify that.

We intend to put much less invasive changes into 4.9 to improve
pointer tracking (bug 492868).  They fix the "mouse hits invisible
wall" problem.  They still require a pointer grab, which virt-viewer
makes relatively painless.

So, the benefit of the proposed patches over what we've got already is
to enable manual configuration so that the mouse grab can be avoided.
While that's certainly nice, it doesn't justify the risk, in my

If you disagree, please reopen the bug.

Some technical background:

There are 3 pieces in the stack: VNC client, QEMU VNC server and the
guest's X.  The old, misbehaving setup has VNC client sending absolute
coordinates, which the VNC server sends through xenkbd to X.  X in
RHEL-4 doesn't have any auto-configuration of input devices, so it
just opens /dev/input/mice, and thus the guest kernel converts from
absolute to relative.  Because the VNC client has no knowledge of this
conversion, you get into situation where you hit an invisible wall in
the client when it thinks it has got to the virtual desktop boundary.

Now, if you had absolute coordinates being passed and used all the way
to X then it would trivially work, but this requires X configuration.
Recent X's do that automatically.  RHEL-4's X simply isn't capable of
that.  The patches proposed by the reporter add manual configuration
steps across a wide range of RPMs.

The fix we did for RHEL-5.4 and plan to backport to 4.9 is to make
xenkbd *not* use absolute coordinates, so the VNC server now sends
relative coordinates.  This removes the broken absolute -> relative
conversion in the guest kernel.  On its own this isn't sufficient,
because you then get broken absolute to relative conversion in the VNC
server instead.  So we also added the VNC relative mouse extension to
QEMU and GTK-VNC.  Now the VNC client is in charge of doing the
absolute -> relative conversion.  This is good, as this is the only
point in the stack capable of doing the conversion correctly, to avoid
hitting an invisible wall.  The only restriction is that you must grab
the host mouse pointer and hide it, so you only see the guest drawn
Comment 6 Markus Armbruster 2009-07-31 10:44:45 EDT
By the way, RHEL-6 pointer tracking will be fine out of the box using absolute coordinates, just like upstream.

Note You need to log in before you can comment on or make changes to this bug.