WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

Re: [Xen-users] 'xm list' states

To: "Petersson, Mats" <Mats.Petersson@xxxxxxx>
Subject: Re: [Xen-users] 'xm list' states
From: Anthony Liguori <aliguori@xxxxxxxxxx>
Date: Mon, 24 Apr 2006 15:37:35 -0500
Cc: xen-users@xxxxxxxxxxxxxxxxxxx, Timo Benk <timo.benk@xxxxxx>
Delivery-date: Mon, 24 Apr 2006 13:38:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <907625E08839C4409CE5768403633E0BA7FBFD@xxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <907625E08839C4409CE5768403633E0BA7FBFD@xxxxxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mail/News 1.5 (X11/20060309)
Petersson, Mats wrote:
Anthony added:
Petersson, Mats wrote:
'c' (crashed) - The domain has crashed.
- If i do 'echo 1 > /proc/balloon' inside a unprivileged domain, i
will get a kernel panic. But the state says nothing
about that? The
domain is definitively crashed, but the xm list command
says nothing
  about that. Why?
It may be that the crash isn't detected properly by hypervisor - I think this may only work under some circumstances. I don't know for sure, I'm just guessing here.
A crash is when the domain does something that it shouldn't supposed to do and the hypervisor has to kill it. I imagine that an OOM condition in the guest will invoke the normal shutdown routines which would explain why the state isn't crashed.

Thanks for the further explanations.
So the 'c' state is entereed when we call domain_crash_synchrnous() in
the hypervisor, right?

Yes, I should also add that libxc confuses things a bit by making the crashed state not appear to be the substate of shutdown (which it is). The kernel is able to crash itself by specifying SHUTDOWN_crash.

Regards,

Anthony Liguori

--
Mats




_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

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