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 17:02:10 +0000
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Tue, 30 Nov 2004 17:03:22 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: Your message of "Tue, 30 Nov 2004 17:45:29 +0100." <41ACA3A9.20305@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
> >>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...)

If you can't restart it, your stuffed.
> >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 ?

Put '-c' on the restore command line to connect to the console.

> If I don't use save/restore/migrate, can I expect Xen to be
> stable ? 

It's stable for most people even using save/restore/migrate. It
must be something about your particular setup or configuration
which is provoking the bug. We've actually put a fair amount of
effort into trying to reproduce the resume crash, but haven't
managed it. 

> Or are there other features that are deemed to cause problems ?

The list of known bugs is currently remarkably short, and mostly
related to certain hardware (drivers or ioapics).


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