From: Mark Wu <wudxw@linux.vnet.ibm.com>
To: Corey Bryant <coreyb@linux.vnet.ibm.com>
Cc: rmarwah@linux.vnet.ibm.com, aliguori@us.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3 4/4] Add support for net bridge
Date: Thu, 03 Nov 2011 11:10:16 +0800 [thread overview]
Message-ID: <4EB20618.3040600@linux.vnet.ibm.com> (raw)
In-Reply-To: <1320086191-23641-5-git-send-email-coreyb@linux.vnet.ibm.com>
On 11/01/2011 02:36 AM, Corey Bryant wrote:
> The default bridge that we attach to is br0. The thinking is that a distro
> could preconfigure such an interface to allow out-of-the-box bridged networking.
>
> Alternatively, if a user wants to use a different bridge, they can say:
>
> qemu linux.img -net bridge,br=qemubr0 -net nic,model=virtio
>
> or:
>
> qemu linux.img -net tap,helper=/usr/local/libexec/qemu-bridge-helper,br=qemubr0
> -net nic,model=virtio
>
With this series of patches, I can also use "bridge" with the option
"-netdev". So do you think we need update the doc for 'netdev' too?
qemu-system-x86_64 ../rhel61.img --enable-kvm -m 1024 -netdev
bridge,br=virbr0,helper=/usr/local/libexec/qemu-bridge-helper,id=port1
-device virtio-net-pci,netdev=port1,id=nic1
Forgot to point out this in last post. Sorry for that.
next prev parent reply other threads:[~2011-11-03 3:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 18:36 [Qemu-devel] [PATCH v3 0/4] -net bridge: rootless bridge support for qemu Corey Bryant
2011-10-31 18:36 ` [Qemu-devel] [PATCH v3 1/4] Add basic version of bridge helper Corey Bryant
2011-11-01 8:15 ` Stefan Hajnoczi
2011-11-01 13:52 ` Corey Bryant
2011-10-31 18:36 ` [Qemu-devel] [PATCH v3 2/4] Add access control support to qemu " Corey Bryant
2011-10-31 18:36 ` [Qemu-devel] [PATCH v3 3/4] Add cap reduction support to enable use as SUID Corey Bryant
2011-10-31 18:36 ` [Qemu-devel] [PATCH v3 4/4] Add support for net bridge Corey Bryant
2011-11-03 3:10 ` Mark Wu [this message]
2011-11-03 20:04 ` Corey Bryant
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=4EB20618.3040600@linux.vnet.ibm.com \
--to=wudxw@linux.vnet.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=coreyb@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=rmarwah@linux.vnet.ibm.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).