From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: Para-Virt DomU + HVM DomU with xen 4.1.1 & linux 3.0.6 locks up system Date: Fri, 14 Oct 2011 10:00:30 -0400 Message-ID: <20111014140030.GF4577@phenom.oracle.com> References: <4E983A91.8040409@overnetdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <4E983A91.8040409@overnetdata.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: Anthony Wright Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org 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?