WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] pvfb: Absolute vs relative mouse tracking mystery

On Wed, Jul 21, 2010 at 06:01:28PM -0700, Jeremy Fitzhardinge wrote:
> >>>>>>>>                 
> >>>>>>>>> On one of my host machines, in PV guests using pvfb I get proper
> >>>>>>>>> absolute mouse tracking.
> >>>>>>>>>
> >>>>>>>>> On another host machine, I get relative tracking in pvfb-using 
> >>>>>>>>> guests.
> >>>>>>>>>
> >>>>>>>>> Both are using identical versions of Fedora 12, identical domain
> >>>>>>>>> configs, and toolstacks and kernels built from the same source.  
> >>>>>>>>> The log
> >>>>>>>>> files of the X servers are more or less identical.
> >>>>>>>>>
> >>>>>>>>> Help?  Any clues?
> >>>>>>>>>
> >>>>>>>>>     
> >>>>>>>>>           
> >>>>>>>>>               
> >>>>>>>>>                   
> >>>>>>>> relative vs absolute depends on a node on xenstore called
> >>>>>>>> "request-abs-pointer" that defaults to 0 and has to be written by the
> >>>>>>>> guest.
> >>>>>>>>   
> >>>>>>>>         
> >>>>>>>>             
> >>>>>>>>                 
> >>>>>>> OK, it looks like it is being set, but the guest is still showing
> >>>>>>> relative behaviour:
> >>>>>>>
> >>>>>>>     vkbd = ""
> >>>>>>>      0 = ""
> >>>>>>>       backend = "/local/domain/0/backend/vkbd/5/0"
> >>>>>>>       backend-id = "0"
> >>>>>>>       state = "4"
> >>>>>>>       page-ref = "1137660"
> >>>>>>>       event-channel = "11"
> >>>>>>>       request-abs-pointer = "1"
> >>>>>>>
> >>>>>>> Does this mean qemu-dm's vnc server is not doing the right thing?
> >>>>>>>       
> >>>>>>>           
> >>>>>>>               
> >>>>>>  
> >>>>>> I think is probably xenfb (that is the framebuffer backend in qemu) 
> >>>>>> that
> >>>>>> is not doing the right thing.
> >>>>>> Try adding some debug output in hw/xenfb.c:input_connect.
> >>>>>>
> >>>>>>     
> >>>>>>         
> >>>>>>             
> >>>>> Jeremy: Did you figure this out? I'm again seeing this problem on my 
> >>>>> Fedora 13 + Xen 4.0.1-rc3-pre box..
> >>>>>   
> >>>>>       
> >>>>>           
> >>>> 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.
> >>>>
> >>>>     
> >>>>         
> >>> Yeah, it's a CentOS 5.5 guest that gets relative pointer on my Fedora 13 
> >>> dom0.
> >>> On a CentOS5 dom0 it gets absolute though..
> >>>
> >>> Fedora 13 guest gets absolute pointer on my Fedora 13 dom0..
> >>>   
> >>>       
> >> Huh, that is interesting.  Maybe there's still a race or something there...
> >>
> >>     
> > Yeah.. maybe. Note that I'm running Xen 4.0.1-rc3-pre and not xen-unstable..
> >   
> 
> I just got a Win7 hvm domain working for the first time in a while, and
> found that it *isn't* getting proper abs updates.  I even set
> usbdevice='tablet' in its config...
> 

Ok. And reading my own lines above, I realize F13 worked for me earlier,
but it was centos 5.5 that didn't work.

I'll have to re-test things here aswell :)

-- Pasi


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel