Re: Problems with 'xl create winxp' (hvm) on xen 4.1.2 (also affects GPLPV)

[jim burns <jim_burn@bellsouth.net>]

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