public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: "Stefan Krümmel" <skruemmel@wheregroup.com>
Cc: kvm@vger.kernel.org
Subject: Re: using KVM w/o dnsmasq on CentOS 5.2 X64
Date: Mon, 2 Feb 2009 10:52:12 +0000	[thread overview]
Message-ID: <20090202105212.GA31756@redhat.com> (raw)
In-Reply-To: <op.uopyc8cmy1yht0@gate.dev.wheregroup.com>

On Mon, Feb 02, 2009 at 11:06:34AM +0100, Stefan Kr?mmel wrote:
> Hi,
> 
> I'm trying to convert some of our virtual machines from VMWare Server 2 to
> KVM on CentOS 5.2 X64.
> 
> KVM constantly gives me headaches when it comes to networking  
> configuration.
> 
> Being used to VMWare, there are some things that don't work as expected.
> 
> 1. kvm/libvirt manipulate iptables, effectivly breaking the hosts  
> networking
> iptables is usually turned off on the dev machine( iptables -F, no rules  
> set during boot)
>
> 2. kvm/libvirt comes with dnsmasq, which gets started automagically,  
> colliding
> with out existing DDNS setup(ISC's bind/dhcpd3 )

libvirt's dnsmasq instance is told to only listen on the network
interface with 192.168.122.1, but unfortunately most other DHCP
daemons will default to listening on every interface. So if you
already run a DHCP interface you'll want to disable libvirt's
default virtual network

  virsh net-destroy default
  virsh net-autostart --disable default

> I'm hope some of you might shed some light on howto
> 1) bridge a KVM-VM to an exisiting Ethernet interface, behaving exactly  
> like
> a real/physical NIC, being able to handle any  
> ARP/BOOTP/PXE/DHCP/IP/whatever requests.

See the 'Shared physical device' docs here for Debian/Ubuntu and
Fedora/RHEL configs:

  http://wiki.libvirt.org/page/Networking

> and 2) setup a virtual ethernet-network, which is completely isolated
> from the host's networking WITHOUT using NAT/dnsmasq.

You can modify libvirt's default virtual network to turn off both
DHCP and NAT forwarding options, which will just leave the bridge
interface in an isolated config

  virsh net-edit default

And remove the DHCP XML elements, and remove the '<forward>'
element


Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

  reply	other threads:[~2009-02-02 10:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-02 10:06 using KVM w/o dnsmasq on CentOS 5.2 X64 Stefan Krümmel
2009-02-02 10:52 ` Daniel P. Berrange [this message]
2009-02-02 11:37 ` Paolo Pedaletti

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=20090202105212.GA31756@redhat.com \
    --to=berrange@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=skruemmel@wheregroup.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