This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] More Xen troubles (with xend this time)

To: Jérôme Petazzoni <jp@xxxxxxxx>
Subject: Re: [Xen-devel] More Xen troubles (with xend this time)
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Tue, 30 Nov 2004 14:09:22 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Tue, 30 Nov 2004 14:10:22 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 30 Nov 2004 14:45:53 +0100." <41AC7991.80506@xxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> When trying to reproduce a crash (when I do "xm restore foo.xen", the 
> restored VM crashed instantaneously), I hit the following "bug" (I hope 
> that the problem lies between my keyboard and my chair and that I didn't 
> find another real bug) :
> I did restore the domain, then noticed it was crashed ("-----c" in xm 
> list). I tried to destroy it, but it didn't work. So I stopped xend, 
> restarted it ... And there it goes :

Restarting xend was a bit of a brave move. Although its intended
to be restartable, there are definitely bugs in the restart code,
particularly if you have domains in unusual states at the time
(e.g. crashed, awaiting reaping). Error case code is always the
least tested...

As to why the domain wouldn't be destroyed, that may turn out to
be a useful clue as to the resume problem at its root. If we
could get a crashdump from a known kernel image I'm sure we can
fix this pretty easily.


SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
Xen-devel mailing list