qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] vmmouse


From: Rick Vernam
Subject: Re: [Qemu-devel] vmmouse
Date: Thu, 29 Jan 2009 23:38:51 -0600
User-agent: KMail/1.11.0 (Linux/2.6.27.10; KDE/4.2.0; x86_64; svn-917832; 2009-01-21)

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: qemu-w2k.png
Description: PNG image


reply via email to

[Prev in Thread] Current Thread [Next in Thread]