[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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


  • To: "Steffen Heil" <lists@xxxxxxxxxxxxxxx>
  • From: "Chris Fanning" <christopher.fanning@xxxxxxxxx>
  • Date: Wed, 6 Jun 2007 15:16:21 +0200
  • Cc: xen-users@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Wed, 06 Jun 2007 06:14:34 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=btpxF8sYaRocqQ70i8gHUD5QuuTw+Q7Ryhy9CtEtLu4Xb5RCSlGLGRBgl2CQXH1HJBZvHb6okTCWbG6Jq6uvUdSjprtMeXevJtEhihmTS4aEDCkcV1UYXoiasCrGgHW4nkQFdOLJPp9SP3Uh0rCwqrX8yClT6hC6yrwWwUWnOzM=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

Hi,

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

Thanks very much, I'll try it. Installing Xen just got a little bit
more complicated :(

But, doesn't this seem a strange?
You know, isn't configuring the kernel a normal thing to expect people to do?

I'd really like to know if this is an oversight on the part of the
developers or if they have instead crafted some other mecanism.

Chris.

On 6/6/07, Steffen Heil <lists@xxxxxxxxxxxxxxx> wrote:
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



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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.