This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-users] Re: Will pv-ops dom0-patched kernel be eventually merged

To: Freddie Cash <fjwcash@xxxxxxxxx>
Subject: Re: [Xen-users] Re: Will pv-ops dom0-patched kernel be eventually merged into Linus Torvalds' mainline Linux kernel tree?
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Tue, 10 Nov 2009 19:58:17 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, "Mr. Teo En Ming \(Zhang Enming\)" <space.time.universe@xxxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 10 Nov 2009 09:59:40 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <b269bc570911100736l713a372cjeda4009c174c08b8@xxxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <f712b9cf0911092129s3f9b7b97j44984d78cb0a20c3@xxxxxxxxxxxxxx> <f712b9cf0911092227x5dbcf76y443411497d4fc6c@xxxxxxxxxxxxxx> <b269bc570911100736l713a372cjeda4009c174c08b8@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)
On Tue, Nov 10, 2009 at 07:36:37AM -0800, Freddie Cash wrote:
> On Mon, Nov 9, 2009 at 10:27 PM, Mr. Teo En Ming (Zhang Enming)
> <space.time.universe@xxxxxxxxx> wrote:
> > One of the reasons why I prefer Xen over KVM is because of networking.
> >
> > I have a Gigabit network card on my Intel DQ45CB motherboard. I don't see a
> > need to install an additional network card on my motherboard as PCI and PCIe
> > expansion slots are limited.
> >
> > In the case of Xen, the physical network interface in my host operating
> > system (dom0) and the virtual network interfaces in my guest operating
> > systems (domU) can be added to the same ethernet bridge on the host OS. This
> > implies that my host and virtual machines will have IP addresses in the same
> > subnet. Moreover, if I do not want to configure static IP addresses, my
> > virtual machines (VMs) can obtain IP adddresses from the DHCP server on
> > commercial routers like Linksys, D-Link, Netgear, etc, similar to the way
> > the physical network card on the host obtaining its IP address from the same
> > router.
> >
> > But, for the case of KVM, I need to setup an internal network for my guests.
> Bzzzt!  Incorrect.  KVM supports the exact same networking methods as
> Xen.  In fact, it's a lot simpler to setup bridged networking in KVM
> then in Xen, as KVM uses the default network configuration scripts of
> the host OS.
> In Debian, it's as simple as editing /etc/network/interfaces, creating
> the bridge configuration in there, and then pointing /etc/kvm/kvm-ifup
> to use that bridge.
> Xen 3.0 used to be this simple, and the bridge device was separate
> from the physical interface.  Then in Xen 3.2 everything changed, and
> it became a royal pain to configure as the physical interface was
> renamed, and the first interface with an IP was used as the bridge
> device, completely breaking setups where you have a management
> interface with an IP, and separate interfaces for the bridge(s).
> (Yes, I know it's possible to work around this, but it broke existing
> setups, and changed things for no good reason.)

With Xen, you can, and have always been able to, use your distro
provided network configuration scripts/methods.

Just disable the default Xen network-bridge script, and do it yourself.
No need to have Xen scripts do the renaming etc.

-- Pasi

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>