From mboxrd@z Thu Jan 1 00:00:00 1970 From: Chris Lalancette Subject: Re: Simple way of putting a VM on a LAN Date: Fri, 27 Jun 2008 09:04:50 +0200 Message-ID: <48649112.7000704@redhat.com> References: <170fa0d20806262146s5710198cw7072aeaac4c7f39f@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Bill Davidsen , kvm@vger.kernel.org To: Mike Snitzer Return-path: Received: from mx1.redhat.com ([66.187.233.31]:46754 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751185AbYF0HFu (ORCPT ); Fri, 27 Jun 2008 03:05:50 -0400 In-Reply-To: <170fa0d20806262146s5710198cw7072aeaac4c7f39f@mail.gmail.com> Sender: kvm-owner@vger.kernel.org List-ID: 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