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

[Xen-users] Bonding – dom0 or dom1 ? and why is vif1.1 missing in DomU?


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: "Ian Brown" <ianbrn@xxxxxxxxx>
  • Date: Fri, 9 Mar 2007 15:23:28 +0200
  • Delivery-date: Fri, 09 Mar 2007 05:22:38 -0800
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=GNz/egolKr0lyxSuUz1C294W1Wa6HHrZal/0gguUTF+1HcY4RIwg/8T3nnUP59993RWieIUQI3q9GmeHawOX+cZ2Wddl+ODe0Ojxu3U28kheBt4OZrUVDJwj1+aBjP9Dgd5iP0nU0eWmksYmZU1GG1f1gSaq0AjRHYNj8kw1HH0=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hello Xen users,

I have a machine with two different nics (sis900 and dmfe).
I am trying bonding in Xen. (on FC6, intel x386, para virtualization).

In the past  I did successfully configured and used bonding on non-Xen
Linux machines.

I saw some posts in this list and in other sites regarding Xen
bonding, but I am a little bewildered
so I want to verify something:

I am using the default /etc/xen/xend-config.sxp config file, which
means I am using
bridging (ifconfig can show xenbr0).

When booting into domain 0 both nics are recognized (as I can see from dmesg),
also "ifconfig -a" from  dom0 shows eth0 and eth1.


Now when I boot into domain U , "ifconfig -a" shows only eth0.
/etc/modprobe.conf has a line saying "alias eth0 xennet" (but eth1
does not appear in /etc/modprobe.conf).


Now I have two questions:
1)I want to configure bonding through the initscripts
(namely , create /etc/sysconfig/network-scripts/ifcfg-bond0 and add MASTER/SLAVE
entries in /etc/sysconfig/network-scripts/ifcfg-eth0 and
/etc/sysconfig/network-scripts/ifcfg-eth1 ,
etc.) Where should I do it ? In dom 0 ? or in dom U ? I saw somewhere
in xen-user mailing list that it should be done in dom U ; but as I
said, ifconfig -a does not show eth1 in dom U .
Any tips or guidance as to what should I do or pointers to bonding on
Xen that worked for you will be helpful.

2)
After boot of domain U , I ran ifconfig -a ***in domain 0***, and I
saw only ONE vif1.* instance (vif1.0) I expected to see also vif1.1
for the second nic.
The XenNetworking wiki page says : "If you create multiple network
interfaces for a domU, it's ends will be eth0, eth1, etc, whereas the
dom0 end will be vif<id#>.0, vif<id#>.1, etc."
(http://wiki.xensource.com/xenwiki/XenNetworking). Did I misunderstood
something ?
Am I wrong somewhere?

Regards,
Ian

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


 


Rackspace

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