http://bugzilla.novell.com/show_bug.cgi?id=618678 http://bugzilla.novell.com/show_bug.cgi?id=618678#c12 --- Comment #12 from James Fehlig <jfehlig@novell.com> 2010-07-02 18:04:52 UTC --- I built a debug netbk by defining DPRINTK as printk("JWF (%s:%d) " fmt ".\n", __FUNCTION__, __LINE__, ##args) in netback/common.h. When doing a normal shutdown I get the following messages Jul 2 11:46:56 xen48 kernel: [ 1172.813625] JWF (frontend_changed:220) Closed. When doing 'xm destroy' I get Jul 2 11:49:25 xen48 kernel: [ 1321.655682] JWF (frontend_changed:220) Unknown. In both cases, xend has invoked destoryDevice on the vif {2010-07-02 11:49:25 3453] DEBUG (XendDomainInfo:1289) XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0 which writes 'online=0' and 'state=Closing' (Closing = 5) to vif backend node in xenstore. In fact, the vif backend path still exists and contains the expected state xen48:~ # xenstore-ls /local/domain/0/backend/vif 2 = "" 0 = "" bridge = "br0" domain = "os11.3" handle = "0" uuid = "6a2ba18b-6fd9-1765-4c85-dbf8017fed5e" script = "/etc/xen/scripts/vif-bridge" state = "5" frontend = "/local/domain/2/device/vif/0" mac = "00:16:3e:5b:ad:25" online = "0" frontend-id = "2" feature-sg = "1" feature-gso-tcpv4 = "1" feature-rx-copy = "1" feature-rx-flip = "0" hotplug-status = "connected" I'm not sure why netbk reads state 'Unknown' instead of 'Closing'. Oh, one final note. netbk dumps a lot of the following messages once it gets in this state Jul 2 11:51:01 xen48 kernel: [ 1417.987320] JWF (netbk_check_gop:529) Bad status -1 from copy to DOM2. -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.