Xen users - Jul 2008 - Still un-answered: How-To build Xen (3.2) to override XenSource''s linux-kernel (2.6.18) with a xenified kernel (your own or distribution)

Hello, 
 
I can say that I have searched the entire ''world wide web'' and
still haven''t found ''complete  and clear answers'' to
the often asked question of:
Given a Xen (release) build (say 3.2.0), which by default tries to get and build
and assume Linux kernel-xen 2.6.18 from the mercurial repository, HOW TO
override the build and make it work with a ''different''
xenified Linux source tree (kernel-xen) say Fedora Core 8 kernel-xen
2.6.23.7-3.fc8-xen.src.rpm
 
I have seen all the discussions on this topic but there are no complete and
clear answers (many of them even digress from the main point and asnwer partial
question!).
Some past threads are:
Re: [Xen-devel] building xen without mercury repository access
http://lists.xensource.com/archives/html/xen-devel/2008-02/msg00250.html
Re: [Xen-users] Howto compiling Xen 3.2 on Debian/Ubuntu (was: Compiling
Xen-3.2.0)
http://lists.xensource.com/archives/html/xen-users/2008-01/msg00699.html

I am able to build with the default XenSource'' xenified Linux kernel
2.6.18 (although there are some booting issues and xend fails).
What I (and many) want to know is, how to build the same Xen 3.2.x from source,
but make it use (or point to) a different xenified Linux kernel-xen, say with
the Fedora Core 8''s xenified Linux
kernel-xen-2.6-2.6.21.7-3.fc8.src.rpm, instead of using the default tarball
(XenSource'' xenified Linux kernel 2.6.18).
Note: Now I don''t know how to make a tarball from this FC8 rpm though;
appriciate any help on that too).
 
Here is what I have tied:
Method #1: (and a few variations of this)
- Get Xen 3.2.x source tarball and get it to build properly first with default
linux-2.6.18 (from mercurial).
- Parallel to Xen-3.2.x (same parent) create linux-2.6.23.7-3.fc8-xen source
tree from Fedora Core 8 repository.
- Now either edit Makefile or export to set variable
KERNELS=linux-2.6.23.7-3.fc8
- make clean
- make world
RESULT: It still builds the same old linux-2.6.18 stuff.
 
Method #2:
- In addition to the KERNELS=linux-2.6.23.7-3.fc8, I also tried re-creating the
symbolic link in the Xen-3.2.0 directory ''linux-2.6.18'' to
(wrongly) point to the linux-2.6.23.7-3.fc8 source tree.
RESULT: the link got re-created back to point at the original linux-2.6.18
during ''make world''.
 
Any clear and complete instructions would be highly appriciated.  (The README in
the Xen source tarball is also not sufficient or complete).
 
PS: I am not a expert but an intermediate level user in linux/kernel builds,
etc.  Prefer instructions spelled out step-by-step.
 
-Thanks and regards,
Jithendra B
 

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

