From: Markus Armbruster Subject: Re: Re: [PATCH 0/2] PV framebuffer Date: Wed, 22 Nov 2006 16:31:09 +0100 Message-ID: <87mz6j8pmq.fsf@pike.pond.sub.org> References: <87odrfptrb.fsf@pike.pond.sub.org> <877ixudx7m.fsf@pike.pond.sub.org> <20061122141801.GA3186@cam.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: <20061122141801.GA3186@cam.ac.uk> (Steven Smith's message of "Wed, 22 Nov 2006 14:18:01 +0000") List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Steven Smith Cc: xen-devel@lists.xensource.com, sos22@srcf.ucam.org List-Id: xen-devel@lists.xenproject.org Steven Smith writes: >> Next iteration. If there's anything left in the way of getting this >> merged, please let me know right away. > I hit a couple of problems when testing this: > > 1) It breaks existing configurations. Changing the xencons default > from xencons=tty to xencons=xvc means that any existing > configurations with gettys etc. set up on /dev/tty1 rather than > /dev/xvc0 will no longer work. That really isn't an option. Done. > 2) The mouse pointer displayed by X or gpm and the pointer as sent by > the client often get out of sync. It looks like X is getting > relative mouse movement messages rather than absolute. The backend > is definitely generating absolute position messages, so I'm not > sure what's going on there. It's possible I've just messed up the > configuration inside the domain. What pointer device did you use? Almost all use relative modes, including tablets. > 3) The backend doesn't do the shutdown protocol correctly. This leads > to > > xenbus_dev_shutdown: device/vkbd/0 timeout closing device > > messages on the console when you try and shut the domain down. > These are more irritants than actual problems, but it'd be good to > get them fixed. Sure. I'd prefer to finish resume first. Still trying to figure out why xm restore doesn't restart the backend. > I'm kind of bogged down with other stuff at the moment, so I'm not > going to be able to look at the patches in detail until next week, but > I figure that should be enough to keep you busy for a little while. :) Sigh...