From: Ian Campbell <Ian.Campbell@citrix.com>
To: jim burns <jim_burn@bellsouth.net>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
"xen-users@lists.xensource.com" <xen-users@lists.xensource.com>
Subject: Re: Problems with 'xl create winxp' (hvm) on xen 4.1.2 (also affects GPLPV)
Date: Tue, 1 Nov 2011 21:49:35 +0900 [thread overview]
Message-ID: <1320151775.3084.16.camel@cthulhu.hellion.org.uk> (raw)
In-Reply-To: <15732981.uFr7VF8Mh1@dell4550>
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?).
Ian.
next prev parent reply other threads:[~2011-11-01 12:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-29 5:57 Problems with 'xl create winxp' (hvm) on xen 4.1.2 (also affects GPLPV) jim burns
2011-10-29 6:17 ` jim burns
2011-10-31 10:56 ` Ian Campbell
2011-10-31 10:50 ` Ian Campbell
2011-10-31 11:26 ` Ian Campbell
2011-10-31 23:00 ` jim burns
2011-11-01 12:49 ` Ian Campbell [this message]
2011-11-01 19:52 ` jim burns
2011-11-03 6:46 ` Stefano Stabellini
2011-11-03 8:39 ` Re: [Xen-devel] " Flavio
2011-11-03 23:33 ` [Xen-users] " Ian Campbell
2011-11-04 1:24 ` Stefano Stabellini
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1320151775.3084.16.camel@cthulhu.hellion.org.uk \
--to=ian.campbell@citrix.com \
--cc=jim_burn@bellsouth.net \
--cc=xen-devel@lists.xensource.com \
--cc=xen-users@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.