From: Mark Cave-Ayland <mark.cave-ayland@siriusit.co.uk>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] NT4 guest mouse failure under qemu 0.9.1
Date: Fri, 23 May 2008 12:07:54 +0100 [thread overview]
Message-ID: <4836A58A.5010700@siriusit.co.uk> (raw)
Hi everyone,
I've noticed another failure within our qemu 0.9.1 NT4 guest with
relation to the PS2 mouse driver. After several minutes of normal use,
the mouse pointer suddenly goes mad, with the slightest touch of the
mouse causing the pointer to go flying around the screen. The only
solution to this problem is to reboot the VM instance :(
Looking at the NT4 Event Log, I see the following messages when this occurs:
An unexpected RESET was detected from the mouse device
Followed by:
Could not set the mouse sample rate
The latter message is repeated in the event log when the mouse is moved
until the VM is rebooted. Has anyone experienced this behaviour before?
Many thanks,
Mark.
--
Mark Cave-Ayland
Sirius Corporation - The Open Source Experts
http://www.siriusit.co.uk
T: +44 870 608 0063
next reply other threads:[~2008-05-23 11:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-23 11:07 Mark Cave-Ayland [this message]
2008-05-24 12:02 ` [Qemu-devel] NT4 guest mouse failure under qemu 0.9.1 Mark Cave-Ayland
2008-05-24 13:14 ` Alexander Graf
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=4836A58A.5010700@siriusit.co.uk \
--to=mark.cave-ayland@siriusit.co.uk \
--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).