[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Qemu-devel] [Bug 894037] Re: With VNC, "-usbdevice tablet" no longer ma

From: Anthony Liguori
Subject: [Qemu-devel] [Bug 894037] Re: With VNC, "-usbdevice tablet" no longer makes mouse pointers line up
Date: Mon, 19 Dec 2011 19:05:10 -0000

Can you please upgrade to 1.0 and see if that fixes the problem.  The
following patch should fix your problem (and is present in 1.0):

commit 21635e121ae0f0ab7874152a7c2f96e9d8cd642f
Author: Gerd Hoffmann <address@hidden>
Date:   Tue Aug 9 12:35:57 2011 +0200

    usb/hid: add hid_pointer_activate, use it
    HID reorganziation broke the usb tablet in windows xp.  The reason is
    that xp activates idle before it starts polling, which creates a
    chicken-and-egg issue:  We don't call hid_pointer_poll because there are
    no pending events.  We don't get any events because the activation code
    in hid_pointer_poll is never executed and thus all pointer events are
    routed to the PS/2 mouse by qemu.
    Fix this by creating a hid_pointer_activate function and call it from
    usb-hid when the guest sets the idle state.
    Signed-off-by: Gerd Hoffmann <address@hidden>

You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.

  With VNC, "-usbdevice tablet" no longer makes mouse pointers line up

Status in QEMU:

Bug description:
  I use qemu in VNC mode.  In order to get the client and server mouse
  pointers to line up, I've had to use the "-usbdevice tablet" option.
  This no longer works, and it behaves the same as if the option is not
  there.  This makes my VMs unusable to me.

  Here's how I'm booting WinXP:

  qemu-system-x86_64 -vga std -drive
  cache=writeback,index=0,media=disk,file=winxp.img -k en-us -m 2048
  -smp 2 -vnc :3101 -usbdevice tablet -boot c -enable-kvm &

  The Windows install hasn't changed, only qemu.

  I'm running this version of QEMU:

  QEMU emulator version 0.15.0 (qemu-kvm-0.15.0), Copyright (c)
  2003-2008 Fabrice Bellard

  I'll see about upgrading to 0.15.1, but since I haven't seen other
  reports of this particular problem in your DB, I'm assuming that this
  problem has not been fixed between 0.15.0 and 0.15.1.

To manage notifications about this bug go to:

reply via email to

[Prev in Thread] Current Thread [Next in Thread]