This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] Xen and make-kpkg

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-users] Xen and make-kpkg
From: Niki Hammler <mailinglists@xxxxxxxxx>
Date: Sun, 10 Sep 2006 21:25:51 +0200
Delivery-date: Mon, 11 Sep 2006 03:13:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx

In my dom0 system (Debian sarge, minimal) I've installed Xen with
backports from sid/etch as described in [1].

But in my domU systems I want and need specialiced kernels. The best
would be to just patch those (existing!) kernel sources with Xen and
recompile. But it doesn't seem to be so simple...

If I'd use the same kernel (as produced with make world from xen-source)
for each domU system, I don't understand the sense of Xen, then I could
also use OpenVZ. The great thing about Xen in my opinion is that I can
choose different kernels for each system.

However, for one domU system (debian sarge), I try to create a
specialized kernel the debian-way with:

1.) replace LINUX_VER in buildconfigs/mk.linux-2.6-xen with ""
to use the *latest* 2.6.16 kernel from kernel.org (I've tried 2.6.17 -
they don't work :-(

2.) decompress the kernel tree and apply xen patches
$ make prep-kernels

3.) Configure the kernel/add patches, e.g.
$ cd linux-
$ patch [...]
$ cp [...] .config
$ make oldconfig
$ make menuconfig

4.) Try to build a debian package:
$ make-kpkg --revision= --initrd kernel_image

But this step throws errors :-(

if [ -r System.map -a -x /sbin/depmod ]; then /sbin/depmod -ae -F
System.map -b
/mnt/.temp/Xen/xen-3.0.2-2/linux- -r; fi
make[2]: Leaving directory `/mnt/.temp/Xen/xen-3.0.2-2/linux-'
test ! -e debian/tmp-image/lib/modules/ ||
   mv debian/tmp-image/lib/modules/ ./debian/source-link
test ! -e debian/tmp-image/lib/modules/ ||
   mv debian/tmp-image/lib/modules/ ./debian/build-link
depmod -q -FSystem.map -b debian/tmp-image;
FATAL: Could not open 'System.map': No such file or directory
make[1]: [real_stamp_image] Error 1 (ignored)
test ! -e ./debian/source-link ||
   mv ./debian/source-link debian/tmp-image/lib/modules/
test ! -e  ./debian/build-link ||
   mv  ./debian/build-link debian/tmp-image/lib/modules/
cp arch/i386/boot/bzImage debian/tmp-image/boot/vmlinuz-
cp: cannot stat `arch/i386/boot/bzImage': No such file or directory
make[1]: *** [real_stamp_image] Error 1
make[1]: Leaving directory `/mnt/.temp/Xen/xen-3.0.2-2/linux-'
make: *** [kernel-image-deb] Error 2

Why isn't there a System.map and bzImage *after* compiling the kernel?
They should be in there in my opinion..

Is there a way to produce debian compliant kernel packages with xen patch?

I can't find much about this in google...is nobody interested to use Xen
on debian "the debian-way"?

Any help would be appreciated.

Thanks in advance,


[1] http://www.huschi.net/16_185_de.html

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Xen and make-kpkg, Niki Hammler <=