On Sun, Jul 6, 2008 at 6:22 PM, Jithendra Bethur <bcj01@yahoo.com> wrote:
> Hello,
>
>
>
> I can say that I have searched the entire ''world wide
web'' and still
> haven''t found ''complete  and clear answers'' to
the often asked question of:
>
> Given a Xen (release) build (say 3.2.0), which by default tries to get and
> build and assume Linux kernel-xen 2.6.18 from the mercurial repository, HOW
> TO override the build and make it work with a ''different''
xenified Linux
> source tree (kernel-xen) say Fedora Core 8 kernel-xen
> 2.6.23.7-3.fc8-xen.src.rpm
>
>
>
> I have seen all the discussions on this topic but there are no complete and
> clear answers (many of them even digress from the main point and asnwer
> partial question!).
>
> Some past threads are:
>
> Re: [Xen-devel] building xen without mercury repository access
> http://lists.xensource.com/archives/html/xen-devel/2008-02/msg00250.html
>
> Re: [Xen-users] Howto compiling Xen 3.2 on Debian/Ubuntu (was: Compiling
> Xen-3.2.0)
> http://lists.xensource.com/archives/html/xen-users/2008-01/msg00699.html
>
> I am able to build with the default XenSource'' xenified Linux
kernel 2.6.18
> (although there are some booting issues and xend fails).
>
> What I (and many) want to know is, how to build the same Xen 3.2.x from
> source, but make it use (or point to) a different xenified Linux
kernel-xen,
> say with the Fedora Core 8''s xenified Linux
> kernel-xen-2.6-2.6.21.7-3.fc8.src.rpm, instead of using the default tarball
> (XenSource'' xenified Linux kernel 2.6.18).
>
> Note: Now I don''t know how to make a tarball from this FC8 rpm
though;
> appriciate any help on that too).
>
>
>
> Here is what I have tied:
>
> *Method #1: (and a few variations of this)*
>
> - Get Xen 3.2.x source tarball and get it to build properly first with
> default linux-2.6.18 (from mercurial).
>
> - Parallel to Xen-3.2.x (same parent) create linux-2.6.23.7-3.fc8-xen
> source tree from Fedora Core 8 repository.
>
> - Now either edit Makefile or export to set variable
> KERNELS=linux-2.6.23.7-3.fc8
>
> - make clean
>
> - make world
>
> RESULT: It still builds the same old linux-2.6.18 stuff.
>
>
>
> Method #2:
>
> - In addition to the KERNELS=linux-2.6.23.7-3.fc8, I also tried re-creating
> the symbolic link in the Xen-3.2.0 directory
''linux-2.6.18'' to (wrongly)
> point to the linux-2.6.23.7-3.fc8 source tree.
>
> RESULT: the link got re-created back to point at the original linux-2.6.18
> during ''make world''.
>
>
>
> Any clear and complete instructions would be highly appriciated.  (The
> README in the Xen source tarball is also not sufficient or complete).
>
>
>

For this method #2, I have had luck getting it to work by changing the file
<xen tree>/buildconfigs/src.hg-clone

you just need to change that file to be:

# Mercurial
HG ?= hg

LINUX_SRCDIR ?= linux-$(LINUX_VER)-xen.hg

# Repository to clone.
XEN_LINUX_HGREPO ?= $$(sh buildconfigs/select-repository $(LINUX_SRCDIR)
$(LINUX_SRC_PATH))

# Set XEN_LINUX_HGREV to update to a particlar revision.
XEN_LINUX_HGREV  ?= tip

$(LINUX_SRCDIR)/.valid-src: $(__XEN_LINUX_UPDATE)
    ln -snf ../linux-2.6.18-xen-3.2.0 linux-2.6.18-xen.hg
    touch $@

A reference for this:
http://xen.markmail.org/search/?q=building+3.2.1#query:building3.2.1+page:1+mid:nqzv32jhed3uvqto+state:results

Hope that helps.

Cheers,
Todd

PS: I am not a expert but an intermediate level user in linux/kernel
builds,
> etc.  Prefer instructions spelled out step-by-step.
>
>
>
> -Thanks and regards,
>
> Jithendra B
>
>
>
> _______________________________________________
> Xen-users mailing list
> Xen-users@lists.xensource.com
> http://lists.xensource.com/xen-users
>


-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com


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

