how to build xen kernel?

I looked at NetBSD/Xen howto but don't see how to build my
own custom 
kernel.

(Something changed and even though I used the PF module for
two weeks I 
can't use it any more.)

I copied sys/arch/i386/conf/XEN2_DOMU to
sys/arch/i386/conf/XEN2_DOMU_PF.

(I am using XEN2 since I am currently using XENU.)

Then I ran:

./build.sh -m xen -a i386 tools kernel=XEN2_DOMU_PF 

It failed after building tools with:

===> Tools built to
/usr/src/netbsd-3/src/obj/tooldir.NetBSD-3.99.21-i386
===> Building kernel:  XEN2_DOMU_PF
===> Build directory:  
/usr/src/netbsd-3/src/sys/arch/xen/compile/obj/XEN2_DOMU_PF
rm -f a.out [Ee]rrs mklog core *.core .gdbinit 
config: cannot read
/usr/src/netbsd-3/src/sys/arch/xen/conf/XEN2_DOMU_PF: 
No such file or directory

ERROR: nbconfig failed for XEN2_DOMU_PF
*** BUILD ABORTED ***

I see it is using wrong directory above.

What is correct way to build NetBSD/Xen kernels?

Am I not supposed to use "-m xen"?

How does the release team build them?

Thanks,

Jeremy C. Reed

p.s. Once I figure this out, I can add to the NetBSD/Xen
howto.

On Wed, Jul 26, 2006 at 02:21:49PM -0500, reedreedmedia.net wrote:
> 
The three virtues of a programmer are impatience, hubris,
and sloth
> I copied sys/arch/i386/conf/XEN2_DOMU to
sys/arch/i386/conf/XEN2_DOMU_PF.
> 
> ./build.sh -m xen -a i386 tools kernel=XEN2_DOMU_PF 
Insufficient sloth.
> 
> It failed after building tools with:
> 
> ===> Tools built to
/usr/src/netbsd-3/src/obj/tooldir.NetBSD-3.99.21-i386
> ===> Building kernel:  XEN2_DOMU_PF
> ===> Build directory:  
>
/usr/src/netbsd-3/src/sys/arch/xen/compile/obj/XEN2_DOMU_PF
> rm -f a.out [Ee]rrs mklog core *.core .gdbinit 
> config: cannot read
/usr/src/netbsd-3/src/sys/arch/xen/conf/XEN2_DOMU_PF: 

See the directory that changed because you exhibited
insufficient sloth?

-- 
Chris Dukes
"The key to effective management is properly timed
hovering."

Hi Jeremy,

I don't know if this can help, but when I compile a kernel
I perform  
these steps :
( my directory containing "src" &
"xsrc" is /CROSSCOMP/BUILD/ )

-1- Build the toolchain :
./build.sh -N 1 -j 3 -m i386 -O /CROSSCOMP/BUILD/obj.i386 -T
/ 
CROSSCOMP/BUILD/tools.i386 -D /CROSSCOM
P/BUILD/dest.i386 -R /CROSSCOMP/BUILD/release.i386 -X
/CROSSCOMP/ 
BUILD/xsrc -U -x tools

-2- Build the Kernel :
./build.sh -N 1 -j 3 -m i386 -O /CROSSCOMP/BUILD/obj.i386 -T
/ 
CROSSCOMP/BUILD/tools.i386 -D /CROSSCOM
P/BUILD/dest.i386 -R /CROSSCOMP/BUILD/release.i386 -X
/CROSSCOMP/ 
BUILD/xsrc -U -x -u kernel=MYKERNEL

I'm not sure you could both use "tools" &
"kernel" on the same  
command line ...

But I haven't tested to compile for ARCH XEN. I only know
it works  
perfectly with i386 / amd64 / sparc64 / macppc ( I tested it
)

Best Regards,

Arnaud.

Le 26 juil. 06 à 21:21, reedreedmedia.net a écrit :

> I looked at NetBSD/Xen howto but don't see how to
build my own custom
> kernel.
>
> (Something changed and even though I used the PF module
for two  
> weeks I
> can't use it any more.)
>
> I copied sys/arch/i386/conf/XEN2_DOMU to
sys/arch/i386/conf/ 
> XEN2_DOMU_PF.
>
> (I am using XEN2 since I am currently using XENU.)
>
> Then I ran:
>
> ./build.sh -m xen -a i386 tools kernel=XEN2_DOMU_PF
>
> It failed after building tools with:
>
> ===> Tools built to /usr/src/netbsd-3/src/obj/ 
> tooldir.NetBSD-3.99.21-i386
> ===> Building kernel:  XEN2_DOMU_PF
> ===> Build directory:
>
/usr/src/netbsd-3/src/sys/arch/xen/compile/obj/XEN2_DOMU_PF
> rm -f a.out [Ee]rrs mklog core *.core .gdbinit
> config: cannot read
/usr/src/netbsd-3/src/sys/arch/xen/conf/ 
> XEN2_DOMU_PF:
> No such file or directory
>
> ERROR: nbconfig failed for XEN2_DOMU_PF
> *** BUILD ABORTED ***
>
> I see it is using wrong directory above.
>
> What is correct way to build NetBSD/Xen kernels?
>
> Am I not supposed to use "-m xen"?
>
> How does the release team build them?
>
> Thanks,
>
> Jeremy C. Reed
>
> p.s. Once I figure this out, I can add to the
NetBSD/Xen howto.
>

> See the directory that changed because you exhibited
insufficient sloth?

I am not sure if you are joking because you didn't read the
line that 
indicated that I know it used the wrong directory.

That still doesn't tell me where the documentation for this
is at.

Am I supposed to manually copy the config to that location?
Why?

Or should I use a path for the build.sh kernel= setting?

Why aren't the Xen kernel configs there in the first place
then?

Is it required to use -m switch?

How do the release engineers do it?

On Wed, Jul 26, 2006 at 02:41:14PM -0500, reedreedmedia.net wrote:
> > See the directory that changed because you
exhibited insufficient sloth?
> 
> I am not sure if you are joking because you didn't
read the line that 
> indicated that I know it used the wrong directory.

You typed too much to begin with.
If you'd been lazy and typed the shortest possible command,
you would
not have seen this error.
Slightly different invocation if cross compiling.
> 
> That still doesn't tell me where the documentation for
this is at.

I went by the bit on building from CVS.
http://w
ww.netbsd.org/Documentation/current/
"Updating an existing system"
Picked the "GENERIC" kernel for Xen.
> 
> Am I supposed to manually copy the config to that
location? Why?
> 
> Or should I use a path for the build.sh kernel=
setting?

If you are not cross compiling (IE building on Linux of
FreeBSD),
limit it to just tools and kernel=.
If cross compiling, use the same parameters you'd use to
target
your base architecture (IE i386).

> 
> Why aren't the Xen kernel configs there in the first
place then?

Xen is a minor tweak and subset on the native instruction
set, it is not
a new instruction set.
I don't think it's there yet, but you could have ia64 xen
and powerpc xen.
> 
> Is it required to use -m switch?

Not unless doing cross compiling
> 
> How do the release engineers do it?

One would hope they follow something similar to the section
"Building a release from source"
from the same URL

-- 
Chris Dukes
"The key to effective management is properly timed
hovering."

On Wed, Jul 26, 2006 at 02:41:14PM -0500, reedreedmedia.net wrote:
> > See the directory that changed because you
exhibited insufficient sloth?
> 
> I am not sure if you are joking because you didn't
read the line that 
> indicated that I know it used the wrong directory.
> 
> That still doesn't tell me where the documentation for
this is at.
> 
> Am I supposed to manually copy the config to that
location? Why?
> 
> Or should I use a path for the build.sh kernel=
setting?
> 
> Why aren't the Xen kernel configs there in the first
place then?
> 
> Is it required to use -m switch?
> 
> How do the release engineers do it?

Just remplace xen with i386  Xen isn't
a different machine, just a few
things done differently in the kernel.

-- 
Manuel Bouyer <bouyerantioche.eu.org>
     NetBSD: 26 ans d'experience feront toujours la
difference
--

On Wed, Jul 26, 2006 at 02:21:49PM -0500, reedreedmedia.net wrote:
> 
The three virtues of a programmer are impatience, hubris,
and sloth
> I copied sys/arch/i386/conf/XEN2_DOMU to
sys/arch/i386/conf/XEN2_DOMU_PF.
> 
> ./build.sh -m xen -a i386 tools kernel=XEN2_DOMU_PF 
Insufficient sloth.
> 
> It failed after building tools with:
> 
> ===> Tools built to
/usr/src/netbsd-3/src/obj/tooldir.NetBSD-3.99.21-i386
> ===> Building kernel:  XEN2_DOMU_PF
> ===> Build directory:  
>
/usr/src/netbsd-3/src/sys/arch/xen/compile/obj/XEN2_DOMU_PF
> rm -f a.out [Ee]rrs mklog core *.core .gdbinit 
> config: cannot read
/usr/src/netbsd-3/src/sys/arch/xen/conf/XEN2_DOMU_PF: 

See the directory that changed because you exhibited
insufficient sloth?

-- 
Chris Dukes
"The key to effective management is properly timed
hovering."

Hi Jeremy,

I don't know if this can help, but when I compile a kernel
I perform  
these steps :
( my directory containing "src" &
"xsrc" is /CROSSCOMP/BUILD/ )

-1- Build the toolchain :
./build.sh -N 1 -j 3 -m i386 -O /CROSSCOMP/BUILD/obj.i386 -T
/ 
CROSSCOMP/BUILD/tools.i386 -D /CROSSCOM
P/BUILD/dest.i386 -R /CROSSCOMP/BUILD/release.i386 -X
/CROSSCOMP/ 
BUILD/xsrc -U -x tools

-2- Build the Kernel :
./build.sh -N 1 -j 3 -m i386 -O /CROSSCOMP/BUILD/obj.i386 -T
/ 
CROSSCOMP/BUILD/tools.i386 -D /CROSSCOM
P/BUILD/dest.i386 -R /CROSSCOMP/BUILD/release.i386 -X
/CROSSCOMP/ 
BUILD/xsrc -U -x -u kernel=MYKERNEL

I'm not sure you could both use "tools" &
"kernel" on the same  
command line ...

But I haven't tested to compile for ARCH XEN. I only know
it works  
perfectly with i386 / amd64 / sparc64 / macppc ( I tested it
)

Best Regards,

Arnaud.

Le 26 juil. 06 à 21:21, reedreedmedia.net a écrit :

> I looked at NetBSD/Xen howto but don't see how to
build my own custom
> kernel.
>
> (Something changed and even though I used the PF module
for two  
> weeks I
> can't use it any more.)
>
> I copied sys/arch/i386/conf/XEN2_DOMU to
sys/arch/i386/conf/ 
> XEN2_DOMU_PF.
>
> (I am using XEN2 since I am currently using XENU.)
>
> Then I ran:
>
> ./build.sh -m xen -a i386 tools kernel=XEN2_DOMU_PF
>
> It failed after building tools with:
>
> ===> Tools built to /usr/src/netbsd-3/src/obj/ 
> tooldir.NetBSD-3.99.21-i386
> ===> Building kernel:  XEN2_DOMU_PF
> ===> Build directory:
>
/usr/src/netbsd-3/src/sys/arch/xen/compile/obj/XEN2_DOMU_PF
> rm -f a.out [Ee]rrs mklog core *.core .gdbinit
> config: cannot read
/usr/src/netbsd-3/src/sys/arch/xen/conf/ 
> XEN2_DOMU_PF:
> No such file or directory
>
> ERROR: nbconfig failed for XEN2_DOMU_PF
> *** BUILD ABORTED ***
>
> I see it is using wrong directory above.
>
> What is correct way to build NetBSD/Xen kernels?
>
> Am I not supposed to use "-m xen"?
>
> How does the release team build them?
>
> Thanks,
>
> Jeremy C. Reed
>
> p.s. Once I figure this out, I can add to the
NetBSD/Xen howto.
>

> See the directory that changed because you exhibited
insufficient sloth?

I am not sure if you are joking because you didn't read the
line that 
indicated that I know it used the wrong directory.

That still doesn't tell me where the documentation for this
is at.

Am I supposed to manually copy the config to that location?
Why?

Or should I use a path for the build.sh kernel= setting?

Why aren't the Xen kernel configs there in the first place
then?

Is it required to use -m switch?

How do the release engineers do it?

On Wed, Jul 26, 2006 at 02:41:14PM -0500, reedreedmedia.net wrote:
> > See the directory that changed because you
exhibited insufficient sloth?
> 
> I am not sure if you are joking because you didn't
read the line that 
> indicated that I know it used the wrong directory.

You typed too much to begin with.
If you'd been lazy and typed the shortest possible command,
you would
not have seen this error.
Slightly different invocation if cross compiling.
> 
> That still doesn't tell me where the documentation for
this is at.

I went by the bit on building from CVS.
http://w
ww.netbsd.org/Documentation/current/
"Updating an existing system"
Picked the "GENERIC" kernel for Xen.
> 
> Am I supposed to manually copy the config to that
location? Why?
> 
> Or should I use a path for the build.sh kernel=
setting?

If you are not cross compiling (IE building on Linux of
FreeBSD),
limit it to just tools and kernel=.
If cross compiling, use the same parameters you'd use to
target
your base architecture (IE i386).

> 
> Why aren't the Xen kernel configs there in the first
place then?

Xen is a minor tweak and subset on the native instruction
set, it is not
a new instruction set.
I don't think it's there yet, but you could have ia64 xen
and powerpc xen.
> 
> Is it required to use -m switch?

Not unless doing cross compiling
> 
> How do the release engineers do it?

One would hope they follow something similar to the section
"Building a release from source"
from the same URL

-- 
Chris Dukes
"The key to effective management is properly timed
hovering."