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:42:12 +0000
Cc: Stephan Seitz <s.seitz@xxxxxxxxxxxx>, XEN Devel - listmembers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 06 Jan 2008 14:42:36 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C3A70A0B.11C24%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: <4778DCD2.2030300@xxxxxxxxxxxx> <C3A70A0B.11C24%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:43:23PM +0000, Keir Fraser wrote:
> I'd advocate a dm_args domain config option, which would be a string of qemu
> command-line arguments which would be dumbly passed straight through to
> qemu-dm without any further processing by xend.
>
> Then you could just do 'dm_args = "serial=/dev/ttyS0 serial=/dev/ttyS1"' and
> not need any changes to qemu source code at all. And this would also let you
> get at any other underlying features of qemu too. Much nicer.

I think that's a bad idea as any info in this generic 'dm_args' is now lost
to the formal API data model. eg If a management app wants to talk to XenD
and determine how / if the serial port is configured, it now has to look
at both the formally specified 'serial' param, and also parse the command
line args in 'dm_args'.  Sure it means we have to write less code in XenD,
but it means that all users talking to XenD have much more work todo. I
don't really see that as a net win.

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>