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] [PATCH][XM-TEST] Test that tries to create a 16MB domain

To: Jacob Gorm Hansen <jacobg@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH][XM-TEST] Test that tries to create a 16MB domain
From: Dan Smith <danms@xxxxxxxxxx>
Date: Thu, 17 Nov 2005 15:11:21 -0800
Cc: Xen Developers <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 17 Nov 2005 23:11:21 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <87r79gcv60.fsf@xxxxxxxxxxxxxxxxxxxxxxxx> <e08041f30511170315v2c8257f7jf4bd47edd66ffdb9@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
JH> I routinely create 4M domains (and I would be able to create them
JH> even smaller if the domain builder would allow it), there is event
JH> a recent Xen paper that mentions running ttylinux in this amout of
JH> space.

But not with a 4M ramdisk, I'm guessing, which is what xm-test uses :)

JH> I think this is a problem in XenLinux, it was discussed recently,
JH> and that you can 'fix' it by setting mem=16M on the linux command
JH> line.

This may be true, however, I am unable to start a 16MB domain with
extra="mem=16M" on x86_64 (x86_32 works).  The domain hangs when
trying to unpack the ramdisk.  I'll submit a patch that adds the
mem=16M argument to the kernel command line so that it will pass on 32
bit.

If there's something different about x86_64 that limits the minimum
size of a domain, then I re-argue for some sort of arch-specific soft
limit to "help" the user realize that they are doing something that is
likely to fail.

-- 
Dan Smith
IBM Linux Technology Center
Open Hypervisor Team
email: danms@xxxxxxxxxx


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