WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [Fwd: [Xen-users] two serial port in HVM DomU patch]

To: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] [Fwd: [Xen-users] two serial port in HVM DomU patch]
From: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Date: Sun, 6 Jan 2008 22:45:48 +0000
Cc: Stephan Seitz <s.seitz@xxxxxxxxxxxx>, XEN Devel - listmembers <xen-devel@xxxxxxxxxxxxxxxxxxx>, Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Delivery-date: Sun, 06 Jan 2008 14:46:12 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3A70ABC.11C27%Keir.Fraser@xxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <20071231124111.GB5447@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <C3A70ABC.11C27%Keir.Fraser@xxxxxxxxxxxx>
Reply-to: "Daniel P. Berrange" <berrange@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.4.1i
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  -=| 

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>