From: Jeremy Katz Subject: Re: [RFC][PATCH] auto-starting viewer for virtual frame buffer Date: Sat, 02 Sep 2006 09:19:23 -0400 Message-ID: <1157203163.15940.13.camel@aglarond.local> References: <44F8327F.D169.003C.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <44F8327F.D169.003C.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Charles Coffing Cc: xen-devel@lists.xensource.com, Markus Armbruster List-Id: xen-devel@lists.xenproject.org On Fri, 2006-09-01 at 15:17 -0400, Charles Coffing wrote: > It seems that discussion of the virtual frame buffer has died down; I assume this > is being held off until after 3.0.3 splits... I sent a new set of patches about a week ago. There was then a rundown of some concerns and Markus has gone through and fixed up most of those. I'll hopefully be posting an updated series with the patches later today -- just a matter of integrating the fixes, splitting out patches, etc. > Nevertheless, I was playing with it and wanted to put this patch out for > discussion. This patch is a rough attempt to make the SDL/VNC viewers behave > similarly for both paravirtual and fully virtual domains. For example, if you > specify "sdl=1" in a paravirtual config file, "xm create" will cause sdlfb to > start automatically. > > My desire is to make para vs. full not appear so different to the casual user. > Config file syntax should be similar, viewers should start in similar ways, etc. Agree 100% -- my last set of patches mostly implemented everything needed here. I think the only thing that's not being done similar between PV and FV with them is vncviewer. Which should be pretty trivial, it's just not one that I regularly use so I haven't gotten the itch. Jeremy