On Sun, Jul 6, 2008 at 6:55 PM, Todd Deshane <deshantm@gmail.com> wrote:
>
>
> On Sun, Jul 6, 2008 at 6:22 PM, Jithendra Bethur <bcj01@yahoo.com>
wrote:
>
>>  Hello,
>>
>>
>>
>> I can say that I have searched the entire ''world wide
web'' and still
>> haven''t found ''complete  and clear answers''
to the often asked question of:
>>
>> Given a Xen (release) build (say 3.2.0), which by default tries to get
and
>> build and assume Linux kernel-xen 2.6.18 from the mercurial repository,
HOW
>> TO override the build and make it work with a
''different'' xenified Linux
>> source tree (kernel-xen) say Fedora Core 8 kernel-xen
>> 2.6.23.7-3.fc8-xen.src.rpm
>>
>>
>>
>> I have seen all the discussions on this topic but there are no complete
>> and clear answers (many of them even digress from the main point and
asnwer
>> partial question!).
>>
>> Some past threads are:
>>
>> Re: [Xen-devel] building xen without mercury repository access
>>
http://lists.xensource.com/archives/html/xen-devel/2008-02/msg00250.html
>>
>> Re: [Xen-users] Howto compiling Xen 3.2 on Debian/Ubuntu (was:
Compiling
>> Xen-3.2.0)
>>
http://lists.xensource.com/archives/html/xen-users/2008-01/msg00699.html
>>
>> I am able to build with the default XenSource'' xenified Linux
kernel
>> 2.6.18 (although there are some booting issues and xend fails).
>>
>> What I (and many) want to know is, how to build the same Xen 3.2.x from
>> source, but make it use (or point to) a different xenified Linux
kernel-xen,
>> say with the Fedora Core 8''s xenified Linux
>> kernel-xen-2.6-2.6.21.7-3.fc8.src.rpm, instead of using the default
tarball
>> (XenSource'' xenified Linux kernel 2.6.18).
>>
>> Note: Now I don''t know how to make a tarball from this FC8 rpm
though;
>> appriciate any help on that too).
>>
>>
>>
>> Here is what I have tied:
>>
>> *Method #1: (and a few variations of this)*
>>
>> - Get Xen 3.2.x source tarball and get it to build properly first with
>> default linux-2.6.18 (from mercurial).
>>
>> - Parallel to Xen-3.2.x (same parent) create linux-2.6.23.7-3.fc8-xen
>> source tree from Fedora Core 8 repository.
>>
>> - Now either edit Makefile or export to set variable
>> KERNELS=linux-2.6.23.7-3.fc8
>>
>> - make clean
>>
>> - make world
>>
>> RESULT: It still builds the same old linux-2.6.18 stuff.
>>
>>
>>
>> Method #2:
>>
>> - In addition to the KERNELS=linux-2.6.23.7-3.fc8, I also tried
>> re-creating the symbolic link in the Xen-3.2.0 directory
''linux-2.6.18'' to
>> (wrongly) point to the linux-2.6.23.7-3.fc8 source tree.
>>
>> RESULT: the link got re-created back to point at the original
linux-2.6.18
>> during ''make world''.
>>
>>
>>
>> Any clear and complete instructions would be highly appriciated.  (The
>> README in the Xen source tarball is also not sufficient or complete).
>>
>>
>>
>
>
> For this method #2, I have had luck getting it to work by changing the file
> <xen tree>/buildconfigs/src.hg-clone
>
> you just need to change that file to be:
>
> # Mercurial
> HG ?= hg
>
> LINUX_SRCDIR ?= linux-$(LINUX_VER)-xen.hg
>
> # Repository to clone.
> XEN_LINUX_HGREPO ?= $$(sh buildconfigs/select-repository $(LINUX_SRCDIR)
> $(LINUX_SRC_PATH))
>
> # Set XEN_LINUX_HGREV to update to a particlar revision.
> XEN_LINUX_HGREV  ?= tip
>
> $(LINUX_SRCDIR)/.valid-src: $(__XEN_LINUX_UPDATE)
>     ln -snf ../linux-2.6.18-xen-3.2.0 linux-2.6.18-xen.hg
>     touch $@
>
> A reference for this:
>
http://xen.markmail.org/search/?q=building+3.2.1#query:building3.2.1+page:1+mid:nqzv32jhed3uvqto+state:results
>
> Hope that helps.
>

Another thing you may want to look into:
http://wiki.xensource.com/xenwiki/XenParavirtOps

