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

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@lists.xensource.com
http://lists.xensource.com/xen-users

I haven''t looked closely at your questions yet, but I did happen
across this nice little Xen/bonding how-to from Dell. Might guide you
further.

jerry

On 3/9/07, Ian Brown <ianbrn@gmail.com> wrote:
> 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@lists.xensource.com
> http://lists.xensource.com/xen-users
>

-- 
"Oh joy! Rapture! I''ve got a brain"
-Scarecrow

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

Oops.
http://www.dell.com/downloads/global/power/ps1q07-20070100-Gautreau-OE.pdf

On 3/9/07, Jerry Amundson <jamundso@gmail.com>
wrote:
> I haven''t looked closely at your questions yet, but I did happen
> across this nice little Xen/bonding how-to from Dell. Might guide you
> further.
>
> jerry
>
> On 3/9/07, Ian Brown <ianbrn@gmail.com> wrote:
> > 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@lists.xensource.com
> > http://lists.xensource.com/xen-users
> >
>
>
> --
> "Oh joy! Rapture! I''ve got a brain"
> -Scarecrow
>

-- 
"Oh joy! Rapture! I''ve got a brain"
-Scarecrow

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

Thanks, Jerry.

  - I am looking at this 3 pages Dell pdf doc and will try something like it.

  - A question:
  It is said there that :
"The bridge and the bond should be configured to disable Address
Resolution Protocol (ARP) and multicast. In the test environment,"
and this should be done by:

# ip link set xenbr1 arp off
# ip link set xenbr1 multicast off

Does anybody knows why this is so ?

Regards,
Ian


On 3/9/07, Jerry Amundson <jamundso@gmail.com>
wrote:
> Oops.
> http://www.dell.com/downloads/global/power/ps1q07-20070100-Gautreau-OE.pdf
>
> On 3/9/07, Jerry Amundson <jamundso@gmail.com> wrote:
> > I haven''t looked closely at your questions yet, but I did
happen
> > across this nice little Xen/bonding how-to from Dell. Might guide you
> > further.
> >
> > jerry
> >
> > On 3/9/07, Ian Brown <ianbrn@gmail.com> wrote:
> > > 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@lists.xensource.com
> > > http://lists.xensource.com/xen-users
> > >
> >
> >
> > --
> > "Oh joy! Rapture! I''ve got a brain"
> > -Scarecrow
> >
>
>
> --
> "Oh joy! Rapture! I''ve got a brain"
> -Scarecrow
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/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.
The default config bridges eth0, so you''ll need to tweak things a bit
to get
both eth0 and eth1 working as a bonding device on that bridge...
> 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).
That''s fine - domUs just see a virtual ethernet device. 
There''s probably not
much point in exposing the two real ethernet devices to guests.  If you 
configure bonding in dom0 you should be able to hide this detail completely 
from the guests - they''ll just see their virtual network going faster.
> 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.
If you edit the config you could pass it through, but I think it would be 
better to try and do it in dom0 so that the guests don''t need to be
configured
individually.
>
> 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?
Unless you explicitly specified two virtual network interfaces in the
domain''s
config, you won''t get two appearing there.  This is probably fine for
you;

I''d be inclined to try bonding eth0 and eth1 in the normal way in dom0
then
arranging for the bonding device to be added to the bridge instead of either 
eth0 or eth1...  I''m not sure if there would be any nasty interactions
with
the bridging and bonding code here.  If you have any problems, you could also 
try using a routed rather than bridged setup.

Solutions to this will probably involve some fiddling with the dom0 config 
and / or the networking setup scripts used to configure vifs.

Hope this clears up some things for you!

Cheers,
Mark


-- 
Dave: Just a question. What use is a unicyle with no seat?  And no pedals!
Mark: To answer a question with a question: What use is a skateboard?
Dave: Skateboards have wheels.
Mark: My wheel has a wheel!

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

Why not have a short look to Novells article?

 http://www.novell.com/coolsolutions/feature/17605.html

It works perfectly for me.


