From: jd <jdsw2002@yahoo.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: KVM List <kvm@vger.kernel.org>
Subject: Re: KVM Management : Public Bridge setup
Date: Sat, 9 Aug 2008 14:19:28 -0700 (PDT) [thread overview]
Message-ID: <789449.59515.qm@web35805.mail.mud.yahoo.com> (raw)
In-Reply-To: <489DBB21.5040603@codemonkey.ws>
cool..... why didnt I think of that.
Will try that out. Thanks.
/Jd
--- On Sat, 8/9/08, Anthony Liguori <anthony@codemonkey.ws> wrote:
> From: Anthony Liguori <anthony@codemonkey.ws>
> Subject: Re: KVM Management : Public Bridge setup
> To: jdsw2002@yahoo.com
> Cc: "KVM List" <kvm@vger.kernel.org>
> Date: Saturday, August 9, 2008, 8:43 AM
> jd wrote:
> > Hi
> > 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.)
> >
>
> Environmental variables passed to the QEMU process can be
> used by the
> scripts. For instance, if you use $BRIDGE_NAME in the
> script, then you
> would start QEMU with:
>
> BRIDGE_NAME=br1 qemu-system-x86_64 ....
>
> Regards,
>
> Anthony Liguori
>
> > Thanks
> > /Jd
> >
> >
> >
> > --
> > 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
> >
next prev parent reply other threads:[~2008-08-09 21:19 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 [this message]
2008-08-12 3:12 ` Alberto Treviño
2008-08-12 17:39 ` jd
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=789449.59515.qm@web35805.mail.mud.yahoo.com \
--to=jdsw2002@yahoo.com \
--cc=anthony@codemonkey.ws \
--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