From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] specify vmchannel as part of "user" net option
Date: Thu, 15 Jan 2009 23:58:21 +0000 [thread overview]
Message-ID: <20090115235821.GA18237@redhat.com> (raw)
In-Reply-To: <20090115205459.GA27165@redhat.com>
On Thu, Jan 15, 2009 at 10:54:59PM +0200, Gleb Natapov wrote:
> On Thu, Jan 15, 2009 at 02:24:05PM -0600, Anthony Liguori wrote:
> > Gleb Natapov wrote:
> >> To configure vmchannel and something like this to -net user:
> >> channels=;777:unix:/tmp/777,server
> >>
> >
> > I'd really like to avoid using ';' as a deliminator. Is the a more
> > clever way we can do this without it totally sucking?
> >
> I can't say I like it, but we can't use ',' and ':' as parsing will be
> ambiguous. So what's left?
Perhaps this is a sign that we should not try to overload it all into
one argument after all. How about just having a separate -net option
for each channel we wish to hook onto a NIC - a little cleverness
behind the scenes could make them all backed by a single Slirp device,
without forcing them to use a single ARGV for config
eg
qemu -net nic,vlan=8 \
-net channel=666,vlan=8,:unix:/tmp/666,server,nowait \
-net channel=777,vlan=8,:unix:/tmp/777,server
Regards,
Daniel
--
|: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :|
|: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|
prev parent reply other threads:[~2009-01-15 23:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-11 15:10 [Qemu-devel] [PATCH] specify vmchannel as part of "user" net option Gleb Natapov
2009-01-15 20:24 ` Anthony Liguori
2009-01-15 20:54 ` Gleb Natapov
2009-01-15 21:27 ` Anthony Liguori
2009-01-15 23:58 ` 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=20090115235821.GA18237@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.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.