[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] Re: [Xen-users] VM bridge doesn't pass traffic
Am 18.01.2016 um 12:12 schrieb Ian Campbell: >> 5: vif1.0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq master >> xenbr0 state DOWN group default qlen 32 >> link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff > This one seems odd though. Compared with a random vif I have on a test box: > > 6: vif2.0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq master xenbr0 > state UP group default qlen 32 > link/ether fe:ff:ff:ff:ff:ff brd ff:ff:ff:ff:ff:ff > inet6 fe80::fcff:ffff:feff:ffff/64 scope link > valid_lft forever preferred_lft forever > > Specifically "NO-CARRIER" and "xenbr0 state DOWN" differ between my working > setup and yours. Yep, that's what's confusing me too. >> [11:26:01] root@XXXXX-web-node02:~# cat /etc/network/interfaces >> # This file describes the network interfaces available on your system >> # and how to activate them. For more information, see interfaces(5). >> >> source /etc/network/interfaces.d/* >> >> # The loopback network interface >> auto lo >> iface lo inet loopback >> >> # The primary network interface >> auto xenbr0 >> allow-hotplug xenbr0 > I think this probably doesn't matter, but I typically use only auto _or_ > allow-hotplug, not both. Specifically I usually use just "auto" for any > fixed interfaces. It actually shouldn't interfere, afaik. But I disabled the allow-hotplug for testing. Didn't make any difference yet, though. >> iface xenbr0 inet static >> address 10.41.16.236 >> netmask 255.255.255.0 >> gateway 10.41.16.1 >> bridge_ports eth0 > FWIW I also use: > bridge_fd 0 > bridge_stp off > > Not clear if that makes a difference in the way you are seeing though. I > don't think it should. Added both - no difference. > I should have asked for these last time, sorry, but could you also post > your guest cfg file and the output of "xenstore-ls -fp". You can view the config file here: http://pastebin.com/M3ZFT47Q It's pretty basic with only little changes after automatic creation by Xen. The output of "xenstore-ls -fp": http://pastebin.com/VdtEbyNB > Are you creating a PV or HVM guest? If I'm getting it right from this source [http://serverfault.com/a/511938] and the following output, it is a "PV-HVM" guest: root@www:~# uname -a Linux www 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u2 (2016-01-02) x86_64 GNU/Linux root@www:~# lsmod | grep xen xen_netfront 26038 0 xen_blkfront 25614 1 > Could you also post any relevant logs from under /var/log/xen, mostly the > ones with the domain's name in the filename, but also anything to do with > hotplug if you have any files like that. The logs are pretty empty: [12:59:59] root@XXXXX-web-node02:~# ls -Ahl /var/log/xen/ total 44K -rw-r----- 1 root adm 0 Dec 22 16:51 xen-hotplug.log -rw-r--r-- 1 root adm 800 Jan 18 12:38 xl-www.xxxxx.de.log -rw-r--r-- 1 root adm 222 Jan 18 12:33 xl-www.xxxxx.de.log.1 -rw-r--r-- 1 root adm 222 Jan 15 11:39 xl-www.xxxxx.de.log.10 -rw-r--r-- 1 root adm 225 Jan 15 13:43 xl-www.xxxxx.de.log.2 -rw-r--r-- 1 root adm 226 Jan 15 13:39 xl-www.xxxxx.de.log.3 -rw-r--r-- 1 root adm 226 Jan 15 13:26 xl-www.xxxxx.de.log.4 -rw-r--r-- 1 root adm 226 Jan 15 13:13 xl-www.xxxxx.de.log.5 -rw-r--r-- 1 root adm 226 Jan 15 12:06 xl-www.xxxxx.de.log.6 -rw-r--r-- 1 root adm 225 Jan 15 11:59 xl-www.xxxxx.de.log.7 -rw-r--r-- 1 root adm 226 Jan 15 11:57 xl-www.xxxxx.de.log.8 -rw-r--r-- 1 root adm 226 Jan 15 11:41 xl-www.xxxxx.de.log.9 [13:00:03] root@XXXXX-web-node02:~# cat /var/log/xen/xen-hotplug.log [13:00:05] root@XXXXX-web-node02:~# cat /var/log/xen/xl-www.xxxxx.de.log Waiting for domain www.xxxxx.de (domid 2) to die [pid 5731] libxl: debug: libxl_event.c:570:libxl__ev_xswatch_register: watch w=0x982920 wpath=@releaseDomain token=3/0: register slotnum=3 libxl: debug: libxl_event.c:514:watchfd_callback: watch w=0x982920 wpath=@releaseDomain token=3/0: event epath=@releaseDomain libxl: debug: libxl.c:1005:domain_death_xswatch_callback: [evg=0x982d00:2] from domid=2 nentries=1 rc=1 libxl: debug: libxl.c:1016:domain_death_xswatch_callback: [evg=0x982d00:2] got=domaininfos[0] got->domain=2 libxl: debug: libxl.c:1043:domain_death_xswatch_callback: exists shutdown_reported=0 dominf.flags=ffff0020 libxl: debug: libxl.c:1009:domain_death_xswatch_callback: [evg=0] all reported libxl: debug: libxl.c:1073:domain_death_xswatch_callback: domain death search done > Lastly while I'm fishing for potential clues please could you post the > output of of "xl -vvv create <cfg>", the -vvv makes it much more verbose. Output of the create command: http://pastebin.com/7CqdS2Zd Output of the vm boot process (from xl console): http://pastebin.com/ZduwSmNn Regards, David Compositiv GmbH Hammer Deich 30 20537 Hamburg Tel: 040 / 609 4349 0 Fax: 040 / 609 4349 40 GeschÃftsfÃhrer Matthias Krawen Amtsgericht Hamburg - HRB 122540 USt.-IdNr: DE282432834 Es gelten ausschlieÃlich unsere AGB. _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxx http://lists.xen.org/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |