[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Xen Netloop module missing

  • To: "Fajar A. Nugraha" <list@xxxxxxxxx>
  • From: Virajith Jalaparti <virajith.j@xxxxxxxxx>
  • Date: Wed, 05 Jan 2011 21:48:54 -0600
  • Cc: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 05 Jan 2011 19:50:22 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=ApOv4upfblTXXEa3ykvqX9hCyLnnsFOu29Bkfc/OizXEdULf4aHW2SuiUuNHj5fdrM jQFhQqjzcDmndPRofT9PueLZUrEk7Dd7UuZz4Zylzva2byJ+0PUlURsYkqeHdQd7ZMbo 9oQFVhFkUduOsWPeeINoNXDCsQ/ACSZGX+oN0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

It means if you need xen netloop support, you need to have it compiled
either as module (CONFIG_XEN_NETDEV_LOOPBACK=y) or builtin
(CONFIG_XEN_NETDEV_LOOPBACK=y). If it's neither, then you can't use
Do both the cases (compiled as a module or builtin) have the same configuration? (CONFIG_XEN_NETDEV_LOOPBACK=y)

  You need to recompile the kernel.
Is this as easy as just doing a "make world"? Would that ensure that the kernel is re-compiled? The thing is when I do a "make world" the /boot/config-* file is re-created. How can I be sure that the new kernel is compiled with this flag enabled i.e. with the netloop module builtin?

Also, which Xen version are you using? Are you using the default
network-bridge or create your own bridges?
netloop is primarily needed for older versions of Xen where the
default bridged setup is :
- create virtual network device pairs for each dom0 interface (vif0.x
and vethx) using netloop module
- rename dom0 interfaces (eth0 ->  peth0, veth0 ->  eth0)
- create a bridge (xenbr0) with peth0 and vif0.0 as its members.

Newer bridge setup use "eth0" as bridge name, and doesn't need netloop anymore.

It has nothing to do whatsoever with VM migration.

In short, if in your current setup your domU is able to access outside
network, most likely you don't need netloop support.

I am using Xen-3.1.3 and I was creating my own bridges. In particular, I was using the following set of commands to set up the bridges in the original version of xen I had installed (from yum repos in CentOS).
vconfig add peth2 513
brctl addbr breth2.513
brctl setfd breth2.513 0
ip link set dev breth2.513 arp off multicast off up
brctl addif breth2.513 peth2.513
ip link set dev peth2.513 up
ip link set dev vif0.4 arp off multicast off
brctl addif breth2.513 vif0.4
ip link set dev vif0.4 up
ip link set dev veth4 name eth2.513 mtu 1400
ip link set dev eth2.513 address `cat /sys/class/net/eth2/address`
ifconfig eth2.513 $ip netmask up

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.