From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Weekes <lists.xen@nuclearfallout.net>
Subject: xm sched-credit2 - changing weight of dom0 freezes
	machine
Date: Mon, 28 Mar 2011 00:30:08 -0700
Message-ID: <4D903900.1020401@nuclearfallout.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>, Keir Fraser <keir@xen.org>, George Dunlap <george.dunlap@eu.citrix.com>
List-Id: xen-devel@lists.xenproject.org

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

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?

-John