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] Re: [PATCH 0/2] PV framebuffer

To: Markus Armbruster <armbru@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH 0/2] PV framebuffer
From: Steven Smith <sos22-xen@xxxxxxxxxxxxx>
Date: Wed, 22 Nov 2006 14:18:01 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, sos22@xxxxxxxxxxxxx
Delivery-date: Wed, 22 Nov 2006 06:16:49 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <877ixudx7m.fsf@xxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <87odrfptrb.fsf@xxxxxxxxxxxxxxxxx> <877ixudx7m.fsf@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> 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.

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.

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.

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. :)

Steven.

Attachment: signature.asc
Description: Digital signature

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