Xen Project Q&A Forum: First Line Help for Simple Questions

This is your chance to ask questions and provide answers about basic use of the Xen Project software. For debugging problems and for more complex issues, consider using the xen-users mailing list instead. You can find information about xen-users under "HELP | Mailing Lists" in the navigation bar above.

xenbr0 keeps going into disabled state

posted in Hypervisor
Wednesday, August 09 2017, 11:11 AM
llo
llo
Offline
0
I often use pxeboot to install images into Xen virtual servers. This has worked flawlessly for many years. Now all of a sudden when I'm installing images to new Xen VMs, when I get to about 14% progress the VM reboots!

From my interpretation of the error logs, it looks like the xenbr0 bridge goes into disabled state and then comes back online.

I'm using Xen version: 4.1.6.1 (preserve-AD) with libvirt 0.9.8 on Ubuntu 12.04.5 LTS

Here is the log output when the error occurs:

Aug 9 12:33:25 xen kernel: [ 8557.399288] xenbr0: port 7(tap24.0) entering forwarding state
Aug 9 12:33:25 xen kernel: [ 8557.399670] xenbr0: port 7(tap24.0) entering disabled state
Aug 9 12:33:25 xen kernel: [ 8557.404092] device tap24.0 left promiscuous mode
Aug 9 12:33:25 xen kernel: [ 8557.404096] xenbr0: port 7(tap24.0) entering disabled state
Aug 9 12:33:25 xen kernel: [ 8557.557005] xenbr0: port 8(vif24.0) entering disabled state
Aug 9 12:33:25 xen kernel: [ 8557.557185] device vif24.0 left promiscuous mode
Aug 9 12:33:25 xen kernel: [ 8557.557188] xenbr0: port 8(vif24.0) entering disabled state
Aug 9 12:33:25 xen logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/console/24/0
Aug 9 12:33:26 xen logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vfb/24/0
Aug 9 12:33:26 xen logger: /etc/xen/scripts/vif-bridge: offline type_if=vif XENBUS_PATH=backend/vif/24/0
Aug 9 12:33:26 xen logger: /etc/xen/scripts/block: remove XENBUS_PATH=backend/vbd/24/768
Aug 9 12:33:26 xen kernel: [ 8558.205171] device tap25.0 entered promiscuous mode
Aug 9 12:33:26 xen kernel: [ 8558.205207] xenbr0: port 7(tap25.0) entering forwarding state
Aug 9 12:33:26 xen kernel: [ 8558.205220] xenbr0: port 7(tap25.0) entering forwarding state
Aug 9 12:33:26 xen logger: /etc/xen/scripts/block: add XENBUS_PATH=backend/vbd/25/768
Aug 9 12:33:26 xen logger: /etc/xen/scripts/vif-bridge: brctl delif xenbr0 vif24.0 failed
Aug 9 12:33:26 xen logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vbd/24/768
Aug 9 12:33:26 xen logger: /etc/xen/scripts/vif-bridge: ifconfig vif24.0 down failed
Aug 9 12:33:26 xen logger: /etc/xen/scripts/vif-bridge: online type_if=vif XENBUS_PATH=backend/vif/25/0
Aug 9 12:33:26 xen logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge offline for vif24.0, bridge xenbr0.
Aug 9 12:33:26 xen logger: /etc/xen/scripts/vif-bridge: add type_if=tap XENBUS_PATH=
Aug 9 12:33:26 xen logger: /etc/xen/scripts/xen-hotplug-cleanup: XENBUS_PATH=backend/vif/24/0
Aug 9 12:33:26 xen kernel: [ 8558.654924] xenbr0: port 7(tap25.0) entering forwarding state
Aug 9 12:33:26 xen kernel: [ 8558.682733] xenbr0: port 7(tap25.0) entering forwarding state
Aug 9 12:33:26 xen kernel: [ 8558.682741] xenbr0: port 7(tap25.0) entering forwarding state
Aug 9 12:33:26 xen logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge add for tap25.0, bridge xenbr0.
Aug 9 12:33:26 xen kernel: [ 8558.695756] device vif25.0 entered promiscuous mode
Aug 9 12:33:26 xen kernel: [ 8558.726438] ADDRCONF(NETDEV_UP): vif25.0: link is not ready
Aug 9 12:33:26 xen logger: /etc/xen/scripts/block: Writing backend/vbd/25/768/node /dev/loop8 to xenstore.
Aug 9 12:33:26 xen logger: /etc/xen/scripts/vif-bridge: Successful vif-bridge online for vif25.0, bridge xenbr0.
Aug 9 12:33:27 xen logger: /etc/xen/scripts/block: Writing backend/vbd/25/768/physical-device 7:8 to xenstore.
Aug 9 12:33:27 xen logger: /etc/xen/scripts/vif-bridge: Writing backend/vif/25/0/hotplug-status connected to xenstore.
Aug 9 12:33:27 xen logger: /etc/xen/scripts/block: Writing backend/vbd/25/768/hotplug-status connected to xenstore.
Aug 9 12:33:28 xen ntpd[2695]: bind(41) AF_INET6 fe80::fcff:ffff:feff:ffff%83#123 flags 0x11 failed: Cannot assign requested address
Aug 9 12:33:28 xen ntpd[2695]: unable to create socket on tap25.0 (50) for fe80::fcff:ffff:feff:ffff#123
Aug 9 12:33:28 xen ntpd[2695]: failed to init interface for address fe80::fcff:ffff:feff:ffff
Aug 9 12:33:28 xen ntpd[2695]: Deleting interface #49 tap24.0, fe80::fcff:ffff:feff:ffff#123, interface stats: received=0, sent=0, dropped=0, active_time=222 secs
Aug 9 12:33:28 xen ntpd[2695]: peers refreshed
Aug 9 12:33:30 xen ntpd[2695]: Listen normally on 51 tap25.0 fe80::fcff:ffff:feff:ffff UDP 123
Aug 9 12:33:30 xen ntpd[2695]: peers refreshed
Aug 9 12:33:30 xen ntpd[2695]: new interface(s) found: waking up resolver



From

llo
Responses (0)
  • There are no replies here yet.
Your Reply