[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] DoSing Xend, unable to destroy domain

  • To: "Jacob Gorm Hansen" <jacobg@xxxxxxx>, "xen-devel" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Thu, 3 Feb 2005 00:36:00 -0000
  • Delivery-date: Thu, 03 Feb 2005 00:39:38 +0000
  • List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
  • Thread-index: AcUJhwMiG/6rty+tQqKvoyS2HAtmewAANFlg
  • Thread-topic: [Xen-devel] DoSing Xend, unable to destroy domain

> 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
> 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.


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



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.