From: "Daniel P. Berrange" <berrange@redhat.com>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Stephan Seitz <s.seitz@netz-haut.de>,
XEN Devel - listmembers <xen-devel@lists.xensource.com>,
Samuel Thibault <samuel.thibault@eu.citrix.com>
Subject: Re: [Fwd: [Xen-users] two serial port in HVM DomU patch]
Date: Sun, 6 Jan 2008 22:45:48 +0000 [thread overview]
Message-ID: <20080106224548.GD5345@redhat.com> (raw)
In-Reply-To: <C3A70ABC.11C27%Keir.Fraser@cl.cam.ac.uk>
On Sun, Jan 06, 2008 at 10:46:20PM +0000, Keir Fraser wrote:
> Ah, this is a nice way that continues to support the existing domain config
> format. I'd still also like a dm_args config option too though! Really many
> of the HVM-specific config options could be deprecated and moved over to a
> single dm_args config field.
No no no, please no. The current scheme is good because there are clear
key,value pairs for each individual configuration option. A generic blob
of dm_args will be a huge PITA to deal with, making a mockery of the
attempt at clearly modelling guest config params in XenAPI, as well as the
legacy config formats. It will also increase the divergance in the way
HVM guests are configured vs paravirt guests if we start to shove all the
HVM args into 'dm_args' rather than representing them in a way which works
well for both HVM and PV domains.
Dan.
--
|=- Red Hat, Engineering, Emerging Technologies, Boston. +1 978 392 2496 -=|
|=- Perl modules: http://search.cpan.org/~danberr/ -=|
|=- Projects: http://freshmeat.net/~danielpb/ -=|
|=- GnuPG: 7D3B9505 F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 -=|
next prev parent reply other threads:[~2008-01-06 22:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-31 12:13 [Fwd: [Xen-users] two serial port in HVM DomU patch] Stephan Seitz
2007-12-31 12:32 ` James Harper
2007-12-31 12:41 ` Samuel Thibault
2008-01-06 22:46 ` Keir Fraser
2008-01-06 22:45 ` Daniel P. Berrange [this message]
2008-01-06 22:43 ` Keir Fraser
2008-01-06 22:42 ` Daniel P. Berrange
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=20080106224548.GD5345@redhat.com \
--to=berrange@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=s.seitz@netz-haut.de \
--cc=samuel.thibault@eu.citrix.com \
--cc=xen-devel@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.