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>
Subject: Re: [Fwd: [Xen-users] two serial port in HVM DomU patch]
Date: Sun, 6 Jan 2008 22:42:12 +0000 [thread overview]
Message-ID: <20080106224212.GC5345@redhat.com> (raw)
In-Reply-To: <C3A70A0B.11C24%Keir.Fraser@cl.cam.ac.uk>
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 -=|
prev parent reply other threads:[~2008-01-06 22:42 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
2008-01-06 22:43 ` Keir Fraser
2008-01-06 22:42 ` Daniel P. Berrange [this message]
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=20080106224212.GC5345@redhat.com \
--to=berrange@redhat.com \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=s.seitz@netz-haut.de \
--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.