It is still a work in progress, but may have some of the features that you
are looking for. As this gets more mature, this is
how the standard Xen Linux kernel will work.

Cheers,
Todd



>
>
>  PS: I am not a expert but an intermediate level user in linux/kernel
>> builds, etc.  Prefer instructions spelled out step-by-step.
>>
>>
>>
>> -Thanks and regards,
>>
>> Jithendra B
>>
>>
>>
>> _______________________________________________
>> Xen-users mailing list
>> Xen-users@lists.xensource.com
>> http://lists.xensource.com/xen-users
>>
>
>
>
> --
> Todd Deshane
> http://todddeshane.net
> check out our book: http://runningxen.com



-- 
Todd Deshane
http://todddeshane.net
check out our book: http://runningxen.com


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

> Method #2:
>
> - In addition to the KERNELS=linux-2.6.23.7-3.fc8, I also tried re-creating
> the symbolic link in the Xen-3.2.0 directory
''linux-2.6.18'' to (wrongly)
> point to the linux-2.6.23.7-3.fc8 source tree.
>
> RESULT: the link got re-created back to point at the original linux-2.6.18
> during ''make world''.
>
>
>
> Any clear and complete instructions would be highly appriciated.  (The
> README in the Xen source tarball is also not sufficient or complete).
>
>
>
Hey Jitendra,

As Todd correctly pointed out - Xen tries to get a correct copy using
mercurial each time during the full build process. So just put your code or
a pointer to it in the linux-2.6.18 directory and comment appropriate lines
in buildconfigs/src.hg-clone. That worked for me as well.


> PS: I am not a expert but an intermediate level user in linux/kernel
> builds, etc.  Prefer instructions spelled out step-by-step.
>
>
>
Here ==> http://pastie.org/228729  is my src.hg-clone file that works.

Regards,
Asim


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

On Sun, 2008-07-06 at 15:22 -0700, Jithendra Bethur
wrote:
> Hello, 
> 
> I can say that I have searched the entire ''world wide
web'' and still
> haven''t found ''complete  and clear answers'' to
the often asked
> question of:
> 
> Given a Xen (release) build (say 3.2.0), which by default tries to get
> and build and assume Linux kernel-xen 2.6.18 from the mercurial
> repository, HOW TO override the build and make it work with a
> ''different'' xenified Linux source tree (kernel-xen) say
Fedora Core 8
> kernel-xen 2.6.23.7-3.fc8-xen.src.rpm
If you are using a pre-patched kernel from a distribution, your better
off building that independently from Xen. Why not just build the
Hypervisor and tools while skipping the kernel?

make XEN_TARGET_ARCH=arch xen
make XEN_TARGET_ARCH=arch tools
make XEN_TARGET_ARCH=arch install-xen
make XEN_TARGET_ARCH=arch install-tools

... of course add docs to that if you want them.

Then build / configure your kernel outside of the Xen source tree, via
whatever means your packager provides.

I use Ubuntu''s Hardy and Intrepid kernel trees which (1) requires Git
and (2) uses the debuild / debian helpers.. its very impractical to try
to include it in the Xen build because many extra steps are needed.

You will still easily be able to produce .deb / .rpm packages of your
own if you use the ''checkinstall'' utility or something
similar.

Regards,
--Tim




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

On Mon, 2008-07-07 at 11:50 +0800, Tim Post wrote:
> You will still easily be able to produce .deb / .rpm packages of your
> own if you use the ''checkinstall'' utility or something
similar.
Please do not use checkinstall; it generates debs which do not pass
policy checks.

William


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

On Mon, 2008-07-07 at 00:11 -0500, William Pitcock
wrote:
> On Mon, 2008-07-07 at 11:50 +0800, Tim Post wrote:
> > You will still easily be able to produce .deb / .rpm packages of your
> > own if you use the ''checkinstall'' utility or
something similar.
> 
> Please do not use checkinstall; it generates debs which do not pass
> policy checks.
> 
> William
A lot of things can go wrong with checkinstall, such as a statically
linked ''ln'' or others, since checkinstall relies on
installwatch. I
should amend, do not use checkinstall for things that you plan to widely
distribute :) If you need to make a .deb / .rpm to clone your
installation on your own stuff its (usually) fine.