Am 10.03.2007 18:59 Uhr schrieb "Mark Williamson" unter
<mark.williamson@cl.cam.ac.uk>:
>> 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.
> 
> The default config bridges eth0, so you''ll need to tweak things a
bit to get
> both eth0 and eth1 working as a bonding device on that bridge...
> 
>> 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).
> 
> That''s fine - domUs just see a virtual ethernet device. 
There''s probably not
> much point in exposing the two real ethernet devices to guests.  If you
> configure bonding in dom0 you should be able to hide this detail completely
> from the guests - they''ll just see their virtual network going
faster.
> 
>> 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.
> 
> If you edit the config you could pass it through, but I think it would be
> better to try and do it in dom0 so that the guests don''t need to
be configured
> individually.
> 
>> 
>> 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?
> 
> Unless you explicitly specified two virtual network interfaces in the
domain''s
> config, you won''t get two appearing there.  This is probably fine
for you;
> 
> I''d be inclined to try bonding eth0 and eth1 in the normal way in
dom0 then
> arranging for the bonding device to be added to the bridge instead of
either
> eth0 or eth1...  I''m not sure if there would be any nasty
interactions with
> the bridging and bonding code here.  If you have any problems, you could
also
> try using a routed rather than bridged setup.
> 
> Solutions to this will probably involve some fiddling with the dom0 config
> and / or the networking setup scripts used to configure vifs.
> 
> Hope this clears up some things for you!
> 
> Cheers,
> Mark
> 

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

On 10 Mar 2007 at 20:11, Julian Pawlowski wrote:
> Why not have a short look to Novells article?
> 
>  http://www.novell.com/coolsolutions/feature/17605.html
> 
> It works perfectly for me.
No unexpected messages in /var/log/messages? Which bonding mode do you use, and
do
you use physical access to the NICs in DumU?

Ulrich

> 
> 
> Am 10.03.2007 18:59 Uhr schrieb "Mark Williamson" unter
> <mark.williamson@cl.cam.ac.uk>:
> 
> >> 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.
> > 
> > The default config bridges eth0, so you''ll need to tweak
things a bit to get
> > both eth0 and eth1 working as a bonding device on that bridge...
> > 
> >> 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).
> > 
> > That''s fine - domUs just see a virtual ethernet device. 
There''s probably not
> > much point in exposing the two real ethernet devices to guests.  If
you
> > configure bonding in dom0 you should be able to hide this detail
completely
> > from the guests - they''ll just see their virtual network
going faster.
> > 
> >> 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.
> > 
> > If you edit the config you could pass it through, but I think it would
be
> > better to try and do it in dom0 so that the guests don''t need
to be configured
> > individually.
> > 
> >> 
> >> 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?
> > 
> > Unless you explicitly specified two virtual network interfaces in the
domain''s
> > config, you won''t get two appearing there.  This is probably
fine for you;
> > 
> > I''d be inclined to try bonding eth0 and eth1 in the normal
way in dom0 then
> > arranging for the bonding device to be added to the bridge instead of
either
> > eth0 or eth1...  I''m not sure if there would be any nasty
interactions with
> > the bridging and bonding code here.  If you have any problems, you
could also
> > try using a routed rather than bridged setup.
> > 
> > Solutions to this will probably involve some fiddling with the dom0
config
> > and / or the networking setup scripts used to configure vifs.
> > 
> > Hope this clears up some things for you!
> > 
> > Cheers,
> > Mark
> > 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users


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

Am 12.03.2007 8:18 Uhr schrieb "Ulrich Windl" unter
<ulrich.windl@rz.uni-regensburg.de>:
> 
> No unexpected messages in /var/log/messages?
Nothing :-)
> Which bonding mode do you use,
mode 0 but I think mode 1 should also be possible without any problem.
> and do you use physical access to the NICs in DumU?
No physical access from domU, the vif is connected to the xenbr0 interface
which itself is connected to bond0.


Julian


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

El sáb, 10-03-2007 a las 12:51 +0200, Ian Brown
escribió:
> Thanks, Jerry.
> 
>   - I am looking at this 3 pages Dell pdf doc and will try something like
it.
> 
>   - A question:
>   It is said there that :
> "The bridge and the bond should be configured to disable Address
> Resolution Protocol (ARP) and multicast. In the test environment,"
> and this should be done by:
> 
> # ip link set xenbr1 arp off
> # ip link set xenbr1 multicast off
> 
> Does anybody knows why this is so ?
> 
	I don'' know. What I know is that if I configure this, I can''t
reach the
xen dom0 (but I can reach domU''s).

	The problem I am having with this configuration is that it works while
I am pinging to domUs (I guess it still works with other kind of
traffic), but as soon as I stop pinging it, the bridge stop working.

	Any idea?

-- 
Angel L. Mateo Martínez
Sección de Telemática
Área de Tecnologías de la Información       _o)
y las Comunicaciones Aplicadas (ATICA)      / \\
http://www.um.es/atica                    _(___V
Tfo: 968367590
Fax: 968398337


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