Re: [Xen-users] how to build xen + dom0 and domU from source?

[Riccardo Veraldi <Riccardo.Veraldi@xxxxxxxxxxxx>]

it won't work.
it will work straight for kernel 2.6.18.
But for any other kernels 2.6.18.X it won't work.
Otherwise you need specific patches to be applied but they are not 
present in hte default
xen 3.1.0 sources.
I can provide you a src rpm with all te patches needed to compile Xen 3.1.2
under the latest RHEL5 kernel 2.6.18-53.1.4

Rick


TMC wrote:
> Hi Guys.
>
> I am trying to build xen 3.1 + linux dom0 and linux domU from source
> with linux  2.6.18.8 as linux kernel.
>
> I do the following steps, which seem logical to me (because that is
> how things worked for me with Xen 3.0.4)
>
> 1. extract 3.1 source tarball
>
> 2. edit buildconfigs/mk.linux-2.6-xen to reflect chanage in kernel
> version to 2.6.18.8.
>
> 3. run 'make linux-2.6-xen0-config config=menuconfig'
>
> 4. run 'make dist KERNELS="linux-2.6-xen0" and instead of a clan
> build, I end up with this  error:
>
> /usr/src/xen-3.1.0-src/linux-2.6.18.8-xen/arch/i386/kernel/head-xen.S:4:27:
> error: linux/elfnote.h: No such file or directory
> make[6]: *** [arch/i386/kernel/head-xen.o] Error 1
> make[5]: *** [arch/i386/kernel] Error 2
> make[4]: *** [vmlinuz] Error 2
> make[3]: *** [vmlinuz] Error 2
> make[3]: Leaving directory
> `/usr/src/xen-3.1.0-src/build-linux-2.6.18.8-xen_x86_32'
> make[2]: *** [build] Error 2
> make[2]: Leaving directory `/usr/src/xen-3.1.0-src'
> make[1]: *** [linux-2.6-xen-install] Error 2
> make[1]: Leaving directory `/usr/src/xen-3.1.0-src'
> make: *** [install-kernels] Error 1
>
> Can someone tell me:
>
> a) if there is a limit as to which 2.6.18.x kernels I can build?
>
> b) HOW the build process changed form the one in Xen 3.0.x?
>
> c) what are the dependencies for building Xen 3.1 from source?
>
> d) is there is a documented build from source process and if so where?
>
> NOTE: the link on xen.org howto section to a page entitled "The
> Perfect Xen 3.1.0 Setup For Debian Etch (i386)" seems of no use. The
> process detailed in there produces the same error.
>
> ANY help is welcome
>
> Tomasz
>
>   
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users