All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlh.net>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: qemu-kvm-1.0 regression with usb tablet after live migration
Date: Thu, 09 Feb 2012 19:12:19 +0100	[thread overview]
Message-ID: <4F340C83.5050004@dlh.net> (raw)

Hi,

i recently started updating our VMs to qemu-kvm 1.0. Since that I see 
that the usb tablet device (used for as pointer device for accurate
mouse positioning) becomes unavailable after live migrating.
If I migrate a few times a Windows 7 VM reliable stops using
the USB tablet and fails back to PS/2 mouse.
If I do the same with qemu-kvm-0.12.5 with the very same VM its working 
fine.

Can anyone imagine what introduced this flaw?

Thanks,
Peter



WARNING: multiple messages have this Message-ID (diff)
From: Peter Lieven <pl@dlh.net>
To: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] qemu-kvm-1.0 regression with usb tablet after live migration
Date: Thu, 09 Feb 2012 19:12:19 +0100	[thread overview]
Message-ID: <4F340C83.5050004@dlh.net> (raw)

Hi,

i recently started updating our VMs to qemu-kvm 1.0. Since that I see 
that the usb tablet device (used for as pointer device for accurate
mouse positioning) becomes unavailable after live migrating.
If I migrate a few times a Windows 7 VM reliable stops using
the USB tablet and fails back to PS/2 mouse.
If I do the same with qemu-kvm-0.12.5 with the very same VM its working 
fine.

Can anyone imagine what introduced this flaw?

Thanks,
Peter

             reply	other threads:[~2012-02-09 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-09 18:12 Peter Lieven [this message]
2012-02-09 18:12 ` [Qemu-devel] qemu-kvm-1.0 regression with usb tablet after live migration Peter Lieven
2012-02-15  9:26 ` Peter Lieven
2012-02-15  9:26   ` [Qemu-devel] " Peter Lieven

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=4F340C83.5050004@dlh.net \
    --to=pl@dlh.net \
    --cc=kvm@vger.kernel.org \
    --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.