qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Rick Vernam <rickv@hobi.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] vmmouse
Date: Thu, 29 Jan 2009 23:38:51 -0600	[thread overview]
Message-ID: <200901292338.52191.rickv@hobi.com> (raw)
In-Reply-To: <200901282248.26006.rickv@hobi.com>

[-- Attachment #1: Type: text/plain, Size: 2375 bytes --]

On Wednesday 28 January 2009 10:48:25 pm Rick Vernam wrote:
> For the past few days (10-15, longer?) both my windows vms seem to have
> broken mice - the mouse cursor does not move in the guest...
> Both guests run windows (2k,xp) and both have vmware mouse driver installed
> (not sure which version, off the top of my head).
>
> I've not followed the list too closely during this time period either - in
> trying to catch up tonight I haven't seen anything on this subject, so I'm
> posting to see if this is a known issue...
>
> I built qemu with DEBUG_VMMOUSE turned on in hw/vmmouse.c.
> When I run qemu I get a single vmmouse_init right when qemu starts, but
> then no additional output.

(btw, Revision: 6476)

On  Win XP guest, in addition to the broken vmmouse, windows perpetually tells 
me that a new video controller has been detected.  I assume it's talking about 
the vmware-vga device, so I've tried installing vmware's video drivers from 
workstation 5.0.1, 5.5.9 & 6.0.5.  (this also started happening at the same 
time as the vmmouse dying, I just didn't mention it before).


vmware-vga is also broken with a w2k guest (see attached screenshot).  
Although, it has adjusted the sdl window to the correct resolution.

It seems I was mistaken before when I said vmmouse didn't work in w2k guest - 
it does works fine with w2k guest.
I get many debug_vmmouse messages like so:
vmmouse_get_status()
set_data = {0, 0, 28, 5658, 80471854, 818700d8}
vmmouse_mouse_event(0, 0, 0, 0)
get_data = {564d5868, 0, 80420028, 817a5658, 817a05e8, 0}
vmmouse_get_status()
set_data = {4, 0, 80420028, 817a5658, 817a05e8, 0}
get_data = {564d5868, 4, 80420027, 817a5658, 817a05e8, 0}
vmmouse_data(4)
set_data = {0, 0, 0, 0, 817a05e8, 0}
get_data = {564d5868, 0, 28, 5658, 80471854, 818700d8}
vmmouse_get_status()
set_data = {0, 0, 28, 5658, 80471854, 818700d8}
get_data = {564d5868, 0, 28, 5658, 80471854, 818700d8}
vmmouse_get_status()
set_data = {0, 0, 28, 5658, 80471854, 818700d8}
get_data = {564d5868, 0, 28, 5658, 80471854, 818700d8}
vmmouse_get_status()
set_data = {0, 0, 28, 5658, 80471854, 818700d8}
get_data = {564d5868, 0, 28, 5658, 80471854, 818700d8}
vmmouse_get_status()
set_data = {0, 0, 28, 5658, 80471854, 818700d8}

It seems to vmware stuff is affected universally.  I'm going to try to narrow 
down an SVN commit tomorrow, if I can get some time...

Thanks.

[-- Attachment #2: qemu-w2k.png --]
[-- Type: image/png, Size: 21299 bytes --]

      parent reply	other threads:[~2009-01-30  5:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  4:48 [Qemu-devel] vmmouse Rick Vernam
2009-01-29 20:58 ` Juergen Lock
2009-01-29 21:31   ` Rick Vernam
2009-01-29 21:56     ` Anthony Liguori
2009-01-29 23:20       ` andrzej zaborowski
2009-01-29 23:28         ` François Revol
2009-01-29 23:29         ` Rick Vernam
2009-02-01 23:48         ` Juergen Lock
2009-01-29 21:56   ` François Revol
2009-01-30  5:38 ` Rick Vernam [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=200901292338.52191.rickv@hobi.com \
    --to=rickv@hobi.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).