[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] RE: [Xen-users] Building XEN with different config PROBLEM
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 _______________________________________________ Xen-users mailing list Xen-users@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-users
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |