vnc mouse trouble; -usbdevice tablet no help
I have been unable to get the real mouse and the virtualized mouse to stay together when using kvm with linux host, guest and client. Previous advice (to me and others) was to use -usbdevice tablet. I've tried that, and a variety of kvm/qemu versions, but no luck.
Can anyone suggest what to do, or how to diagnose it?
vnc and the mouse work OK for Windows XP guests.
Host system:
Intel(R) Xeon(R) CPU E5420 @ 2.50GHz, 8 cores
qemu-kvm 0.12.2, built from source
linux 2.6.32-trunk-amd64 (stock Debian kernel)
guest linux 2.6.26-2-amd64
Invoked with
sudo vdeq bin/qemu-system-x86_64 -net
nic,vlan=1,macaddr=52:54:a0:14:01:01 \
-name "Lenny BCU Server" \
-vga std -vnc localhost:5 -usb -usbdevice tablet \
-net vde,vlan=1,sock=/var/run/vde2/tap0.ctl \
-boot c \
-hda /dev/turtle/Lenny06BCU \
-soundhw es1370 -m 1G -smp 2I've tried without the -usb; I added it hoping it would help. It didn't.
My client has been either the host system or 32 bit linux system. Mostly I've used krdc.
All systems basically Debian Lenny, with bits from later releases (e.g., the kernel on the host).
Quoted 2 lines · Ross Boylan
Previous advice (to me and others) was to use -usbdevice tablet. I've tried that, and a variety of kvm/qemu versions, but no luck.
check your guest's X11 config. if you didn't have -usbdevice tablet when installing, the installer would set only the PS/2 mouse, which isn't disabled when adding the tablet.
Signature · 1 line
Javier
Re: vnc mouse trouble; -usbdevice tablet no help [SOLVED]
Quoted 8 lines · Javier Guerra
Quoted 2 lines · Ross Boylan
Previous advice (to me and others) was to use -usbdevice tablet. I've tried that, and a variety of kvm/qemu versions, but no luck.
check your guest's X11 config. if you didn't have -usbdevice tablet when installing, the installer would set only the PS/2 mouse, which isn't disabled when adding the tablet.
Thank you for the tip. It worked.
Documentation on how to do this was skimpy, but the following seems to work. The two mice still get separated during motion, but when I pause they catch up with each other. This is with xorg 1:7.3+20 on Debian Lenny.
<xorg.conf>
Section "Module"
Load "evdev"
Disable "mouse"
EndSection
Section "InputDevice"
Identifier "Generic Keyboard"
Driver "kbd"
Option "XkbRules" "xorg"
Option "XkbModel" "pc104"
Option "XkbLayout" "us"EndSection
Section "InputDevice"
Identifier "Configured Mouse"
Driver "evdev"
Option "CorePointer"
Option "Device""/dev/input/by-path/pci-0000:00:01.2-usb-0:1:1.0-event-joystick"
Option "Path"
"/dev/input/by-path/pci-0000:00:01.2-usb-0:1:1.0-event-joystick" EndSection
Section "Device"
Identifier "Configured Video Device"
EndSection
Section "Monitor"
Identifier "Configured Monitor"
EndSection
Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
EndSection
</xorg.conf>
The man page with the distribution says the mouse module supports the USB protocol, but when I put that in I got an error that it was an unknown protocol.
"Device" and "Path" are supposed to be redundant for evdev; I put in the device when I got "no device specified" errors (approximate wording). I think the real cause was that the default mouse driver was still being preferred. I added the CorePointer option and the Module section to defeat that.
It's probably possible to cook up some udev rule to get a more useful and stable name for the input device. There may be one now, but I wasn't sure which it was.
The current xorg is advertised as auto-detecting the configuration; clearly that's not quite true in this case.
The xorg.conf above probably includes unnecessary directives.
The current virtual screen is too big. Can anyone tell me the best way to fix that?