Hi,
I have been running a xen server with the same config for a year.
It has two bridges, one for all nodes and another one for a lan between some
nodes. It just worked well.
I rebooted the server for updating kernel max loop devs to 256 because I
cannot create more instances due to the limit.
Now, the script only setup one network bridge and does not setu second. It
is supposed to be a mishandling with bridges since I configure xen with
vif-route and it works fine. At some point, xen tries to add the interface
to the bridge and it breaks the iface (see HWAddr). I compared all scripts
with very older backups and checked if apt updated the packages but software
seem to be the same.
Since Xens breaks network interface trying to restore virtual machines, Im
wondering if is there any place where I can remove the start of this
machines. (They were running when I exec reboot)
Please find bellow some info.
Ifconfig )
eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00
inet addr:123.123.123.123 Bcast:123.123.123.247
Mask:255.255.255.248
route)
It just setup loopback and lan interface.
logs)
messages)
Feb 26 10:19:06 poseidon kernel: device vif11.0 entered promiscuous mode
Feb 26 10:19:06 poseidon kernel: audit(1267201146.695:15): dev=vif11.0
prom=256 old_prom=0 auid=4294967295
Feb 26 10:19:06 poseidon kernel: ADDRCONF(NETDEV_UP): vif11.0: link is not
ready
Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled
state
Feb 26 10:20:47 poseidon kernel: device vif11.0 left promiscuous mode
Feb 26 10:20:47 poseidon kernel: audit(1267201247.214:16): dev=vif11.0
prom=0 old_prom=256 auid=4294967295
Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled
state
Feb 26 10:21:06 poseidon kernel: device vif12.0 entered promiscuous mode
Feb 26 10:21:06 poseidon kernel: audit(1267201266.019:17): dev=vif12.0
prom=256 old_prom=0 auid=4294967295
Feb
regards! 26 10:21:06 poseidon kernel: ADDRCONF(NETDEV_UP): vif12.0: link is
not ready
Feb 26 10:22:46 poseidon kernel: xenbr1: port 2(vif12.0) entering disabled
state
Feb 26 10:22:46 poseidon kernel: device vif12.0 left promiscuous mode
Feb 26 10:22:46 poseidon kernel: audit(1267201366.425:18): dev=vif12.0
prom=0 old_prom=256 auid=4294967295
Feb 26 10:22:46 poseidon kernel: xenbr1: port 2(vif12.0) entering disabled
state
syslog)
Feb 26 10:19:06 poseidon kernel: device vif11.0 entered promiscuous mode
Feb 26 10:19:06 poseidon kernel: audit(1267201146.695:15): dev=vif11.0
prom=256 old_prom=0 auid=4294967295
Feb 26 10:19:06 poseidon kernel: ADDRCONF(NETDEV_UP): vif11.0: link is not
ready
Feb 26 10:19:06 poseidon logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge online for vif11.0, bridge xenbr1.
Feb 26 10:19:06 poseidon logger: /etc/xen/scripts/vif-bridge: Writing
backend/vif/11/0/hotplug-status connected to xenstore.
Feb 26 10:19:08 poseidon logger: /etc/xen/scripts/block: Writing
backend/vbd/11/2050/physical-device fe:39 to xenstore.
Feb 26 10:19:08 poseidon logger: /etc/xen/scripts/block: Writing
backend/vbd/11/2050/hotplug-status connected to xenstore.
Feb 26 10:19:09 poseidon logger: /etc/xen/scripts/block: Writing
backend/vbd/11/2049/physical-device fe:38 to xenstore.
Feb 26 10:19:09 poseidon logger: /etc/xen/scripts/block: Writing
backend/vbd/11/2049/hotplug-status connected to xenstore.
Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled
state
Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/vif-bridge: offline
XENBUS_PATH=backend/vif/11/0
Feb 26 10:20:47 poseidon kernel: device vif11.0 left promiscuous mode
Feb 26 10:20:47 poseidon kernel: audit(1267201247.214:16): dev=vif11.0
prom=0 old_prom=256 auid=4294967295
Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled
state
Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/11/2050
Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/block: remove
XENBUS_PATH=backend/vbd/11/2049
Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/11/2050
Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vbd/11/2049
Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/vif-bridge: offline
XENBUS_PATH=backend/vif/11/1
Feb 26 10:20:53 poseidon logger: /etc/xen/scripts/vif-bridge: online
XENBUS_PATH=backend/vif/12/1
Feb 26 10:20:53 poseidon logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/12/2049
Feb 26 10:20:54 poseidon logger: /etc/xen/scripts/block: add
XENBUS_PATH=backend/vbd/12/2050
Feb 26 10:20:54 poseidon logger: /etc/xen/scripts/vif-bridge: online
XENBUS_PATH=backend/vif/12/0
Feb 26 10:21:01 poseidon logger: /etc/xen/scripts/vif-bridge: brctl delif
xenbr1 vif11.0 failed
Feb 26 10:21:04 poseidon logger: /etc/xen/scripts/vif-bridge: ifconfig
vif11.0 down failed
Feb 26 10:21:05 poseidon logger: /etc/xen/scripts/vif-bridge: Successful
vif-bridge offline for vif11.0, bridge xenbr1.
Feb 26 10:21:05 poseidon logger: /etc/xen/scripts/vif-bridge: brctl delif
xenbrlan0 vif11.1 failed
Feb 26 10:21:05 poseidon logger: /etc/xen/scripts/vif-bridge: ifconfig
vif11.1 down failed
Feb 26 10:21:06 poseidon logger: /etc/xen/scripts/xen-hotplug-cleanup:
XENBUS_PATH=backend/vif/11/0
Now, I just can boot xen choosing other network script, otherwise it does
not work.
best regards!
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Juan Antonio Cortés
2010-Mar-02 17:10 UTC
[Xen-users] Re: network bridge fails after reboot
hi, I solved this issue removing /var/lib/xen/save/* files and xen (via xenstored-rm) references . everything is working as ussualy with NO other change. (just a reboot) I restarted this server to change maxloops, but after the fail (It reached vif127.0) something weird happened every reboot while adding eth1 to bridge as described before. I hope this can help in event you face this Poltergeist. best regards. El 28 de febrero de 2010 13:29, Juan Antonio Cortés <jancorg@gmail.com>escribió:> Hi, > > I have been running a xen server with the same config for a year. > It has two bridges, one for all nodes and another one for a lan between > some nodes. It just worked well. > I rebooted the server for updating kernel max loop devs to 256 because I > cannot create more instances due to the limit. > > Now, the script only setup one network bridge and does not setu second. It > is supposed to be a mishandling with bridges since I configure xen with > vif-route and it works fine. At some point, xen tries to add the interface > to the bridge and it breaks the iface (see HWAddr). I compared all scripts > with very older backups and checked if apt updated the packages but software > seem to be the same. > > Since Xens breaks network interface trying to restore virtual machines, Im > wondering if is there any place where I can remove the start of this > machines. (They were running when I exec reboot) > > Please find bellow some info. > > Ifconfig ) > > eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:123.123.123.123 Bcast:123.123.123.247 > Mask:255.255.255.248 > > route) > > It just setup loopback and lan interface. > > > logs) > messages) > > Feb 26 10:19:06 poseidon kernel: device vif11.0 entered promiscuous mode > Feb 26 10:19:06 poseidon kernel: audit(1267201146.695:15): dev=vif11.0 > prom=256 old_prom=0 auid=4294967295 > Feb 26 10:19:06 poseidon kernel: ADDRCONF(NETDEV_UP): vif11.0: link is not > ready > Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled > state > Feb 26 10:20:47 poseidon kernel: device vif11.0 left promiscuous mode > Feb 26 10:20:47 poseidon kernel: audit(1267201247.214:16): dev=vif11.0 > prom=0 old_prom=256 auid=4294967295 > Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled > state > Feb 26 10:21:06 poseidon kernel: device vif12.0 entered promiscuous mode > Feb 26 10:21:06 poseidon kernel: audit(1267201266.019:17): dev=vif12.0 > prom=256 old_prom=0 auid=4294967295 > Feb > > regards! 26 10:21:06 poseidon kernel: ADDRCONF(NETDEV_UP): vif12.0: link is > not ready > Feb 26 10:22:46 poseidon kernel: xenbr1: port 2(vif12.0) entering disabled > state > Feb 26 10:22:46 poseidon kernel: device vif12.0 left promiscuous mode > Feb 26 10:22:46 poseidon kernel: audit(1267201366.425:18): dev=vif12.0 > prom=0 old_prom=256 auid=4294967295 > Feb 26 10:22:46 poseidon kernel: xenbr1: port 2(vif12.0) entering disabled > state > > syslog) > > Feb 26 10:19:06 poseidon kernel: device vif11.0 entered promiscuous mode > Feb 26 10:19:06 poseidon kernel: audit(1267201146.695:15): dev=vif11.0 > prom=256 old_prom=0 auid=4294967295 > Feb 26 10:19:06 poseidon kernel: ADDRCONF(NETDEV_UP): vif11.0: link is not > ready > Feb 26 10:19:06 poseidon logger: /etc/xen/scripts/vif-bridge: Successful > vif-bridge online for vif11.0, bridge xenbr1. > Feb 26 10:19:06 poseidon logger: /etc/xen/scripts/vif-bridge: Writing > backend/vif/11/0/hotplug-status connected to xenstore. > Feb 26 10:19:08 poseidon logger: /etc/xen/scripts/block: Writing > backend/vbd/11/2050/physical-device fe:39 to xenstore. > Feb 26 10:19:08 poseidon logger: /etc/xen/scripts/block: Writing > backend/vbd/11/2050/hotplug-status connected to xenstore. > Feb 26 10:19:09 poseidon logger: /etc/xen/scripts/block: Writing > backend/vbd/11/2049/physical-device fe:38 to xenstore. > Feb 26 10:19:09 poseidon logger: /etc/xen/scripts/block: Writing > backend/vbd/11/2049/hotplug-status connected to xenstore. > Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled > state > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/vif-bridge: offline > XENBUS_PATH=backend/vif/11/0 > Feb 26 10:20:47 poseidon kernel: device vif11.0 left promiscuous mode > Feb 26 10:20:47 poseidon kernel: audit(1267201247.214:16): dev=vif11.0 > prom=0 old_prom=256 auid=4294967295 > Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled > state > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/block: remove > XENBUS_PATH=backend/vbd/11/2050 > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/block: remove > XENBUS_PATH=backend/vbd/11/2049 > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/xen-hotplug-cleanup: > XENBUS_PATH=backend/vbd/11/2050 > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/xen-hotplug-cleanup: > XENBUS_PATH=backend/vbd/11/2049 > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/vif-bridge: offline > XENBUS_PATH=backend/vif/11/1 > Feb 26 10:20:53 poseidon logger: /etc/xen/scripts/vif-bridge: online > XENBUS_PATH=backend/vif/12/1 > Feb 26 10:20:53 poseidon logger: /etc/xen/scripts/block: add > XENBUS_PATH=backend/vbd/12/2049 > Feb 26 10:20:54 poseidon logger: /etc/xen/scripts/block: add > XENBUS_PATH=backend/vbd/12/2050 > Feb 26 10:20:54 poseidon logger: /etc/xen/scripts/vif-bridge: online > XENBUS_PATH=backend/vif/12/0 > Feb 26 10:21:01 poseidon logger: /etc/xen/scripts/vif-bridge: brctl delif > xenbr1 vif11.0 failed > Feb 26 10:21:04 poseidon logger: /etc/xen/scripts/vif-bridge: ifconfig > vif11.0 down failed > Feb 26 10:21:05 poseidon logger: /etc/xen/scripts/vif-bridge: Successful > vif-bridge offline for vif11.0, bridge xenbr1. > Feb 26 10:21:05 poseidon logger: /etc/xen/scripts/vif-bridge: brctl delif > xenbrlan0 vif11.1 failed > Feb 26 10:21:05 poseidon logger: /etc/xen/scripts/vif-bridge: ifconfig > vif11.1 down failed > Feb 26 10:21:06 poseidon logger: /etc/xen/scripts/xen-hotplug-cleanup: > XENBUS_PATH=backend/vif/11/0 > > > > > Now, I just can boot xen choosing other network script, otherwise it does > not work. > > best regards! > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
hi, I solved this issue removing /var/lib/xen/save/* files and xen (via xenstored-rm) references . everything is working as ussualy with NO other change. (just a reboot) I restarted this server to change maxloops, but after the fail (It reached vif127.0) something weird happened every reboot while adding eth1 to bridge as described before. I hope this can help in event you face this Poltergeist. best regards. El 28 de febrero de 2010 13:29, Juan Antonio Cortés <jancorg@gmail.com>escribió: Hi,> > I have been running a xen server with the same config for a year. > It has two bridges, one for all nodes and another one for a lan between > some nodes. It just worked well. > I rebooted the server for updating kernel max loop devs to 256 because I > cannot create more instances due to the limit. > > Now, the script only setup one network bridge and does not setu second. It > is supposed to be a mishandling with bridges since I configure xen with > vif-route and it works fine. At some point, xen tries to add the interface > to the bridge and it breaks the iface (see HWAddr). I compared all scripts > with very older backups and checked if apt updated the packages but software > seem to be the same. > > Since Xens breaks network interface trying to restore virtual machines, Im > wondering if is there any place where I can remove the start of this > machines. (They were running when I exec reboot) > > Please find bellow some info. > > Ifconfig ) > > eth1 Link encap:Ethernet HWaddr 00:00:00:00:00:00 > inet addr:123.123.123.123 Bcast:123.123.123.247 > Mask:255.255.255.248 > > route) > > It just setup loopback and lan interface. > > > logs) > messages) > > Feb 26 10:19:06 poseidon kernel: device vif11.0 entered promiscuous mode > Feb 26 10:19:06 poseidon kernel: audit(1267201146.695:15): dev=vif11.0 > prom=256 old_prom=0 auid=4294967295 > Feb 26 10:19:06 poseidon kernel: ADDRCONF(NETDEV_UP): vif11.0: link is not > ready > Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled > state > Feb 26 10:20:47 poseidon kernel: device vif11.0 left promiscuous mode > Feb 26 10:20:47 poseidon kernel: audit(1267201247.214:16): dev=vif11.0 > prom=0 old_prom=256 auid=4294967295 > Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled > state > Feb 26 10:21:06 poseidon kernel: device vif12.0 entered promiscuous mode > Feb 26 10:21:06 poseidon kernel: audit(1267201266.019:17): dev=vif12.0 > prom=256 old_prom=0 auid=4294967295 > Feb > > regards! 26 10:21:06 poseidon kernel: ADDRCONF(NETDEV_UP): vif12.0: link is > not ready > Feb 26 10:22:46 poseidon kernel: xenbr1: port 2(vif12.0) entering disabled > state > Feb 26 10:22:46 poseidon kernel: device vif12.0 left promiscuous mode > Feb 26 10:22:46 poseidon kernel: audit(1267201366.425:18): dev=vif12.0 > prom=0 old_prom=256 auid=4294967295 > Feb 26 10:22:46 poseidon kernel: xenbr1: port 2(vif12.0) entering disabled > state > > syslog) > > Feb 26 10:19:06 poseidon kernel: device vif11.0 entered promiscuous mode > Feb 26 10:19:06 poseidon kernel: audit(1267201146.695:15): dev=vif11.0 > prom=256 old_prom=0 auid=4294967295 > Feb 26 10:19:06 poseidon kernel: ADDRCONF(NETDEV_UP): vif11.0: link is not > ready > Feb 26 10:19:06 poseidon logger: /etc/xen/scripts/vif-bridge: Successful > vif-bridge online for vif11.0, bridge xenbr1. > Feb 26 10:19:06 poseidon logger: /etc/xen/scripts/vif-bridge: Writing > backend/vif/11/0/hotplug-status connected to xenstore. > Feb 26 10:19:08 poseidon logger: /etc/xen/scripts/block: Writing > backend/vbd/11/2050/physical-device fe:39 to xenstore. > Feb 26 10:19:08 poseidon logger: /etc/xen/scripts/block: Writing > backend/vbd/11/2050/hotplug-status connected to xenstore. > Feb 26 10:19:09 poseidon logger: /etc/xen/scripts/block: Writing > backend/vbd/11/2049/physical-device fe:38 to xenstore. > Feb 26 10:19:09 poseidon logger: /etc/xen/scripts/block: Writing > backend/vbd/11/2049/hotplug-status connected to xenstore. > Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled > state > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/vif-bridge: offline > XENBUS_PATH=backend/vif/11/0 > Feb 26 10:20:47 poseidon kernel: device vif11.0 left promiscuous mode > Feb 26 10:20:47 poseidon kernel: audit(1267201247.214:16): dev=vif11.0 > prom=0 old_prom=256 auid=4294967295 > Feb 26 10:20:47 poseidon kernel: xenbr1: port 2(vif11.0) entering disabled > state > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/block: remove > XENBUS_PATH=backend/vbd/11/2050 > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/block: remove > XENBUS_PATH=backend/vbd/11/2049 > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/xen-hotplug-cleanup: > XENBUS_PATH=backend/vbd/11/2050 > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/xen-hotplug-cleanup: > XENBUS_PATH=backend/vbd/11/2049 > Feb 26 10:20:47 poseidon logger: /etc/xen/scripts/vif-bridge: offline > XENBUS_PATH=backend/vif/11/1 > Feb 26 10:20:53 poseidon logger: /etc/xen/scripts/vif-bridge: online > XENBUS_PATH=backend/vif/12/1 > Feb 26 10:20:53 poseidon logger: /etc/xen/scripts/block: add > XENBUS_PATH=backend/vbd/12/2049 > Feb 26 10:20:54 poseidon logger: /etc/xen/scripts/block: add > XENBUS_PATH=backend/vbd/12/2050 > Feb 26 10:20:54 poseidon logger: /etc/xen/scripts/vif-bridge: online > XENBUS_PATH=backend/vif/12/0 > Feb 26 10:21:01 poseidon logger: /etc/xen/scripts/vif-bridge: brctl delif > xenbr1 vif11.0 failed > Feb 26 10:21:04 poseidon logger: /etc/xen/scripts/vif-bridge: ifconfig > vif11.0 down failed > Feb 26 10:21:05 poseidon logger: /etc/xen/scripts/vif-bridge: Successful > vif-bridge offline for vif11.0, bridge xenbr1. > Feb 26 10:21:05 poseidon logger: /etc/xen/scripts/vif-bridge: brctl delif > xenbrlan0 vif11.1 failed > Feb 26 10:21:05 poseidon logger: /etc/xen/scripts/vif-bridge: ifconfig > vif11.1 down failed > Feb 26 10:21:06 poseidon logger: /etc/xen/scripts/xen-hotplug-cleanup: > XENBUS_PATH=backend/vif/11/0 > > > > > Now, I just can boot xen choosing other network script, otherwise it does > not work. > > best regards! > > >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users