Also do not use it to replace Debian (proper) package names. For
instance, if you hope to make a replacement for ''coreutils'',
name the
package something else and take the original out of apt''s reach.

I would not go as far as to say ''just don''t use it'',
as it is a very
useful tool. If you want to set up your own trivial repository for your
company or friends to use, its fine.

Regards,
--Tim




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

Progress/Update and a new-sub-question!
 
Thanks to all for your quick and accurate response.  I was able to build Xen 3.2
AND override the linux kernel-xen pointer by modifying the
buildconfigs/src.hg-clone.  I will shortly post a detailed full instructions for
other (Fedora core) users.
 
Sub-Question: As Tim Post suggested, I was able to build the linux kernel
seperately and use that with Xen-kernel to successfully boot to Xen+Dom0.  But
just for completion sake, I tried to bulid the linux kernel from within
Xen-3.2.0 (by ''make prep-kernel'' AND ''copying
.config'' AND make world).  It almost completed the build 99% (I think)
and encountered the below error (while copying the vmlinux file to
...../arch/i386/boot/ directory).
--------- <<<< Begin: Build output (partial) with error
<<<<<< ---------------------------------
............
........
....
WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem_low
from .text between ''xen_machine_kexec_setup_resources'' (at
offset 0xc1151646) and ''xen_machine_kexec_load''
  OBJCOPY vmlinux-stripped
BFD: vmlinux-stripped: warning: allocated section `.notes'' not in
segment
  GZIP    vmlinuz
make[3]: Leaving directory
`/home/dev1/xen-build/xen-3.2.0/build-linux-2.6.18-xen_x86_32''
mkdir -p /home/dev1/xen-build/xen-3.2.0/dist/install/boot
cp build-linux-2.6.18-xen_x86_32/arch/i386/boot/vmlinuz
/home/dev1/xen-build/xen-3.2.0/dist/install/boot/vmlinuz-2.6.21.7-8096.fc8xen-xen
cp: cannot stat `build-linux-2.6.18-xen_x86_32/arch/i386/boot/vmlinuz'':
No such file or directory
make[2]: *** [build] Error 1
make[2]: Leaving directory `/home/dev1/xen-build/xen-3.2.0''
make[1]: *** [linux-2.6-xen-install] Error 2
make[1]: Leaving directory `/home/dev1/xen-build/xen-3.2.0''
make: *** [install-kernels] Error 1
--------- <<<< End: Build output (partial) with error
<<<<<< ---------------------------------
 
Why am I getting this:
cp: cannot stat `build-linux-2.6.18-xen_x86_32/arch/i386/boot/vmlinuz'':
No such file or directory
errror with cp?
 
I noticed that under the
''build-linux-2.6.18-xen_x86_32/arch/i386''  directory there was
really no boot/ directory.  Rather there was a boot-xen/ directory (along with
other directories like crypto, kernel, lib, mach-xen etc).  The destination
dist/install/boot existed.
 
Why would the .....arch/i386/boot directory be missing.
PS: This may well be Fedora Core specific (in which case we may drop it at this
if inappropriate)
 
-regards,
Jithendra B


--- On Sun, 7/6/08, Tim Post <echo@echoreply.us> wrote:

From: Tim Post <echo@echoreply.us>
Subject: Re: [Xen-users] Still un-answered: How-To build Xen (3.2) to override
XenSource''s linux-kernel (2.6.18) with a xenified kernel (your own or
distribution)
To: "Jithendra Bethur" <bcj01@yahoo.com>
Cc: xen-users@lists.xensource.com
Date: Sunday, July 6, 2008, 8:50 PM

