On Thu, Jun 26, 2008 at 9:54 PM, Bill Davidsen <[EMAIL PROTECTED]> wrote: > I seem to be missing the "right way" to put a VM on the LAN such that it > appears to really be a machine on the LAN. This is a requirement for being > able to deploy internal servers as needed. > > For instance, consider a DNS server or outbound mailer at IP 10.x.y.z and > how to do that with a VM. Current I have not found a way other than putting > the IP on as an alias, like eth0:1, setting up a tunnel using a bunch of > stuff from Debian, plugging in a set of moderately complex iptables rules, > starting the VM using a bunch of obscure -nic options unreleated to the > actual IP to be provided, and generally a ton of complexity to install and > remove. > > I often want to provide momentary service not requiring preserving a lot of > state, like mailers, DNS, etc. Surely there's a better way?
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. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
