qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Gerhard Wiesinger <lists@wiesinger.com>,
	Jan Kiszka <jan.kiszka@siemens.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] hw/vmmouse.c: Disable vmmouse after reboot
Date: Thu, 26 Jan 2012 09:26:23 +0100	[thread overview]
Message-ID: <4F210E2F.5040706@suse.de> (raw)
In-Reply-To: <alpine.LFD.2.02.1201252103080.21459@bbs.intern>

Am 25.01.2012 21:04, schrieb Gerhard Wiesinger:
> Bugfix after reboot when vmmouse was enabled and another OS which uses
> e.g. PS/2
> mouse.
> 
> Details:
> When a guest activated the vmmouse followed by a reboot the vmmouse was
> still
> enabled and the PS/2 mouse was therefore unsusable. When another guest
> is then
> booted without vmmouse support (e.g. PS/2 mouse) the mouse is not working.
> 
> Reason is that VMMouse has priority and disables all other mouse entities
> and therefore must be disabled on reset.
> 
> Testscenario:
> 1.) Boot e.g. OS with VMMouse support (e.g. Windows with VMMouse tools)
> 2.) reboot
> 3.) Boot e.g. OS without VMMouse support (e.g. DOS) => PS/2 mouse
> doesn't work
>     any more. Fixes that issue.
> 
> Testscenario 2 by Jan Kiszka <jan.kiszka@siemens.com>:
> Confirm that this patch fixes a real issue. Setup: qemu.git,
> opensuse 11.4 guest, SDL graphic, system_reset while guest is using the
> vmmouse. Without the patch, the vmmouse become unusable after the
> reboot. Also, the mouse stays in absolute mode even before X starts again.
> 
> Fixed by:
> Disabling the vmmouse in its reset handler.
> 
> Signed-off-by: Gerhard Wiesinger <lists@wiesinger.com>

I've been able to reproduce this the day before yesterday, on my version
of qemu-kvm 0.15.1 with this patch apparently fixing the mouse after a
kdump.

Yesterday however the reporter applied the patch himself to qemu.git and
reported this patch not to fix it on their side.

We boot into the desktop, then do:
# echo 1 > /proc/sys/kernel/sysrq
# echo c > /proc/sysrq-trigger
System then reboots after a while and at login mouse does or does not work.

I had originally tried to kdump with just a virtio drive w/ default
settings; then I tried with the reporter's setting of -smp 4 (and
cache=unsafe) and was able to reproduce it. Afterwards I was able to
reproduce without -smp 4 as well; no recompilation occurred. Guest was
the same SLES11 SP2 RC2 all the time.

So, is there any indeterminism involved? I.e. is the mouse unusability
maybe not 100% reproducible? Anything else that may need to be fixed
beyond this patch?

Patch does not break anything, so for now:

Tested-by: Andreas Färber <afaerber@suse.de>

Thanks,
Andreas

-- 
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg

  reply	other threads:[~2012-01-26  8:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 20:04 [Qemu-devel] [PATCH] hw/vmmouse.c: Disable vmmouse after reboot Gerhard Wiesinger
2012-01-26  8:26 ` Andreas Färber [this message]
2012-01-27  6:53   ` Gerhard Wiesinger
2012-02-03 17:21 ` Anthony Liguori
2012-02-03 17:57   ` Gerhard Wiesinger
2012-08-22 17:01     ` Andreas Färber
2012-08-22 16:54   ` Andreas Färber

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=4F210E2F.5040706@suse.de \
    --to=afaerber@suse.de \
    --cc=jan.kiszka@siemens.com \
    --cc=lists@wiesinger.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).