Re: [Xen-devel] After switching from "xm" to "xl" toolstack, can't get Guest networking to work.

[Roger Pau Monnà <roger.pau@xxxxxxxxxxxxx>]

2012/1/21  <erin.balid@xxxxxxxxxxxx>:
> Hi All.
>
> I posted this over on the OpenSUSE Virtual mailing list, since I use
> that distro. ÂBut I found on the Xen wiki site,
>
> Âhttp://wiki.xen.org/wiki/MigrationGuideToXen4.1%2B#Toolstack_upgrade_notes
>
> so I guess we should post xm->xl migration configuration problems here
> too, or instead.
>
>
> I inherited an OpenSUSE Version 11.4 Xen host machine here at work.
>
> Without too much trouble I finished upgrading it to Version 12.1.
>
> The old setup was running using the Xen "xm" toolstack and works like
> you'd expect. ÂThe new setup works ok if I use the "xm" stack as well.
>
> I learned that we should move to the "xl" toolstack. ÂI'm trying to do
> that now and having some problems with networking, but only with the xl
> approach.
>
> I've been running up to date Xen for awhile.
>
> rpm -qa | grep -i xen
> Âxen-tools-4.1.2_11-164.5.x86_64
> Âxen-doc-html-4.1.2_11-164.5.x86_64
> Âxen-libs-4.1.2_11-164.5.x86_64
> Âxen-4.1.2_11-164.5.x86_64
> Âpatterns-openSUSE-xen_server-12.1-25.21.1.x86_64
> Âxen-devel-4.1.2_11-164.5.x86_64
> Âxen-doc-pdf-4.1.2_11-164.5.x86_64
> Âkernel-xen-devel-3.1.0-1.2.1.x86_64
> Âkernel-xen-3.1.0-1.2.1.x86_64
>
> I already setup the networking on the Host to use OpenSUSE
> configuration.
>
> brctl show
> Âbridge name   bridge id        STP enabled   interfaces
> Âbr0       8000.0052351d5337    no       Âeth0
>
> cat /etc/sysconfig/network/ifcfg-br0
> ÂSTARTMODE='auto'
> ÂBOOTPROTO='static'
> ÂBRIDGE='yes'
> ÂBRIDGE_PORTS='eth0'
> ÂBRIDGE_FORWARDDELAY='0'
> ÂBRIDGE_STP='off'
>
> ÂNAME='Motherboard'
> ÂIPADDR='192.168.1.32/24'
> ÂBROADCAST=''
> ÂREMOTE_IPADDR=''
> ÂNETWORK=''
> ÂMTU=''
> ÂETHTOOL_OPTIONS=''
> ÂUSERCONTROL='no'
> ÂNM_CONTROLLED='no'
>
> cat /etc/sysconfig/network/ifcfg-eth0
> ÂSTARTMODE='manual'
> ÂBOOTPROTO='none'
> ÂBRIDGE='no'
>
> The Guest cfg file I'm using for testing is:
>
> cat test.cfg
> Âname='test'
> Âbuilder='linux'
> Âbootloader='/usr/bin/pygrub'
> Âdisk=['phy:/dev/XenVols/test,xvda,w']
> Âvif=[mac=00:16:3e:12:34:01, bridge=br0 Â, vifname=vifBR']

The xl toolstack present in version 4.1.2 doesn't support vifname[0]
(newer versions do), so I think if you remove that it should be ok.

[0] http://lists.xen.org/archives/html/xen-users/2011-12/msg00225.html

> Âvfb=[ 'type=vnc, vncdisplay=1, vnclisten=127.0.0.1']
> Âextra='textmode=1 xencons=xvc0 noirqdebug'
> Âon_shutdown='destroy'
> Âon_reboot='restart'
> Âon_crash='destroy'
> Âvcpus=2
> Âmaxmem=2048
> Âmemory=2048
>
> With a clean-booted Host and no launched Guests,
>
> xl list
> ÂName                    ÂID  Mem VCPUs   ÂState
> ÂTime(s)
> ÂDomain-0 Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â Â 0 Â1010 Â Â 4 Â Â r-----
> Â Â86.3
>
> xl create -c test.cfg
> Â Â Â Â Â ÂpyGRUB Âversion 0.6
> Â Â Â Â 
> ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
> Â Â Â Â â Xen4 12.1 DomU
> Â Â Â Â Â Â Â Â Ââ
> Â Â Â Â â
> Â Â Â Â Â Â Â Â Ââ
> Â Â Â Â â
> Â Â Â Â Â Â Â Â Ââ
> Â Â Â Â â
> Â Â Â Â Â Â Â Â Ââ
> Â Â Â Â â
> Â Â Â Â Â Â Â Â Ââ
> Â Â Â Â â
> Â Â Â Â Â Â Â Â Ââ
> Â Â Â Â â
> Â Â Â Â Â Â Â Â Ââ
> Â Â Â Â â
> Â Â Â Â Â Â Â Â Ââ
> Â Â Â Â 
> ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
> Â Â Â Â Â Â Use the ^ and v keys to select which entry is highlighted.
> Â Â Â Â Â Â Press enter to boot the selected OS, 'e' to edit the
> Â Â Â Â Â Â commands before booting, 'a' to modify the kernel arguments
> Â Â Â Â Â Â before booting, or 'c' for a command line.
>
> Â Â Â Â Â Â Will boot selected entry in Â1 seconds
>
>
> Â Â Â ÂDaemon running with PID 6779
>
> I get no other output here (why not?) on the console for about 30
> seconds. Then just,
>
> ÂWelcome to openSUSE 12.1 "Asparagus" - Kernel 3.1.0-1.2-xen (xvc0).
>
> Âtestserver login:
>
>
> The output of 'tail -f /var/log/messages /var/log/xen/*log' is just
>
> Â Â Â Â==> /var/log/messages <==
> Â Â Â ÂJan 21 10:40:39 testserver logger: /etc/xen/scripts/block: add
> Â Â Â ÂXENBUS_PATH=backend/vbd/5/51712
> Â Â Â ÂJan 21 10:40:39 testserver logger: /etc/xen/scripts/block: add
> Â Â Â ÂXENBUS_PATH=backend/vbd/5/51728
> Â Â Â ÂJan 21 10:40:39 testserver logger: /etc/xen/scripts/block: add
> Â Â Â ÂXENBUS_PATH=backend/vbd/5/51744
> Â Â Â ÂJan 21 10:40:40 testserver logger: /etc/xen/scripts/vif-bridge:
> Â Â Â Âonline type_if=vif XENBUS_PATH=backend/vif/5/0
> Â Â Â ÂJan 21 10:40:40 testserver logger: /etc/xen/scripts/vif-bridge:
> Â Â Â ÂNo device details in backend/vif/5/0, exiting.
> Â Â Â ÂJan 21 10:40:40 testserver logger: /etc/xen/scripts/vif-bridge:
> Â Â Â Âonline XENBUS_PATH=backend/vif/5/0
> Â Â Â ÂJan 21 10:40:40 testserver logger: /etc/xen/scripts/vif-bridge:
> Â Â Â ÂNo device details in backend/vif/5/0, exiting.
> Â Â Â ÂJan 21 10:40:40 testserver kernel: [ 2711.951822] blkback:
> Â Â Â Âring-ref 8, event-channel 12, protocol 1 (x86_64-abi)
> Â Â Â ÂJan 21 10:40:40 testserver kernel: [ 2712.015731] blkback:
> Â Â Â Âring-ref 9, event-channel 13, protocol 1 (x86_64-abi)
> Â Â Â ÂJan 21 10:40:40 testserver kernel: [ 2712.066467] blkback:
> Â Â Â Âring-ref 10, event-channel 14, protocol 1 (x86_64-abi)
>
>
> I can login to the guest at the console and the Guest's networking looks
> like it's recognized OK.
>
> dmesg | grep eth
> [ Â Â0.896597] netfront: Initialising virtual ethernet driver.
>
> hwinfo --network
> 05: None 00.0: 10700 Loopback
> Â[Created at net.124]
> ÂUnique ID: ZsBS.GQNx7L4uPNA
> ÂSysFS ID: /class/net/lo
> ÂHardware Class: network interface
> ÂModel: "Loopback network interface"
> ÂDevice File: lo
> ÂLink detected: yes
> ÂConfig Status: cfg=new, avail=yes, need=no, active=unknown
>
> 06: None 00.0: 10701 Ethernet
> Â[Created at net.124]
> ÂUnique ID: usDW.ndpeucax6V1
> ÂParent ID: +jsg.Sd+ykfyvlK4
> ÂSysFS ID: /class/net/eth0
> ÂSysFS Device Link: /devices/xen/vif-0
> ÂHardware Class: network interface
> ÂModel: "Ethernet network interface"
> ÂDriver: "vif"
> ÂDriver Modules: "xennet"
> ÂDevice File: eth0
> ÂHW Address: 00:16:3e:12:34:01
> ÂLink detected: yes
> ÂConfig Status: cfg=new, avail=yes, need=no, active=unknown
> ÂAttached to: #4 (Ethernet controller)
>
> The Guest's network routes look OK.
>
> route
> Kernel IP routing table
> Destination   Gateway     Genmask     Flags Metric Ref  ÂUse
> Iface
> default     192.168.1.1   0.0.0.0     UG  Â0   Â0    Â0
> eth0
> loopback    Â*        255.0.0.0    U   0   Â0    Â0
> lo
> link-local   Â*        255.255.0.0   U   0   Â0    Â0
> eth0
> 192.168.1.0 Â Â * Â Â Â Â Â Â Â 255.255.255.0 Â U Â Â 0 Â Â Â0 Â Â Â Â0
> eth0
>
> But when I try to ping anywhere off the Guest I get HostUnreachable
> errors.
>
> ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> From 192.168.1.32 icmp_seq=1 Destination Host Unreachable
> From 192.168.1.32 icmp_seq=2 Destination Host Unreachable
> From 192.168.1.32 icmp_seq=3 Destination Host Unreachable
> etc etc
>
> It feels like I'm pretty close to getting this working. ÂAm I still
> missing some part of the configuration changes needed for using the xl
> toolstack?
>
> Regards,
>
> Erin
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel