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] can't create any more pv-on-hvm domains after~38under 3.

To: James Harper <james.harper@xxxxxxxxxxxxxxxx>, Jan Beulich <jbeulich@xxxxxxxxxx>
Subject: Re: [Xen-devel] can't create any more pv-on-hvm domains after~38under 3.3-testing
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Wed, 03 Dec 2008 11:35:11 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 03 Dec 2008 03:35:38 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <AEC6C66638C05B468B556EA548C1A77D0154FE66@trantor>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AclTmGJLz8h42+pCRU+dWJTw8j7bUgBnCiZwAAEjtigAABg8AAAAbiyo
Thread-topic: [Xen-devel] can't create any more pv-on-hvm domains after~38under 3.3-testing
User-agent: Microsoft-Entourage/12.14.0.081024
On 03/12/2008 11:27, "James Harper" <james.harper@xxxxxxxxxxxxxxxx> wrote:

> Alternatively it could be a combination of the gplpv drivers and netback
> or blkback. I'm pretty sure that I had the problem before I started
> testing pvscsi...
> 
> The machine I am testing on will be busy for the rest of the night, but
> tomorrow I'll do some testing and see what happens, unless you can
> suggest a way I could discover what those pages belong to in the
> meantime?

Unfortunately it's a bit of a pain in the butt since we don't have full page
tracking in Xen -- we only know that *someone* *somewhere* has that page
mapped for *some* purpose. Indeed even with more tracking Xen can only
really tell you which domain holds the reference, and that's bound to be
dom0 (unless this is a bogus refcounting bug in Xen itself).

I would suggest dumping addresses of interesting control pages in your
backend drivers (some can log that already if built with debugging I think),
then match up the address of the remaining page in the zombie domain.

 -- Keir



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

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