[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-devel] More driver domain issues - rebooting backend hangs
Thanks for the response Ian. I've tried this with xen-2.0.3, 2.0.4 and xen-2.0-testing.bk (the latest from yesterday at 16:00 AST -4:00). Looking into the xend.log/xend-debug.log files, what it appears I should see is: [2005-02-06 21:13:28 xend] INFO (XendRoot:91) EVENT> xend.domain.shutdown ['be03-3c59x', '3', 'poweroff'] [2005-02-06 21:13:38 xend] INFO (XendDomain:564) Destroying domain: name=be03-3c59x [2005-02-06 21:13:38 xend] INFO (XendRoot:91) EVENT> xend.virq 4 [2005-02-06 21:13:38 xend] INFO (XendRoot:91) EVENT> xend.domain.exit ['be03-3c59x', '3', 'poweroff'] [2005-02-06 21:13:38 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy ['be03-3c59x', '3'] [2005-02-06 21:13:39 xend] INFO (XendRoot:91) EVENT> xend.domain.died ['be03-3c59x', '3'] but instead get (looping): [2005-02-06 20:30:22 xend] INFO (XendRoot:91) EVENT> xend.domain.shutdown ['be03-3c59x', '3', 'poweroff'] [2005-02-06 20:30:34 xend] INFO (XendDomain:564) Destroying domain: name=be03-3c59x [2005-02-06 20:30:34 xend] INFO (XendRoot:91) EVENT> xend.virq 4 [2005-02-06 20:30:34 xend] INFO (XendRoot:91) EVENT> xend.domain.exit ['be03-3c59x', '3', 'poweroff'] [2005-02-06 20:30:34 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy ['be03-3c59x', '3'] [2005-02-06 20:32:58 xend] INFO (XendDomain:564) Destroying domain: name=be03-3c59x [2005-02-06 20:32:58 xend] INFO (XendRoot:91) EVENT> xend.domain.exit ['be03-3c59x', '3', 'poweroff'] [2005-02-06 20:32:58 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy ['be03-3c59x', '3'] [2005-02-06 20:33:01 xend] INFO (XendDomain:564) Destroying domain: name=be03-3c59x [2005-02-06 20:33:01 xend] INFO (XendRoot:91) EVENT> xend.domain.exit ['be03-3c59x', '3', 'poweroff'] [2005-02-06 20:33:01 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy ['be03-3c59x', '3'] [2005-02-06 20:33:03 xend] INFO (XendDomain:564) Destroying domain: name=be03-3c59x [2005-02-06 20:33:03 xend] INFO (XendRoot:91) EVENT> xend.domain.exit ['be03-3c59x', '3', 'poweroff'] [2005-02-06 20:33:03 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy ['be03-3c59x', '3'] [2005-02-06 20:33:05 xend] INFO (XendDomain:564) Destroying domain: name=be03-3c59x [2005-02-06 20:33:05 xend] INFO (XendRoot:91) EVENT> xend.domain.exit ['be03-3c59x', '3', 'poweroff'] [2005-02-06 20:33:05 xend] INFO (XendRoot:91) EVENT> xend.domain.destroy ['be03-3c59x', '3'] On Sun, 2005-02-06 at 21:51, Ian Pratt wrote: > > When rebooting the backend driver domain, if it has been utilized by a > > normal domU, it will close down properly and then hang (not > > reboot). I'm > > left rebooting the whole box. Is this to be expected? This even > > happens if the normal domU has been powered off. > > It certainly never used to be a problem with the old xend, but running > separate driver domains has not been widely tested with the current one. > > If you're using a debug build of Xen with a serial console, it might be > worth hitting 'o' to find out what resources the domain is still > holding. I will try this and email you back > Ian > If there is any other information that I can/should provide, please let me know. B. ------------------------------------------------------- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |