From: Anthony PERARD <anthony.perard@citrix.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Xen Devel <xen-devel@lists.xen.org>
Subject: Re: [RFC 4/6] libxl: Add "stubdomain_version" to domain_build_info.
Date: Mon, 22 Apr 2013 14:31:06 +0100 [thread overview]
Message-ID: <51753B9A.5070503@citrix.com> (raw)
In-Reply-To: <1366363786.19111.76.camel@zakaz.uk.xensource.com>
On 19/04/13 10:29, Ian Campbell wrote:
> On Wed, 2013-04-17 at 20:09 +0100, Anthony PERARD wrote:
>> This enum give the ability to select between the MiniOS based stubdomain
>> and the Linux based stubdomain. It can be written in a VM config file via
>> "stubdomain_version" variable, but will be automatically filled by the
>> appropriate value depending on the device_model_version. To use the
>> stubdomain, it's the same config option
>> "devive_model_stubdomain_override=1" to force the stubdomain.
>
> Given that there is no actual choice available (it's minios for
> qemu-xen-trad and Linux for qemu-xen) at the moment perhaps we should
> just leave this option out for now and cross this bridge if/when there
> is a real choice to be made?
I feel like this will be an easier thing to do for now.
> If we do want to keep this then I think I'd prefer to see us extend the
> semantics of device_model_stubdomain_override to be more than a simple
> boolean, e.g. make it a libxl enum libxl_device_model_stubdomain_type:
> 0 = "none" => process dm in dom0
> 1 = "minios" => mini-os based stubdom
> 2 = "linux" => ...
> 3 = "foobsd" => ...
With this, I don't see how to say: "I want a stubdom for this domain."
without having to know which type will be the best (or only) choice. So
I go for the no choice for the user, beside stubdom or not.
--
Anthony PERARD
next prev parent reply other threads:[~2013-04-22 13:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-17 19:09 [RFC 0/6] RFC Linux based stub-domain Anthony PERARD
2013-04-17 19:09 ` [RFC 1/6] linux-stubdomain: Compile QEMU Anthony PERARD
2013-04-17 19:09 ` [RFC 2/6] linux-stubdomain: Compile Linux Anthony PERARD
2013-04-19 10:33 ` Stefano Stabellini
2013-04-22 13:46 ` Anthony PERARD
2013-04-22 13:59 ` Daniel De Graaf
2013-04-22 14:09 ` Samuel Thibault
2013-04-17 19:09 ` [RFC 3/6] linux-stubdomain: Build a disk image Anthony PERARD
2013-04-19 9:26 ` Ian Campbell
2013-04-19 11:58 ` Anthony PERARD
2013-04-19 12:08 ` Ian Campbell
2013-04-19 13:53 ` Samuel Thibault
2013-04-17 19:09 ` [RFC 4/6] libxl: Add "stubdomain_version" to domain_build_info Anthony PERARD
2013-04-19 9:29 ` Ian Campbell
2013-04-22 13:31 ` Anthony PERARD [this message]
2013-04-22 14:36 ` Ian Campbell
2013-04-17 19:09 ` [RFC 5/6] libxl: Handle Linux stubdomain specifique QEMU option Anthony PERARD
2013-04-19 9:31 ` Ian Campbell
2013-04-22 13:37 ` Anthony PERARD
2013-04-17 19:09 ` [RFC 6/6] libxl: Build the domain with a Linux based stubdomain Anthony PERARD
2013-04-19 9:17 ` [RFC 0/6] RFC Linux based stub-domain Ian Campbell
2013-04-19 11:11 ` Anthony PERARD
2013-04-19 12:04 ` David Vrabel
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=51753B9A.5070503@citrix.com \
--to=anthony.perard@citrix.com \
--cc=Ian.Campbell@citrix.com \
--cc=xen-devel@lists.xen.org \
/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.