From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Xen 4.0.0-rc5 with xen/stable 2.6.32.9 dom0 kernel, blktap2, relative mouse Date: Thu, 04 Mar 2010 10:24:07 -0800 Message-ID: <4B8FFAC7.9040204@goop.org> References: <20100304154421.GA2761@reaktio.net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <20100304154421.GA2761@reaktio.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?ISO-8859-1?Q?Pasi_K=E4rkk=E4inen?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 03/04/2010 07:44 AM, Pasi K=E4rkk=E4inen wrote: > Also it seems pvfb uses the broken 'relative' mouse instead of 'absolut= e', > any ideas why that happens? > =20 I've noticed that too. I poked around a little to try and work out what=20 was going on, but I got stuck. "xinput" is showing the pointer device=20 is "absolute" in the domain, which looks OK - but it is still getting=20 relative motion. Are you using vnc? J