On Sun, 2008-07-06 at 15:22 -0700, Jithendra Bethur
wrote:
> Hello, 
> 
> I can say that I have searched the entire ''world wide
web'' and
still
> haven''t found ''complete  and clear answers'' to
the often asked
> question of:
> 
> Given a Xen (release) build (say 3.2.0), which by default tries to get
> and build and assume Linux kernel-xen 2.6.18 from the mercurial
> repository, HOW TO override the build and make it work with a
> ''different'' xenified Linux source tree (kernel-xen) say
Fedora
Core 8
> kernel-xen 2.6.23.7-3.fc8-xen.src.rpm
If you are using a pre-patched kernel from a distribution, your better
off building that independently from Xen. Why not just build the
Hypervisor and tools while skipping the kernel?

make XEN_TARGET_ARCH=arch xen
make XEN_TARGET_ARCH=arch tools
make XEN_TARGET_ARCH=arch install-xen
make XEN_TARGET_ARCH=arch install-tools

... of course add docs to that if you want them.

Then build / configure your kernel outside of the Xen source tree, via
whatever means your packager provides.

I use Ubuntu''s Hardy and Intrepid kernel trees which (1) requires Git
and (2) uses the debuild / debian helpers.. its very impractical to try
to include it in the Xen build because many extra steps are needed.

You will still easily be able to produce .deb / .rpm packages of your
own if you use the ''checkinstall'' utility or something
similar.

Regards,
--Tim[Jithendra B] Minor correction in the original post (to help searches
resulting from this keywords!).For the Fedora Core kernel-xen package revision,
I mistakenly typed "kernel-xen 2.6.23.7-3.fc8-xen.src.rpm" when I
meant to type "> kernel-xen 2.6.21.7-3.fc8-xen.src.rpm"(it is .21
and not .23) 

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

PS: Correction in my mail below
 
........(by ''make prep-kernel'' AND ''copying
.config'' AND make world)
SHOULD READ
........(by ''make prep-kernel'' AND ''copying
.config'' AND make dist).
 
(I did ''make dist'' and not ''make world'' to
build the linux-kernel from within xen-3.2.0 directory).
 
-regards,
Jithendra B
 

--- On Tue, 7/8/08, Jithendra Bethur <bcj01@yahoo.com> wrote:

From: Jithendra Bethur <bcj01@yahoo.com>
Subject: Re: [Xen-users] Still un-answered: How-To build Xen (3.2) to override
XenSource''s linux-kernel (2.6.18) with a xenified kernel (your own or
distribution)
To: xen-users@lists.xensource.com
Date: Tuesday, July 8, 2008, 4:43 AM







Progress/Update and a new-sub-question!
 
Thanks to all for your quick and accurate response.  I was able to build Xen 3.2
AND override the linux kernel-xen pointer by modifying the
buildconfigs/src.hg-clone.  I will shortly post a detailed full instructions for
other (Fedora core) users.
 
Sub-Question: As Tim Post suggested, I was able to build the linux kernel
seperately and use that with Xen-kernel to successfully boot to Xen+Dom0.  But
just for completion sake, I tried to bulid the linux kernel from within
Xen-3.2.0 (by ''make prep-kernel'' AND ''copying
.config'' AND make world).  It almost completed the build 99% (I think)
and encountered the below error (while copying the vmlinux file to
...../arch/i386/boot/ directory).
--------- <<<< Begin: Build output (partial) with error
<<<<<< ---------------------------------
............
........
....
WARNING: vmlinux - Section mismatch: reference to .init.text:__alloc_bootmem_low
from .text between ''xen_machine_kexec_setup_resources'' (at
offset 0xc1151646) and ''xen_machine_kexec_load''
  OBJCOPY vmlinux-stripped
