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/
Home Products Support Community News


Re: [Xen-devel] XEN 4.0 + pvops kernel : system crashes on sta

To: Yuvraj Agarwal <yuvraj@xxxxxxxxxxx>
Subject: Re: [Xen-devel] XEN 4.0 + pvops kernel : system crashes on starting 155th domU
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Tue, 27 Apr 2010 09:59:11 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 27 Apr 2010 07:01:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <019701cae5dd$01b36e70$051a4b50$@ucsd.edu>
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: <019701cae5dd$01b36e70$051a4b50$@ucsd.edu>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.19 (2009-01-05)
On Tue, Apr 27, 2010 at 12:41:07AM -0700, Yuvraj Agarwal wrote:
> Hi All, 
> We are setting up a system with a large number of very small VMs for a
> project. We worked through a number of limitations, including those
> imposed by blktap2 devices and the number of dynamic IRQ (set kernel
> config NR_CPUS) etc. After these changes we were able to get to  154 domUs
> (!), but as soon as we start up the 155th domU the system crashes. We
> edited each domU config to have one blktap2 device (the disk image) and
> two virtual network interfaces each. 

This sounds strangly familiar. I believe somebody posted a question
about this a couple of months ago on the xen-devel mailing list and
found the answer. I think part of it was CONFIG_LEGACY_PTY_COUNT had to
be high. But I don't remember the exact details - you might want to
search the archive.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>