[Xen-devel] Re: Experience with netchannel2

[Sergey Tovpeko <tsv.devel@xxxxxxxxx>]

Hello, Steven.
> > 1. During xen-netchannel2 building, vif2 script
> > tools/hotplug/Linux/vif2 isn't installed to /etc/xen/scripts.
> > Is this script needed at all?
> >     
> It is needed, and it should be installed in /etc/xen/scripts.  The
> normal tools makefiles are supposed to do this automatically when you
> run ``make install'' (and they do on my test box).  Could you post
> the output of ``cd tools/hotplug; make install'', please?
>   
I've attached the log in 'hotplug_makefile' file.
It seems that tools/hotplug/Makefile doesn't know that it should place
'vif2' to /etc/xen/scripts.


> > What variable should be placed in domU config : 'vif' or 'vif2'?
> >     
> vif2.  e.g.:
>
> vif2 = [ 'bridge=eth1' ]
>   
Hmm, there is no key 'bridge' for vif2 in tools/python/xen/xm/create.py
And domU doesn't start with
Error: Invalid vif option: bridge

    for c in vifs2:
        d = comma_sep_kv_to_dict(c)
        config_vif = ['vif2']

        for k in d.keys():
            if k not in ['front_mac', 'back_mac', 'backend', 'pdev',
                         'max_bypasses']:
                err('Invalid vif option: ' + k)
            config_vif.append([k, d[k]])
        config_devs.append(['device', config_vif])


Moreover, the domU is starting without 'bridge' key with
vif2 =[ '' ]
but what i have, are
1. Virtual network interface is created in dom0 with name 'eth1', while
in old netchannel1,  virtual network intarface
has the name 'vifN.M'. It's very strange that i have 'eth1' instead of
'vifN.M'.
2. Despite the fact that DomU have started, there no connection in domU.
I suppose it's due to the virtual interface have not been attached to
the bridge in Dom0.
I noticed that there are differencies between /etc/xen/scripts/vif and
/etc/xen/scritps/vif2. The old vif uses 'brctl show' command to find the
bridge, but vif2 script doesn't.


> > 2. I have managed to start domU with netchannel2 succesfully with single 
> > virtual ethernet card.
> >  But when I added second vif device to the domU configuration, i got black 
> > screen in dom0, during
> > domU starting. It happens on the on network initialisation stage, so i could 
> > consider netchannel2
> > affects this somehow. I didn't dig it yet, but it's critical to me to have more 
> > then one NIC.
> >     
> What do you mean by ``black screen''?  That dom0 crashes?  Is there
> any chance you could get a serial console on it, please?
>   
I mean my dom0 is rebooting, tripple fault have been occured.
I'm going to research this problem. Here my test case
1. Start domU with two netchannel1 NIC
vif = [ '', '' ]
2. In DomU obtain IP-address manually for  first NIC, then for second one.
dhclient eth0
dhclient eth1

Before second dhclient finished, dom0 goes to reboot.


Best regards,
   Sergey Tovpeko.

make[1]: Entering directory 
`/home/niagara/hghome/netchannel2-xen-unstable.hg/tools/hotplug'
make -C common install
make[2]: Entering directory 
`/home/niagara/hghome/netchannel2-xen-unstable.hg/tools/hotplug/common'
[ -d //etc/xen/scripts ] || \
                ../../..//tools/cross-install -d -m0755 -p //etc/xen/scripts
set -e; for i in ; \
           do \
           ../../..//tools/cross-install -m0755 -p $i //etc/xen/scripts; \
        done
set -e; for i in ; \
           do \
           ../../..//tools/cross-install -m0644 -p $i //etc/xen/scripts; \
        done
make[2]: Leaving directory 
`/home/niagara/hghome/netchannel2-xen-unstable.hg/tools/hotplug/common'
make[1]: Leaving directory 
`/home/niagara/hghome/netchannel2-xen-unstable.hg/tools/hotplug'
make[1]: Entering directory 
`/home/niagara/hghome/netchannel2-xen-unstable.hg/tools/hotplug'
make -C Linux install
make[2]: Entering directory 
`/home/niagara/hghome/netchannel2-xen-unstable.hg/tools/hotplug/Linux'
[ -d //etc/init.d ] || ../../..//tools/cross-install -d -m0755 -p //etc/init.d
[ -d //etc/sysconfig ] || ../../..//tools/cross-install -d -m0755 -p 
//etc/sysconfig
../../..//tools/cross-install -m0755 -p init.d/xend //etc/init.d
../../..//tools/cross-install -m0755 -p init.d/xendomains //etc/init.d
../../..//tools/cross-install -m0755 -p init.d/sysconfig.xendomains 
//etc/sysconfig/xendomains
[ -d //etc/xen/scripts ] || \
                ../../..//tools/cross-install -d -m0755 -p //etc/xen/scripts
set -e; for i in network-bridge vif-bridge network-route vif-route network-nat 
vif-nat block block-enbd block-nbd vtpm vtpm-delete xen-hotplug-cleanup 
external-device-migrate vscsi; \
            do \
            ../../..//tools/cross-install -m0755 -p $i //etc/xen/scripts; \
        done
set -e; for i in xen-script-common.sh locking.sh logging.sh 
xen-hotplug-common.sh xen-network-common.sh vif-common.sh block-common.sh 
vtpm-common.sh vtpm-hotplug-common.sh vtpm-migration.sh vtpm-impl; \
            do \
            ../../..//tools/cross-install -m0644 -p $i //etc/xen/scripts; \
        done
[ -d //etc/udev ] || \
                ../../..//tools/cross-install -d -m0755 -p //etc/udev/rules.d
set -e; for i in xen-backend.rules xend.rules; \
            do \
            ../../..//tools/cross-install -m0644 -p $i //etc/udev; \
            ln -sf ../$i //etc/udev/rules.d; \
        done
make[2]: Leaving directory 
`/home/niagara/hghome/netchannel2-xen-unstable.hg/tools/hotplug/Linux'
make[1]: Leaving directory 
`/home/niagara/hghome/netchannel2-xen-unstable.hg/tools/hotplug'

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