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-users] (xen) Possible bug: Memory squeeze in netback driver.

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] (xen) Possible bug: Memory squeeze in netback driver.
From: Kanwar Ranbir Sandhu <m3freak@xxxxxxxxxx>
Date: Wed, 14 Jun 2006 09:24:27 -0400
Delivery-date: Wed, 14 Jun 2006 06:25:23 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=rogers.com; h=Received:Subject:From:To:In-Reply-To:References:Content-Type:Date:Message-Id:Mime-Version:X-Mailer:Content-Transfer-Encoding; b=mpxxR9Vgf9ez4OGaol+YtFk6M8bphDKJqyR5OYP4PcuU0AjXDRaVWnZB7skFzEh9E3CIweNWwO4W+UotYCUGID11xJwT5iPjIuiB/Gt4DLX9hvs6SNZFihBqb3Qhqd9bx7id62A7yEuf7lmU0iqXxhiF3ygdpPnuY4hWK212Lx0= ;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1150257065.5782.27.camel@krs>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <200606062047.44746.erik@xxxxxxxxxxx> <1150257065.5782.27.camel@krs>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
On Tue, 2006-13-06 at 23:51 -0400, Kanwar Ranbir Sandhu wrote:
> It's a head scratcher, all right.  I have no idea what it means, so I'm
> reduced to tinkering with the config files, including lowering memory
> usage for my one working domU.  Haven't tried it yet, though.

My second domU is up and running now.

I had forgotten to copy the modules for the xen linux kernel from dom0
to the new domU.  So, I did that, and lowered the memory allocated to
the first domU.  The second domU booted without any problems.

I'm not sure which one of the above fixed it for me, but I'd recommend
looking into both.



Kanwar Ranbir Sandhu
Linux 2.6.16-1.2111_FC4 i686 GNU/Linux 
09:16:29 up 1 day, 2:46, 2 users, load average: 0.11, 0.11, 0.05 

Xen-users mailing list