From mboxrd@z Thu Jan  1 00:00:00 1970
From: Charles Duffy <cduffy@spamcop.net>
Subject: [WORKAROUND] Re: current Xen3 (446aa56ca4fe) unable to
 reboot XenU ("cannot allocate memory")
Date: Mon, 17 Oct 2005 19:02:06 -0500
Message-ID: <dj1e23$i2s$1@sea.gmane.org>
References: <dj14d0$nqd$1@sea.gmane.org>
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>
In-Reply-To: <dj14d0$nqd$1@sea.gmane.org>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/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/cgi-bin/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
List-Id: xen-devel@lists.xenproject.org

Setting dom0_mem such that it's not necessary to balloon out on the 
restart appears to work around this issue, such that the DomU is 
successfully restarted by xend.