From mboxrd@z Thu Jan 1 00:00:00 1970 From: Anthony Wright Subject: Re: Para-Virt DomU + HVM DomU with xen 4.1.1 & linux 3.0.6 locks up system Date: Fri, 14 Oct 2011 16:16:58 +0100 Message-ID: <4E98526A.7090007@overnetdata.com> References: <4E983A91.8040409@overnetdata.com> <20111014140030.GF4577@phenom.oracle.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20111014140030.GF4577@phenom.oracle.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Konrad Rzeszutek Wilk Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 14/10/2011 15:00, Konrad Rzeszutek Wilk wrote: > On Fri, Oct 14, 2011 at 02:35:13PM +0100, Anthony Wright wrote: >> I have xen 4.1.1 running with a 3.0.6 linux kernel, both 32 bit. >> >> If I run 2 x para-virtualized DomUs they run fine. If I run 2 x HVM >> DomUs they run fine. If I run 1 x para-virtualized and 1 x HVM DomU (it >> doesn't matter which one is run first & which second), the system locks >> up just after I start the second DomU. > Locks up you say? When you launch the second guest, can you > also run 'while (true); do; xl list; sleep 1; done' to see if the memory > for Dom0 is going down to unreasonable amount? It behaves as if it's run out of memory as you say, but I did 'while true; do; xl list; sleep 0.2 ; done' on one session while I started the other DomU, and the system locked so quickly that the xl list didn't see any drop in Dom0 memory or the DomU even start. I have given Dom0 1000MB, and the HVM DomU also uses 1000MB (though it gets reported as 995MB). The para-virtual DomU uses 2000MB, and the machine has 8GB. Before I start the para-virtual DomU the commited AS_limit is around 141MB