From mboxrd@z Thu Jan 1 00:00:00 1970 From: jim burns Subject: Re: Problems with 'xl create winxp' (hvm) on xen 4.1.2 (also affects GPLPV) Date: Tue, 01 Nov 2011 15:52:14 -0400 Message-ID: <3160759.Xnf0bZpx0m@dell4550> References: <1758215.SCbitK4oVy@dell4550> <15732981.uFr7VF8Mh1@dell4550> <1320151775.3084.16.camel@cthulhu.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <1320151775.3084.16.camel@cthulhu.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" , "xen-users@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On Tue November 1 2011, 9:49:35 PM, Ian Campbell wrote: > On Mon, 2011-10-31 at 19:00 -0400, jim burns wrote: > > > that's the source of one of the missing features. Fixing it should > > > > be a > > > > > case of adding the option to libxl_domain_build_info in the IDL, > > > reacting to it in libxl__build_device_model_args_old and > > > libxl__build_device_model_args_new and parsing the config file > > > > option > > > > > into it in parse_config_data(). > > > > Hopefully, the fix for 3) (vncconsole=1) is just as simple. > > Rather than having libxl__build_device..._args handling things I think > you would want to call libxl_vncviewer_exec from xl, at roughly the same > sort of place as libxl_console_exec is called when -c is passed to > create, that is wherever autoconnect_console is called. > > (aside: would a command line option similar to -c but for VNC be as/more > useful than the vncauto thing in the cfg?). > Hmm - I suppose it would be more symmetric. You have '-c' for 'xm/xl create', corresponding to 'xm/xl console'. I suppose '-vnc' (or whatever) would then correspond to 'xm/xl vncviewer'. I personally prefer the 'vncauto thing', as I always want to see the boot msgs, and I don't want to miss any because I forgot to add the option, and have to do a 'xm/xl vncviewer/console' after some of the msgs have scrolled away. (It's amazing how some stdout/errout msgs never make it into a log file.)