From: "B.G. Bruce" <bgb@nt-nv.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>
Cc: xen-devel <xen-devel@lists.sourceforge.net>
Subject: RE: More driver domain issues - rebooting backend hangs
Date: Mon, 07 Feb 2005 09:48:03 -0400 [thread overview]
Message-ID: <1107784083.4411.288.camel@master.vms.security> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D123740@liverpoolst.ad.cl.cam.ac.uk>
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
next prev parent reply other threads:[~2005-02-07 13:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-07 1:51 More driver domain issues - rebooting backend hangs Ian Pratt
2005-02-07 13:48 ` B.G. Bruce [this message]
2005-02-07 22:16 ` B.G. Bruce
2005-02-08 11:58 ` B.G. Bruce
2005-02-08 12:53 ` B.G. Bruce
-- strict thread matches above, loose matches on Subject: below --
2005-02-08 22:45 Ian Pratt
2005-02-09 0:47 ` B.G. Bruce
2005-02-04 15:37 B.G. Bruce
2005-02-06 11:23 ` B.G. Bruce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1107784083.4411.288.camel@master.vms.security \
--to=bgb@nt-nv.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.