[Xen-devel] vif's disappear after dom1 reboot

[Wensheng Wang <wenshengwang@xxxxxxxxx>]

Today I found I can not ping some of my domU's.  I logged in to dom0,
did a "xm list", all domU are there.   Then I did a "ifconfig" and
surprised to find some of vif's disappeared!
Like for example.  "xm list" show dom13 is alive, but "brctl show"
shows no vif13.0.

If I "xm console 13", there's some message:
WARNING: g.e. still in use!
WARNING: leaking g.e. and page still in use!


I found following in /var/log/message:
------------------------------------------------------------------------------------------------
Jan  4 21:06:31 m7 kernel: xenbr0: port 3(vif1.0) entering disabled state
Jan  4 21:06:31 m7 kernel: device vif1.0 left promiscuous mode
Jan  4 21:06:31 m7 kernel: xenbr0: port 3(vif1.0) entering disabled state
Jan  4 21:06:32 m7 kernel: xenbr0: port 12(vif10.0) entering disabled state
Jan  4 21:06:32 m7 kernel: device vif10.0 left promiscuous mode
Jan  4 21:06:32 m7 kernel: xenbr0: port 12(vif10.0) entering disabled state
Jan  4 21:06:32 m7 kernel: xenbr0: port 8(vif13.0) entering disabled state
Jan  4 21:06:32 m7 kernel: device vif13.0 left promiscuous mode
Jan  4 21:06:32 m7 kernel: xenbr0: port 8(vif13.0) entering disabled state
Jan  4 21:06:33 m7 kernel: device vif26.0 entered promiscuous mode
Jan  4 21:06:33 m7 kernel: xenbr0: port 4(vif14.0) entering disabled state
Jan  4 21:06:33 m7 kernel: device vif14.0 left promiscuous mode
Jan  4 21:06:33 m7 kernel: xenbr0: port 4(vif14.0) entering disabled state
Jan  4 21:06:33 m7 kernel: xenbr0: port 3(vif26.0) entering learning state
Jan  4 21:06:33 m7 kernel: xenbr0: port 13(vif16.0) entering disabled state
Jan  4 21:06:33 m7 kernel: xenbr0: topology change detected, propagating
Jan  4 21:06:33 m7 kernel: xenbr0: port 3(vif26.0) entering forwarding state
Jan  4 21:06:34 m7 kernel: device vif16.0 left promiscuous mode
Jan  4 21:06:34 m7 kernel: xenbr0: port 13(vif16.0) entering disabled state
--------------------------------------------------------------------------------------------------

And xend.log shows at around 21:06:31, dom 1 rebooted and no other
domains were shutdown or rebooted.

So it appears this dom 1 reboot knock off some other vif's.

I can reproduce this and found only dom 1 reboot disable other vif's. 
 Rebooting domains other than dom 1 has no problem.

I use xen3.0-testing (changeset 8259:5baa96bedc13)
dom0 OS is fedora core 4.  use default bridge configuration.

Bug?

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