From: "B.G. Bruce" <bgb@nt-nv.com>
To: xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: More driver domain issues - rebooting backend hangs
Date: Sun, 06 Feb 2005 07:23:25 -0400 [thread overview]
Message-ID: <1107689005.4411.252.camel@master.vms.security> (raw)
In-Reply-To: <1107531421.4411.224.camel@master.vms.security>
On Fri, 2005-02-04 at 11:37, B.G. Bruce 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.
I would still be really interested to know if anyone else using driver
domains experiences this. If this is "normal/expected" behavior, I will
stop bug hunting and continue on with life. If not, then I may
reconsider using driver domains at this time.
>
> Second issue. About half the time that I reboot the driver domain (no
> connections from any outside domain), I'm left xm consoling to the
> domain to hit the enter key on a simple line of:
>
> echo "0" > /sys/bus/pci/slots:0000\:01:\01.1/power
>
> I'm using the fake pci hotplug module so that I can reboot the driver
> domain and still have the network card come back up after the reboot.
>
> Any ideas?
This one has been solved ... it was a hotplug issue.
> 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@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/xen-devel
>
-------------------------------------------------------
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-06 11:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 15:37 More driver domain issues - rebooting backend hangs B.G. Bruce
2005-02-06 11:23 ` B.G. Bruce [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-02-07 1:51 Ian Pratt
2005-02-07 13:48 ` B.G. Bruce
2005-02-07 22:16 ` B.G. Bruce
2005-02-08 11:58 ` B.G. Bruce
2005-02-08 12:53 ` B.G. Bruce
2005-02-08 22:45 Ian Pratt
2005-02-09 0:47 ` 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=1107689005.4411.252.camel@master.vms.security \
--to=bgb@nt-nv.com \
--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.