WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: "Mr. Teo En Ming (Zhang Enming)" <space.time.universe@xxxxxxxxx>
Subject: Re: [Xen-users] Re: Will pv-ops dom0-patched kernel be eventually merged into Linus Torvalds' mainline Linux kernel tree?
From: Freddie Cash <fjwcash@xxxxxxxxx>
Date: Tue, 10 Nov 2009 07:36:37 -0800
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 10 Nov 2009 07:39:44 -0800
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:cc:content-type; bh=dSKiE52ODRjgTj0Nf7oKyRxeA7Af+zZjlRyGeGWpqwk=; b=wPujv66/D5Dzr9w6LXVinMCJmWYEUE3B4P7o5jjwnUz7C9nDmEIAm6UfIW016tMwCD DHgCAQ/WSy27EvNQcxdZcnVVYFYbgNM72sPDrOk3MBJfEWDUWtDZdfqEcY/q5TQYhCns 00VCTwzcDZxwLwsSjICih/LZQjmJoRe1dR7g0=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; b=dw6XMej4WruvpjgZvTRldy+MzErgzMMSYu+BndjgtHyBMhOsk79SP/nd/beOv9ydqL jQ7f3whXSwFwCL5CEB2NpKxZjxgOlJa0yrceM6LtYWBGEyL2NtloKwGX2z9r7GXelqca pOzkkhpPi/vKldJtqCFgArpoAAK7tyiKz4LeE=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <f712b9cf0911092227x5dbcf76y443411497d4fc6c@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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
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.)

-- 
Freddie Cash
fjwcash@xxxxxxxxx

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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