All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
	Ferry Huberts <ferry-NbsvJix5b8QAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH] make kvm service script transfer dhclient settings correctly
Date: Sun, 16 Sep 2007 19:28:47 +0100	[thread overview]
Message-ID: <20070916182847.GA25929@redhat.com> (raw)
In-Reply-To: <46ECFCF8.2020002-atKUWr5tajBWk0Htik3J/w@public.gmane.org>

On Sun, Sep 16, 2007 at 11:52:56AM +0200, Avi Kivity wrote:
> Ferry Huberts wrote:
> > Avi Kivity wrote:
> >> Ferry Huberts wrote:
> >>
> >>
> >> I really recommend against using the kvm initscript... it is fragile 
> >> is broken.  On Fedora, you can use the standard initscripts (well, 
> >> they are fragile and broken too, but they are more complete than the 
> >> kvm initscript):

I entirely agree with your recommendation against using the kvm initscript.
We don't include in the Fedora KVM rpms, and the equivalent script shipped
with Xen has inflicted untold misery & bug report chaos. Using the distro
specific initscripts for setting up bridges is a much more predictable and
reliable approach.

> >>
> >> [avi@blast ~]$ cat /etc/sysconfig/network-scripts/ifcfg-sw0
> >> DEVICE=sw0
> >> BOOTPROTO=dhcp
> >> HWADDR=00:0F:EA:6E:1E:F0
> >> ONBOOT=yes
> >> TYPE=Bridge
> >> DHCP_HOSTNAME=blast
> >>
> >> [avi@blast ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth0
> >> DEVICE=eth0
> >> BRIDGE=sw0
> >> HWADDR=00:0F:EA:6E:1E:F0
> >> ONBOOT=yes
> >> TYPE=Ethernet
> >>
> >>
> >> This setup starts dhcp directly on the bridge, without the need to 
> >> move things around.  See especially the 'TYPE=Bridge' and 
> >> 'BRIDGE=sw0' statements.

This is similar to the way we document bridge setup in Fedora, although
for the sake of consistent nomenculture with Xen, we have peth0 being the 
physical device & eth0 being the bridge device. Either way its just naming,
the end result is functionally the same.

Libvirt also provides a 'virtual network' which is an isolated bridge
device, connected to the physical devices using NAT as our 'out of the box'
connectivity.

There's a short blog post with recommendations for KVM networking on Fedora

http://watzmann.net/blog/index.php/2007/04/27/networking_with_kvm_and_libvirt

> I'll remove the script unless anyone sees an objection?

Gets my vote.

Regards,
Dan.
-- 
|=- Red Hat, Engineering, Emerging Technologies, Boston.  +1 978 392 2496 -=|
|=-           Perl modules: http://search.cpan.org/~danberr/              -=|
|=-               Projects: http://freshmeat.net/~danielpb/               -=|
|=-  GnuPG: 7D3B9505   F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505  -=| 

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-09-16 18:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-15 17:09 [PATCH] make kvm service script transfer dhclient settings correctly Ferry Huberts
     [not found] ` <46EC11AE.9090408-NbsvJix5b8QAvxtiuMwx3w@public.gmane.org>
2007-09-16  9:18   ` Avi Kivity
     [not found]     ` <46ECF4E2.9000203-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-16  9:39       ` Ferry Huberts
     [not found]         ` <46ECF9DB.5020208-NbsvJix5b8QAvxtiuMwx3w@public.gmane.org>
2007-09-16  9:52           ` Avi Kivity
     [not found]             ` <46ECFCF8.2020002-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-16 18:28               ` Daniel P. Berrange [this message]
2007-09-16  9:55           ` Dor Laor

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=20070916182847.GA25929@redhat.com \
    --to=berrange-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
    --cc=ferry-NbsvJix5b8QAvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.