All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlh.net>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] usb-hid: activate usb tablet / mouse after migration.
Date: Tue, 21 Feb 2012 17:25:41 +0100	[thread overview]
Message-ID: <4F43C585.9000609@dlh.net> (raw)
In-Reply-To: <CAETRQWkeJzr-ctQp3N1wz4BL2Bita81Om_ZM9DV59D2D5dt=Tw@mail.gmail.com>

On 16.10.2011 10:54, TeLeMan wrote:
> On Thu, Oct 13, 2011 at 18:48, Gerd Hoffmann<kraxel@redhat.com>  wrote:
>> On 10/13/11 04:09, TeLeMan wrote:
>>> On Wed, Oct 12, 2011 at 19:30, Gerd Hoffmann<kraxel@redhat.com>    wrote:
>>>> qemu uses the ps/2 mouse by default.  The usb tablet (or mouse) is
>>>> activated as soon as qemu sees some guest activity on the device,
>>>> i.e. polling for HID events.  That used to work fine for both fresh
>>>> boot and migration.
>>> It does not fix usb tablet/mouse when starting vm directly from snapshot.
>> What does "info mice" print before/after snapshotting?
>> Which guest?  WinXP IIRC?
> Yes, the guest is WinXP.
>
> Original:
> * Mouse #1: QEMU HID Tablet (absolute)
>    Mouse #0: QEMU PS/2 Mouse
>
> Start from the snapshot:
> * Mouse #0: QEMU PS/2 Mouse
>    Mouse #1: QEMU HID Tablet (absolute)
>
> The active mouse device is not be saved into the snapshot.
it seems that the active mouse event receiver is messed up up after 
loading a vm.

if you issue a 'mouse_set 1' in the qemu monitor the tablet should work 
again.

can someone who is more familiar with the loadvm code check if the 
devices are just added in wrong order?

thanks
peter

      parent reply	other threads:[~2012-02-21 16:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-12 11:30 [Qemu-devel] [PATCH] usb-hid: activate usb tablet / mouse after migration Gerd Hoffmann
2011-10-13  2:09 ` TeLeMan
2011-10-13 10:48   ` Gerd Hoffmann
2011-10-16  8:54     ` TeLeMan
2011-10-21  9:22       ` Gerd Hoffmann
2012-02-20 10:42         ` Peter Lieven
2012-02-21 16:25       ` Peter Lieven [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4F43C585.9000609@dlh.net \
    --to=pl@dlh.net \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.