* DoSing Xend, unable to destroy domain
@ 2005-02-03 0:22 Jacob Gorm Hansen
0 siblings, 0 replies; 3+ messages in thread
From: Jacob Gorm Hansen @ 2005-02-03 0:22 UTC (permalink / raw)
To: xen-devel
hi,
just for fun my domain overwrote the shared_info_page with some repeated
random value, whereafter the domain stopped responding (no surprise there).
I could still 'xm list' my running domains, but trying to 'xm destroy'
the dead domain left xm hanging, and xend unresponsive. The only way to
get xend running again was by booting the machine.
Calling xc_destroy() in libxc directly still left the domain hanging.
This is in the unstable tree.
Jacob
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* RE: DoSing Xend, unable to destroy domain
@ 2005-02-03 0:36 Ian Pratt
2005-02-04 22:57 ` Jacob Gorm Hansen
0 siblings, 1 reply; 3+ messages in thread
From: Ian Pratt @ 2005-02-03 0:36 UTC (permalink / raw)
To: Jacob Gorm Hansen, xen-devel
> just for fun my domain overwrote the shared_info_page with
> some repeated
> random value, whereafter the domain stopped responding (no
> surprise there).
>
> I could still 'xm list' my running domains, but trying to 'xm
> destroy'
> the dead domain left xm hanging, and xend unresponsive. The
> only way to
> get xend running again was by booting the machine.
That shouldn't happen, but I'm not totally surprised. We know xend needs
to be a bit more defensive -- its one of the reasons for the planned
rewrite.
> Calling xc_destroy() in libxc directly still left the domain hanging.
I suspect this is due to xend not correctly closing down and freeing the
shared pages for the device channels. This will stop Xen from doing the
final cleanup of the domain, though most of the memory will have been
freed. Domains lingering in this state are ugly but fairly harmless.
Ian
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: DoSing Xend, unable to destroy domain
2005-02-03 0:36 Ian Pratt
@ 2005-02-04 22:57 ` Jacob Gorm Hansen
0 siblings, 0 replies; 3+ messages in thread
From: Jacob Gorm Hansen @ 2005-02-04 22:57 UTC (permalink / raw)
To: xen-devel
Ian Pratt wrote:
>>I could still 'xm list' my running domains, but trying to 'xm
>>destroy'
>>the dead domain left xm hanging, and xend unresponsive. The
>>only way to
>>get xend running again was by booting the machine.
>
>
> That shouldn't happen, but I'm not totally surprised. We know xend needs
> to be a bit more defensive -- its one of the reasons for the planned
> rewrite.
Actually this a bit worse that I first thought, even a normal domU
sitting in a tight loop seems immune to destruction :-(
Jacob
-------------------------------------------------------
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2005-02-04 22:57 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2005-02-03 0:22 DoSing Xend, unable to destroy domain Jacob Gorm Hansen
-- strict thread matches above, loose matches on Subject: below --
2005-02-03 0:36 Ian Pratt
2005-02-04 22:57 ` Jacob Gorm Hansen
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.