public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Charles Duffy <Charles_Duffy@messageone.com>
To: kvm@vger.kernel.org
Subject: Re: Trouble understanding net config options
Date: Wed, 15 Jul 2009 19:03:43 -0500	[thread overview]
Message-ID: <4A5E6E5F.9010208@messageone.com> (raw)
In-Reply-To: <f02c30210907151641g786c9798q91bab35962ebda6b@mail.gmail.com>

Michael Jinks wrote:
> On Wed, Jul 15, 2009 at 6:24 PM, Chris Webb<chris@arachsys.com> wrote:
>> You want
>>
>>  -net nic,vlan=0 -net tap,vlan=0,ifname=tap11 -net nic,vlan=1 -net tap,vlan=1,ifname=tap12
> 
> Progress!  This works, I can bring up the guest and watch it boot, but
> both of its NICs came up bound to the first bridge on the system.
> 
> I can work around that using 'brctl delif' and 'brctl addif' on the
> host system, but how would I automate it so that, say, tap11 always
> goes to br1, and tap12 always goes to br0?  I guess by taking out the
> brctl in the kvm ifup script, and pre-setting all my bridge/tap
> connections?

Use the script= argument on the -net tap,vlan=1 to use a qemu-ifup 
script which connects the tap device to the bridge you'd prefer be used.


  reply	other threads:[~2009-07-16  0:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-15 22:54 Trouble understanding net config options Michael Jinks
2009-07-15 23:05 ` Stephane Bakhos
2009-07-15 23:08   ` Michael Jinks
2009-07-15 23:12     ` Stephane Bakhos
2009-07-15 23:12   ` Andreas Plesner Jacobsen
2009-07-15 23:17     ` Michael Jinks
2009-07-15 23:24       ` Chris Webb
2009-07-15 23:41         ` Michael Jinks
2009-07-16  0:03           ` Charles Duffy [this message]
2009-07-15 23:48     ` Andreas Plesner Jacobsen
2009-07-15 23:07 ` Andreas Plesner Jacobsen
2009-07-15 23:22   ` Michael Jinks
2009-07-15 23:27     ` Stephane Bakhos
2009-07-15 23:35     ` Andreas Plesner Jacobsen
2009-07-15 23:42       ` Michael Jinks

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=4A5E6E5F.9010208@messageone.com \
    --to=charles_duffy@messageone.com \
    --cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox