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: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-devel] More Xen troubles (with xend this time)
From: Jérôme Petazzoni <jp@xxxxxxxx>
Date: Tue, 30 Nov 2004 17:45:29 +0100
Delivery-date: Tue, 30 Nov 2004 16:46:27 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <E1CZ8h0-0007Wq-00@xxxxxxxxxxxxxxxxx>
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>
References: <E1CZ8h0-0007Wq-00@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.8 (X11/20040926)

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
Okay, and once we "lost" xend, there is no way to do anything ? (create, destroy, shutdown, get a console...)

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.
I will do my best to reboot the box and try to reproduce the problem. But if the restore operation crashes xend, I will never be able to get a crash dump - unless there's another way to get the information ?

If I don't use save/restore/migrate, can I expect Xen to be stable ? Or are there other features that are deemed to cause problems ?

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. http://productguide.itmanagersjournal.com/
Xen-devel mailing list