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-devel

Re: [Xen-devel] xm sched-credit2 - changing weight of dom0 freezes machi

To: John Weekes <lists.xen@xxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xm sched-credit2 - changing weight of dom0 freezes machine
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Mon, 28 Mar 2011 11:04:33 +0300
Cc: George Dunlap <george.dunlap@xxxxxxxxxxxxx>, "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>
Delivery-date: Mon, 28 Mar 2011 01:06:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4D903900.1020401@xxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4D903900.1020401@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Mon, Mar 28, 2011 at 12:30:08AM -0700, John Weekes wrote:
> In testing credit2, I have observed that changing the weight of dom0  
> freezes a machine on RELEASE-4.1.0. Executing this command immediately  
> causes a freeze, for instance:
>
> xm sched-credit2 -d 0 -w 256
>

Ouch. Any output at all on the console?

> This is with the latest stable-2.6.32 (2.6.32.35-gdf3a556). I haven't  
> tested with credit2 previously, so I don't know how long this problem  
> has existed.
>
> I also saw a different freeze event after starting up 20 or so domains  
> on one machine. There were no messages in the xend.log or  
> /var/log/messages after the freeze -- the machine just stopped  
> responding, as it does when trying to change the dom0 weight. How can I  
> effectively debug this if I see it happen again?
>

You should set up a serial console and enable various debugging/logging 
options..

Serial console: http://wiki.xensource.com/xenwiki/XenSerialConsole
Various debugging options for dom0 kernel: 
http://wiki.xen.org/xenwiki/XenParavirtOps

-- Pasi


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

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