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-users

RE: [Xen-users] Building XEN with different config PROBLEM

To: "'Chris Fanning'" <christopher.fanning@xxxxxxxxx>
Subject: RE: [Xen-users] Building XEN with different config PROBLEM
From: "Steffen Heil" <lists@xxxxxxxxxxxxxxx>
Date: Wed, 6 Jun 2007 15:08:06 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 06 Jun 2007 06:07:42 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <215ff4410706060458q7b8a0f76g85ddb959216f9e32@xxxxxxxxxxxxxx>
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: <97D1EA73AEF14ADDB1D731A51736EB19@shs1> <215ff4410706060458q7b8a0f76g85ddb959216f9e32@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AceoMh4W1ilaTS0ISTyo0YmZWUXNUwACKgGA
Hi

> I have the same problem.
> Did you solve this question?

Yes.

More hacking than really solving, but it works. I now use the following
script:

rm -rf xen-3.1.0-src
tar xzf xen-3.1.0-src.tgz
cd xen-3.1.0-src
mkdir -p dist/install/boot
cp ../config/$1/xen0 dist/install/boot/config-2.6.18-xen0
cp ../config/$1/xenU dist/install/boot/config-2.6.18-xenU
make KERNELS="linux-2.6-xen0 linux-2.6-xenU" dist
cd dist/
tar czf ../../dist/$1-xen3.1.tgz .
cd ../..
rm -rf xen-3.1.0-src


The only downside is, that the configuration of the created kernels slightly
differs from my given configs:

xen0:
162,163c162,163
< # CONFIG_HIGHMEM4G is not set
< CONFIG_HIGHMEM64G=y
---
> CONFIG_HIGHMEM4G=y
> # CONFIG_HIGHMEM64G is not set
166d165
< CONFIG_X86_PAE=y
843a843,844

xenU:
< # CONFIG_HIGHMEM4G is not set
< CONFIG_HIGHMEM64G=y
---
> CONFIG_HIGHMEM4G=y
> # CONFIG_HIGHMEM64G is not set
158c158,160
< CONFIG_X86_PAE=y
---
> # CONFIG_FLATMEM_MANUAL is not set
> # CONFIG_DISCONTIGMEM_MANUAL is not set
> # CONFIG_SPARSEMEM_MANUAL is not set
163c165
< CONFIG_RESOURCES_64BIT=y
---
> # CONFIG_RESOURCES_64BIT is not set

So actually, the build process forces HIGHMEM64G and CONFIG_X86_PAE and in
domU also RESOURCES_64BIT.
I don't know why. However those kernels work fine on my systems.

If someone knows, please let me know.

Regards,
  Steffen

Attachment: smime.p7s
Description: S/MIME cryptographic signature

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