From: Bill Davidsen <davidsen@tmr.com>
To: Chris Lalancette <clalance@redhat.com>
Cc: Mike Snitzer <snitzer@gmail.com>, kvm@vger.kernel.org
Subject: Re: Simple way of putting a VM on a LAN
Date: Wed, 09 Jul 2008 12:28:05 -0400 [thread overview]
Message-ID: <4874E715.8040903@tmr.com> (raw)
In-Reply-To: <48649112.7000704@redhat.com>
Chris Lalancette wrote:
> 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.
>
A bit of the original problem seems to have been clipped before you read
it, or I stated it poorly.
- the problems are immediate, not permanent hosting. So startup
anythings are out, I'd have to put in scripts for every machine I might
ever want to host on every machine capable of hosting.
- I need to bind an IP, unless you can point me to a different bridge
package. If eth0 is x.y.z.10 and I put x.y.z.20 on eth0:1
ifconfig eth0:1 x.y.z.20 up
adding eth0:1 moves the whole NIC to the bridge, and the normal
functions of the machine come to a halt. I'm probably doing something
wrong, currently I'm getting this done by ugly iptables abuse.
I am missing some piece on doing this quickly and selectively, for the
case of "dns02 just dropped a cooling fan, we need another server, run
it on your {whatever} machine for a few minutes." These are immediate
and short term, but often done on machines in burn-in state, someone's
desktop, etc. Little load, but the service must be running.
Does that clarify?
--
Bill Davidsen <davidsen@tmr.com>
"We have more to fear from the bungling of the incompetent than from
the machinations of the wicked." - from Slashdot
next prev parent reply other threads:[~2008-07-09 16:23 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
2008-07-09 16:28 ` Bill Davidsen [this message]
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=4874E715.8040903@tmr.com \
--to=davidsen@tmr.com \
--cc=clalance@redhat.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