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


[Xen-changelog] [xen-unstable] xm-test: ia64 min memory & arbitrarily la

To: xen-changelog@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-changelog] [xen-unstable] xm-test: ia64 min memory & arbitrarily large ramdisk
From: Xen patchbot-unstable <patchbot-unstable@xxxxxxxxxxxxxxxxxxx>
Date: Mon, 04 Jun 2007 03:15:46 -0700
Delivery-date: Mon, 04 Jun 2007 03:17:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-changelog-request@lists.xensource.com?subject=help>
List-id: BK change log <xen-changelog.lists.xensource.com>
List-post: <mailto:xen-changelog@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-changelog>, <mailto:xen-changelog-request@lists.xensource.com?subject=unsubscribe>
Reply-to: xen-devel@xxxxxxxxxxxxxxxxxxx
Sender: xen-changelog-bounces@xxxxxxxxxxxxxxxxxxx
# HG changeset patch
# User kfraser@xxxxxxxxxxxxxxxxxxxxx
# Date 1180017654 -3600
# Node ID d1cce5bafe288e166b9eea40dc72a7514d36d897
# Parent  e046da853ffc4488c843ea7ac3f15852af81d4bf
xm-test: ia64 min memory & arbitrarily large ramdisk

1) Sets a minimum of 128MB RAM for an ia64 domU; this limit was set
after experimentation, which seems to indicate it's a reasonable lower
limit (the 32MB limit previously in place did not allow an ia64 domU
to start).  If there's any problem with this, I don't mind splitting
the patch and sending it to the ia64 list, but it was small, so I hope
it's okay to include it.

2) xm-test uses ramdisks built with uClibc, which doesn't compile on
ia64.  I was able to create a ramdisk by hand, but as it was too
large, the resultant domU crashed after boot.  This patch enables the
use of an arbitrarily large ramdisk, so long as it's uncompressed.  As
xm-test builds only uncompressed ramdisks, I figured this was
reasonable for that specific application.  Suggestions on how to
detect and handle a compressed ramdisk would be welcome.

Signed-off-by: Alex Williamson <alex.williamson@xxxxxx>
 tools/xm-test/lib/XmTestLib/arch.py |   14 ++++++++++++++
 1 files changed, 14 insertions(+)

diff -r e046da853ffc -r d1cce5bafe28 tools/xm-test/lib/XmTestLib/arch.py
--- a/tools/xm-test/lib/XmTestLib/arch.py       Thu May 24 15:36:13 2007 +0100
+++ b/tools/xm-test/lib/XmTestLib/arch.py       Thu May 24 15:40:54 2007 +0100
@@ -45,6 +45,9 @@ def ia_checkBuffer(buffer):
 def ia_minSafeMem():
     return 32
+def ia64_minSafeMem():
+    return 128
 def ia_getDeviceModel():
     """Get the path to the device model based on
@@ -139,6 +142,17 @@ if _arch == "x86" or _arch == "x86_64" o
         configDefaults = ia_HVMDefaults
         configDefaults = ia_ParavirtDefaults
+    # note: xm-test generates an uncompressed image, and this code
+    # expects one.  This will fail with a gzip-ed image. 
+    if configDefaults['ramdisk']:
+        rd_size = os.stat(configDefaults['ramdisk']).st_size
+        configDefaults['extra'] = 'ramdisk_size=' + str((rd_size / 1024)+1)
+    if _arch == "ia64":
+        minSafeMem = ia64_minSafeMem
+        configDefaults['memory'] = ia64_minSafeMem()
 elif _arch == "powerpc":
     minSafeMem = ppc_minSafeMem
     getDefaultKernel = ppc_getDefaultKernel

Xen-changelog mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-changelog] [xen-unstable] xm-test: ia64 min memory & arbitrarily large ramdisk, Xen patchbot-unstable <=