From: Chris Lalancette <clalance@redhat.com>
To: Mike Snitzer <snitzer@gmail.com>
Cc: Bill Davidsen <davidsen@tmr.com>, kvm@vger.kernel.org
Subject: Re: Simple way of putting a VM on a LAN
Date: Fri, 27 Jun 2008 09:04:50 +0200 [thread overview]
Message-ID: <48649112.7000704@redhat.com> (raw)
In-Reply-To: <170fa0d20806262146s5710198cw7072aeaac4c7f39f@mail.gmail.com>
Mike Snitzer wrote:
> I've taken to using a bridge (or in virt-manager speak "shared
> physical device"). The 'network-bridge' script (and supporting
> xen-network-common.sh and xen-script-common.sh) that are provided with
> xen rpms (e.g. xen-3.1.0-13.fc8.x86_64.rpm) make this relatively
> painless.
>
> The overall solution is not what I'd call "simple" but once I've
> started the bridge I just defer to libvirtd to abstract away the
> complexity associated with exposing each kvm guest to the physical
> network.
Yep, exactly. Actually, generally your distribution of choice provides nice
startup scripts to such things; in Fedora, you create an
/etc/sysconfig/network-scripts/ifcfg-eth0 that has a BRIDGE=br0, and an
/etc/sysconfig/network-scripts/ifcfg-br0 that defines the actual bridge with
TYPE=Bridge, and the system will bring up the bridge at bootup and plug your
eth0 into it. I'm sure the other distributions have similar mechanisms.
Chris Lalancette
next prev parent reply other threads:[~2008-06-27 7:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-27 1:54 Simple way of putting a VM on a LAN Bill Davidsen
2008-06-27 4:46 ` Mike Snitzer
2008-06-27 7:04 ` Chris Lalancette [this message]
2008-07-09 16:28 ` Bill Davidsen
2008-07-09 17:23 ` Javier Guerra
2008-07-24 4:15 ` Bill Davidsen
2008-07-24 14:22 ` Javier Guerra
2008-07-25 16:44 ` Bill Davidsen
2008-07-25 22:31 ` Stuart Jansen
2008-07-26 17:26 ` Bill Davidsen
2008-06-27 22:44 ` Freddie Cash
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=48649112.7000704@redhat.com \
--to=clalance@redhat.com \
--cc=davidsen@tmr.com \
--cc=kvm@vger.kernel.org \
--cc=snitzer@gmail.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