From: jd <jdsw2002@yahoo.com>
To: "Alberto Treviño" <alberto@byu.edu>
Cc: KVM List <kvm@vger.kernel.org>
Subject: Re: KVM Management : Public Bridge setup
Date: Tue, 12 Aug 2008 10:39:59 -0700 (PDT) [thread overview]
Message-ID: <187398.31839.qm@web35803.mail.mud.yahoo.com> (raw)
In-Reply-To: <200808112112.12363.alberto@byu.edu>
Neat.
Thanks
/Jd
--- On Mon, 8/11/08, Alberto Treviño <alberto@byu.edu> wrote:
> From: Alberto Treviño <alberto@byu.edu>
> Subject: Re: KVM Management : Public Bridge setup
> To: "jdsw2002@yahoo.com" <jdsw2002@yahoo.com>
> Cc: "KVM List" <kvm@vger.kernel.org>
> Date: Monday, August 11, 2008, 8:12 PM
> On Friday 08 August 2008 08:18:26 pm jd wrote:
> > The /etc/qemu-if script seems to be taking the
> interface as a
> > parameter, is there a way to pass the bridge name to
> the script as well.
> > Thus from the command line one can pass the bridge
> that one whats to
> > attach to. (One can potentially one script for each
> bridge and pass the
> > script name to qemu... but it seems bit unnecessary.)
>
> I name my tap devices (using ifname=...) as follows:
>
> tap.br0.05.1
>
> where
> tap -- this is a tap device
> br0 -- the name of the bridge
> 05 -- the ID of the VM (each of my VM's has a
> unique numeric ID)
> 1 -- The NIC # on the VM (1, 2, 3, or 4 depending on #
> of NIC's)
>
> Then on my scripts I can extract the bridge name and use
> it. This also has
> the advantage of helping me know just by the name what
> bridge this devices
> is hooked up to, what VM it belongs to, and which NIC it is
> inside the VM.
> --
> To unsubscribe from this list: send the line
> "unsubscribe kvm" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at
> http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-08-12 17:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-09 2:18 KVM Management : Public Bridge setup jd
2008-08-09 15:43 ` Anthony Liguori
2008-08-09 21:19 ` jd
2008-08-12 3:12 ` Alberto Treviño
2008-08-12 17:39 ` jd [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=187398.31839.qm@web35803.mail.mud.yahoo.com \
--to=jdsw2002@yahoo.com \
--cc=alberto@byu.edu \
--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