BFD: vmlinux-stripped: warning: allocated section `.notes'' not in
segment
  GZIP    vmlinuz
make[3]: Leaving directory
`/home/dev1/xen-build/xen-3.2.0/build-linux-2.6.18-xen_x86_32''
mkdir -p /home/dev1/xen-build/xen-3.2.0/dist/install/boot
cp build-linux-2.6.18-xen_x86_32/arch/i386/boot/vmlinuz
/home/dev1/xen-build/xen-3.2.0/dist/install/boot/vmlinuz-2.6.21.7-8096.fc8xen-xen
cp: cannot stat `build-linux-2.6.18-xen_x86_32/arch/i386/boot/vmlinuz'':
No such file or directory
make[2]: *** [build] Error 1
make[2]: Leaving directory `/home/dev1/xen-build/xen-3.2.0''
make[1]: *** [linux-2.6-xen-install] Error 2
make[1]: Leaving directory `/home/dev1/xen-build/xen-3.2.0''
make: *** [install-kernels] Error 1
--------- <<<< End: Build output (partial) with error
<<<<<< ---------------------------------
 
Why am I getting this:
cp: cannot stat `build-linux-2.6.18-xen_x86_32/arch/i386/boot/vmlinuz'':
No such file or directory
errror with cp?
 
I noticed that under the
''build-linux-2.6.18-xen_x86_32/arch/i386''  directory there was
really no boot/ directory.  Rather there was a boot-xen/ directory (along with
other directories like crypto, kernel, lib, mach-xen etc).  The destination
dist/install/boot existed.
 
Why would the .....arch/i386/boot directory be missing.
PS: This may well be Fedora Core specific (in which case we may drop it at this
if inappropriate)
 
-regards,
Jithendra B


--- On Sun, 7/6/08, Tim Post <echo@echoreply.us> wrote:

From: Tim Post <echo@echoreply.us>
Subject: Re: [Xen-users] Still un-answered: How-To build Xen (3.2) to override
XenSource''s linux-kernel (2.6.18) with a xenified kernel (your own or
distribution)
To: "Jithendra Bethur" <bcj01@yahoo.com>
Cc: xen-users@lists.xensource.com
Date: Sunday, July 6, 2008, 8:50 PM

On Sun, 2008-07-06 at 15:22 -0700, Jithendra Bethur
wrote:
> Hello, 
> 
> I can say that I have searched the entire ''world wide
web'' and
still
> haven''t found ''complete  and clear answers'' to
the often asked
> question of:
> 
> Given a Xen (release) build (say 3.2.0), which by default tries to get
> and build and assume Linux kernel-xen 2.6.18 from the mercurial
> repository, HOW TO override the build and make it work with a
> ''different'' xenified Linux source tree (kernel-xen) say
Fedora
Core 8
> kernel-xen 2.6.23.7-3.fc8-xen.src.rpm
If you are using a pre-patched kernel from a distribution, your better
off building that independently from Xen. Why not just build the
Hypervisor and tools while skipping the kernel?

make XEN_TARGET_ARCH=arch xen
make XEN_TARGET_ARCH=arch tools
make XEN_TARGET_ARCH=arch install-xen
make XEN_TARGET_ARCH=arch install-tools

... of course add docs to that if you want them.

Then build / configure your kernel outside of the Xen source tree, via
whatever means your packager provides.

I use Ubuntu''s Hardy and Intrepid kernel trees which (1) requires Git
and (2) uses the debuild / debian helpers.. its very impractical to try
to include it in the Xen build because many extra steps are needed.

You will still easily be able to produce .deb / .rpm packages of your
own if you use the ''checkinstall'' utility or something
similar.

Regards,
--Tim[Jithendra B] Minor correction in the original post (to help searches
resulting from this keywords!).For the Fedora Core kernel-xen package revision,
I mistakenly typed "kernel-xen 2.6.23.7-3.fc8-xen.src.rpm" when I
meant to type "> kernel-xen 2.6.21.7-3.fc8-xen.src.rpm"(it is .21
and not .23) 

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