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] Para-Virt DomU + HVM DomU with xen 4.1.1 & linux 3.0.6 l

To: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Subject: Re: [Xen-devel] Para-Virt DomU + HVM DomU with xen 4.1.1 & linux 3.0.6 locks up system
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Fri, 14 Oct 2011 17:42:56 +0300
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Anthony Wright <anthony@xxxxxxxxxxxxxxx>
Delivery-date: Fri, 14 Oct 2011 07:43:39 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20111014140030.GF4577@xxxxxxxxxxxxxxxxx>
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: <4E983A91.8040409@xxxxxxxxxxxxxxx> <20111014140030.GF4577@xxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Fri, Oct 14, 2011 at 10:00:30AM -0400, 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?
> 

Also are you using dom0_mem= for Xen? and did you disable dom0 ballooning?

Try enabling serial console and capturing all the Xen+dom0 console output..
http://wiki.xen.org/xenwiki/XenSerialConsole

-- Pasi


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