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


[Xen-users] Re: Lenny DomU crash!

To: Simon Hobson <linux@xxxxxxxxxxxxxxxx>
Subject: [Xen-users] Re: Lenny DomU crash!
From: Ferenc Wagner <wferi@xxxxxxx>
Date: Sat, 18 Jul 2009 22:14:15 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 18 Jul 2009 13:15:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <a06240809c68743b75074@xxxxxxxxxxxxxxxxxxxxxx> (Simon Hobson's message of "Sat, 18 Jul 2009 10:21:02 +0100")
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <002301ca05e8$4778efa0$d66acee0$@it> <7207d96f0907160053k16f95602m46fd4ba124934ef5@xxxxxxxxxxxxxx> <a06240807c684bac9f76f@xxxxxxxxxxxxxxxxxxxxxx> <87eisec03d.fsf@xxxxxxxxxxxxx> <a06240809c68743b75074@xxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/21.4 (gnu/linux)
Simon Hobson <linux@xxxxxxxxxxxxxxxx> writes:

> From the first link, I see that this event is characterised by an
> inability to start PV guests and existing guests showing state
> blocked. 

When a guest is stuck this way, it's constantly in running state.
There is some confusion in the report, yes.

> In my case, I can start a PV guest, and the stuck guest shows state
> running and consumes 100% cpu.

Yes, that agrees with my experience.

> Also, if it were that, wouldn't I expect to see other guests on the
> same host lock up ?

It isn't that simple.  Other guests lock up when they fill their
console buffers, apparently.  But new guests seem to work fine for
me.  Just try it, when you next experience this: stop xend, kill
xenconsoled, start xends.  Don't touch xenstored!  If everything
returns to normal, then this was it.  If not, then something else. :)

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>