From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: pvfb: Absolute vs relative mouse tracking mystery Date: Mon, 02 Aug 2010 12:00:25 -0700 Message-ID: <4C5715C9.3030006@goop.org> References: <4BE49501.6000408@goop.org> <4BE86945.9050408@goop.org> <20100619154145.GM17817@reaktio.net> <4C1CE6DE.8000602@goop.org> <4C1F7DC4.3090706@oracle.com> <4C1F7E58.8030605@goop.org> <4C55C6CD.40200@brandeis.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4C55C6CD.40200@brandeis.edu> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Joshua West Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 08/01/2010 12:11 PM, Joshua West wrote: > On 06/21/2010 10:59 AM, Jeremy Fitzhardinge wrote: >> On 06/21/2010 03:57 PM, John Haxby wrote: >>> On 19/06/10 16:48, Jeremy Fitzhardinge wrote: >>>> Yes, that should be fixed in current xen-unstable - it was a xenbus >>>> race-condition. What guest are you seeing it in? I've found that I >>>> still don't get absolute pointers in Centos guests. >>>> >>>> >>> Do you know what the changeset it? This has been bugging me for a >>> while -- every now and again (just to taunt me) I get an absolute >>> pointer. >> It's in the qemu code, so you may need to explicitly make sure that has >> been updated: "cd tools/ioemu-remote; git pull". >> >> J >> >> _______________________________________________ >> Xen-devel mailing list >> Xen-devel@lists.xensource.com >> http://lists.xensource.com/xen-devel > Jeremy, > > Do you know if this will be fixed in the Xen 3.4.x series as well? In > the 3.4.x ioemu-remote qemu code and the 2.6.18.8 xen kernel? > > I ask because this is an issue for me on RHEL5 domU's which are > paravirtualized. Using Xen 3.4.3 w/ Xen kernel 2.6.18.8 and I'm not > yet ready to switch production clusters to 4.0.x. RHEL/CentOS5 deliberately avoids using the absolute pointer mode for reasons I don't understand, so it is broken as expected. J