Hi, My apologies for posting this question on this list but I figured that the Debian aficionados on this list might be more familiar with the issue than the general Debian user. As for the question itself, it most likely will attest more to my lack of knowledge than any issue with Xen. Ok, here we go: How do I generate the source header files for a 2.6.11 kernel patched with Xen 2.0.6? Some background: I´m trying to compile a few special modules (ibmsmb, for the IBM Director Agent, and zaphfc, for HFC-based ISDN cards, in case anyone is interested) and their Makefiles assume the presence of kernel source header files in case they are build against a 2.6 kernel. That is, some meaningful code in /lib/modules/`uname -r`/build/include/linux... I´m using the unstable packages kernel-source-2.6.11 and the kernel-patch-xen to generate the source tree. I also copied the .config from the xen0 directory created when downloading the xen 2.0.6 source distribution. Trying to build a kernel package using make-kpkg --added patches=xen --config=menuconfig --arch=xen --subarch=xen --revision=xenserver.0.1 kernel-image works just fine (but I should admit that I haven´t tried that kernel) and generates a Debian kernel package in /usr/src. However trying the same with make-kpkg --added patches=xen --config=menuconfig --arch=xen --subarch=xen --revision=xenserver.0.1 kernel-image kernel_headers still generates only the kernel-package. Doing just a make-kpkg kernel_headers is successful in creating a kernel-headers package but I´m wondering if that´s then for the right architecture. At this point I´m well willing to do away with the luxury of Debian packages if only I could compile the darn modules. Hence the broad question about _any_ way to generate the header files. If there´s a neat way to generate a Debian package, that would be to good to be true. I should also mention that I´d appreciate any not so subtle hint what I´m missing here. Thanks in advance Olaf _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Some background: I´m trying to compile a few special modules (ibmsmb, > for the IBM Director Agent, and zaphfc, for HFC-based ISDN cards, in > case anyone is interested) and their Makefiles assume the presence of > kernel source header files in case they are build against a 2.6 > kernel. That is, some meaningful code in /lib/modules/`uname > -r`/build/include/linux.../lib/modules/`uname -r`/build is often just a symlink to wherever you built the kernel from and this is good enough for most uses, but if the machine you''re compiling on isn''t the machine you''re going to be running the kernel from, or if you want to get rid of your kernel sources, you really do need the kernel_headers package.> Trying to build a kernel package using > > make-kpkg --added patches=xen --config=menuconfig --arch=xen > --subarch=xen --revision=xenserver.0.1 kernel-image > > works just fineThat''s a surprise. Shouldn''t it be --added-patches instead of --added patches? I assume this is a typo in copying out the command to the mail, but if not, it looks like you have other things to worry about :-> Note that make-kpkg has other problems with Xen: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311004 Sorry I couldn''t be of more help, Daniel -- There may come a time The open palm of desire, When I will lose you, ]http://surreal.istic.org/[ The rose of Jericho, Lose you as I lose my sight, Soil as soft as Summer, Days falling backward into velvet night; The strength to let you go. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Some background: I´m trying to compile a few special modules (ibmsmb, > for the IBM Director Agent, and zaphfc, for HFC-based ISDN cards, in > case anyone is interested) and their Makefiles assume the presence of > kernel source header files in case they are build against a 2.6 > kernel. That is, some meaningful code in /lib/modules/`uname > -r`/build/include/linux.../lib/modules/`uname -r`/build is often just a symlink to wherever you built the kernel from and this is good enough for most uses, but if the machine you''re compiling on isn''t the machine you''re going to be running the kernel from, or if you want to get rid of your kernel sources, you really do need the kernel_headers package.> Trying to build a kernel package using > > make-kpkg --added patches=xen --config=menuconfig --arch=xen > --subarch=xen --revision=xenserver.0.1 kernel-image > > works just fineThat''s a surprise. Shouldn''t it be --added-patches instead of --added patches? I assume this is a typo in copying out the command to the mail, but if not, it looks like you have other things to worry about :-> Note that make-kpkg has other problems with Xen: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311004 Sorry I couldn''t be of more help, Daniel -- There may come a time The open palm of desire, When I will lose you, ]http://surreal.istic.org/[ The rose of Jericho, Lose you as I lose my sight, Soil as soft as Summer, Days falling backward into velvet night; The strength to let you go. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Olaf, Olaf wrote:> Hi, > > My apologies for posting this question on this list but I figured that > the Debian aficionados on this list might be more familiar with the > issue than the general Debian user. As for the question itself, it > most likely will attest more to my lack of knowledge than any issue > with Xen. > > Ok, here we go: How do I generate the source header files for a > 2.6.11 kernel patched with Xen 2.0.6? > > Some background: I´m trying to compile a few special modules (ibmsmb, > for the IBM Director Agent, and zaphfc, for HFC-based ISDN cards, in > case anyone is interested) and their Makefiles assume the presence of > kernel source header files in case they are build against a 2.6 > kernel. That is, some meaningful code in /lib/modules/`uname > -r`/build/include/linux... > > I´m using the unstable packages kernel-source-2.6.11 and the > kernel-patch-xen to generate the source tree. I also copied the > .config from the xen0 directory created when downloading the xen 2.0.6 > source distribution. Trying to build a kernel package using > > make-kpkg --added patches=xen --config=menuconfig --arch=xen > --subarch=xen --revision=xenserver.0.1 kernel-image > > works just fine (but I should admit that I haven´t tried that kernel) > and generates a Debian kernel package in /usr/src. However trying the > same with > > make-kpkg --added patches=xen --config=menuconfig --arch=xen > --subarch=xen --revision=xenserver.0.1 kernel-image kernel_headers > > still generates only the kernel-package. > > Doing just a > > make-kpkg kernel_headers > > is successful in creating a kernel-headers package but I´m wondering > if that´s then for the right architecture. > > At this point I´m well willing to do away with the luxury of Debian > packages if only I could compile the darn modules. Hence the broad > question about _any_ way to generate the header files. If there´s a > neat way to generate a Debian package, that would be to good to be > true. I should also mention that I´d appreciate any not so subtle hint > what I´m missing here. > > Thanks in advance > OlafI''ve been using Debian for my Xen, but I''m afraid I haven''t played with the idea of making packages yet. The way I''ve been doing it is - download and unpack the xen branch of choice (currently using testing), - install the appropriate kernel source using apt-get (ie. Debianised kernel source) - copy the source file into /usr/src/xen - do a ''make dist'' - cd to ./linux-2.6.xx-domU and do a ''make ARCH=xen menuconfig'' - repeat ''make dist'' - copy kernel/modules/... from ./dist/install/ to destination There''s probably a proper way of doing it, but this works for me. I actually use a number of different kernels depending on the task of the domU, so I''ve modified the KERNEL statement in my Makefile and added extra make scripts in ./buildconfigs for each kernel. Once I get my new Xen-based server going (I''ve decided the old one is too inefficient with both drive space and ram, etc) I too will be looking into make-kpkg to simplify (?) upgrades and maintenance. I''m not sure why your headers don''t build, but perhaps you could try: - kernel-headers instead of kernel_headers? (stab in dark:)) - remove the subarch stanza? (necessary?) - export ARCH as an environment variable before make? - OK, I''ve got no idea :) Marcus. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel Hulme schrieb:> Note that make-kpkg has other problems with Xen: > >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311004 > > >But it works fine without the initrd. I am running a xen0 kernel I have made using make-kpkg. Why should I need initrd? Dirk _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> >http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311004> But it works fine without the initrd. I am running a xen0 kernel I > have made using make-kpkg. Why should I need initrd?I am not suggesting you do, merely giving an example of make-kpkg and XenLinux not playing nice together. It seems unlikely that this is what is causing this problem, but I like to keep an open mind when diagnosing things that should not happen :-> -- Stop the infinite loop, I want to get off! http://surreal.istic.org/ Paraphernalia/Never hides your broken bones,/ And I don''t know why you''d want to try:/ It''s plain to see you''re on your own. -- Paul Simon The documentation that can be written is not the true documentation. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Sorry about the duplicate post, everyone. The ML has been a bit laggy for me in the last few days, and when I didn''t see my post I thought it had got dropped in the bit-bucket somewhere along the way. If this were a newsgroup I''d have posted a cancellation. *hint hint* -- Stop the infinite loop, I want to get off! http://surreal.istic.org/ Paraphernalia/Never hides your broken bones,/ And I don''t know why you''d want to try:/ It''s plain to see you''re on your own. -- Paul Simon The documentation that can be written is not the true documentation. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Daniel, Thanks for your reply, the hint about the symlink was really helpful - I got at least the driver for the IBM system management board (ibmsmb) to compile and install (which was a tour de force in and of itself). As for your remark, you´re absolutely right, it´s --added-patches=xen - I guess that confirms that I´m not always copy-pasting... Thanks again Olaf btw: As your email suggests that you´re close (at least your mail server is, geographically speaking) to the developers, I can´t help to ask: The roadmap says 3.0 is likely to be released in June - any news on that one? On Aug 1, 2005, at 1:39 PM, Daniel Hulme wrote:>> Some background: I´m trying to compile a few special modules (ibmsmb, >> for the IBM Director Agent, and zaphfc, for HFC-based ISDN cards, in >> case anyone is interested) and their Makefiles assume the presence of >> kernel source header files in case they are build against a 2.6 >> kernel. That is, some meaningful code in /lib/modules/`uname >> -r`/build/include/linux... > /lib/modules/`uname -r`/build is often just a symlink to wherever you > built the kernel from and this is good enough for most uses, but if the > machine you''re compiling on isn''t the machine you''re going to be > running > the kernel from, or if you want to get rid of your kernel sources, you > really do need the kernel_headers package. > >> Trying to build a kernel package using >> >> make-kpkg --added patches=xen --config=menuconfig --arch=xen >> --subarch=xen --revision=xenserver.0.1 kernel-image >> >> works just fine > That''s a surprise. Shouldn''t it be --added-patches instead of --added > patches? I assume this is a typo in copying out the command to the > mail, > but if not, it looks like you have other things to worry about :-> > > Note that make-kpkg has other problems with Xen: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311004 > > Sorry I couldn''t be of more help, > Daniel > > -- > There may come a time The open palm of > desire, > When I will lose you, ]http://surreal.istic.org/[ The rose of > Jericho, > Lose you as I lose my sight, Soil as soft as > Summer, > Days falling backward into velvet night; The strength to let you > go. > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Marcus, Thanks for taking the time to go through the post. Regarding your remarks: I´m using stable, mainly because a while ago a post came round that hiding PCI devices from dom0 isn´t working at the moment. The manpage gives both targets (kernel_headers, kernel-headers) as valid. Tried to toy around with the subarch - no luck. No luck either exporting ARCH=xen. When you start using make-kpkg, maybe the following observations might help: Installing the kernel-package that make-kpkg generated failed to update grub´s menu.lst. The kernel is also named such that it won´t be recognized by grub-update. As I don´t have physical access to the machine I´m using, I haven´t tried the new kernel yet. However I used it to boot a domU and that worked just fine. Again, thanks for looking into it, I´d be interested to see how your make-kpkg experience turns out. Olaf On Aug 2, 2005, at 3:32 AM, Marcus Brown wrote:> Hi Olaf, > > Olaf wrote: > >> Hi, >> >> My apologies for posting this question on this list but I figured that >> the Debian aficionados on this list might be more familiar with the >> issue than the general Debian user. As for the question itself, it >> most likely will attest more to my lack of knowledge than any issue >> with Xen. >> >> Ok, here we go: How do I generate the source header files for a >> 2.6.11 kernel patched with Xen 2.0.6? >> >> Some background: I´m trying to compile a few special modules (ibmsmb, >> for the IBM Director Agent, and zaphfc, for HFC-based ISDN cards, in >> case anyone is interested) and their Makefiles assume the presence of >> kernel source header files in case they are build against a 2.6 >> kernel. That is, some meaningful code in /lib/modules/`uname >> -r`/build/include/linux... >> >> I´m using the unstable packages kernel-source-2.6.11 and the >> kernel-patch-xen to generate the source tree. I also copied the >> .config from the xen0 directory created when downloading the xen 2.0.6 >> source distribution. Trying to build a kernel package using >> >> make-kpkg --added patches=xen --config=menuconfig --arch=xen >> --subarch=xen --revision=xenserver.0.1 kernel-image >> >> works just fine (but I should admit that I haven´t tried that kernel) >> and generates a Debian kernel package in /usr/src. However trying the >> same with >> >> make-kpkg --added patches=xen --config=menuconfig --arch=xen >> --subarch=xen --revision=xenserver.0.1 kernel-image kernel_headers >> >> still generates only the kernel-package. >> >> Doing just a >> >> make-kpkg kernel_headers >> >> is successful in creating a kernel-headers package but I´m wondering >> if that´s then for the right architecture. >> >> At this point I´m well willing to do away with the luxury of Debian >> packages if only I could compile the darn modules. Hence the broad >> question about _any_ way to generate the header files. If there´s a >> neat way to generate a Debian package, that would be to good to be >> true. I should also mention that I´d appreciate any not so subtle hint >> what I´m missing here. >> >> Thanks in advance >> Olaf > > I''ve been using Debian for my Xen, but I''m afraid I haven''t played with > the idea of making packages yet. > The way I''ve been doing it is > - download and unpack the xen branch of choice (currently using > testing), > - install the appropriate kernel source using apt-get (ie. > Debianised kernel source) > - copy the source file into /usr/src/xen > - do a ''make dist'' > - cd to ./linux-2.6.xx-domU and do a ''make ARCH=xen menuconfig'' > - repeat ''make dist'' > - copy kernel/modules/... from ./dist/install/ to destination > > There''s probably a proper way of doing it, but this works for me. I > actually use a > number of different kernels depending on the task of the domU, so I''ve > modified > the KERNEL statement in my Makefile and added extra make scripts in > ./buildconfigs > for each kernel. > > Once I get my new Xen-based server going (I''ve decided the old one is > too inefficient > with both drive space and ram, etc) I too will be looking into > make-kpkg > to simplify (?) > upgrades and maintenance. > > I''m not sure why your headers don''t build, but perhaps you could try: > - kernel-headers instead of kernel_headers? (stab in dark:)) > - remove the subarch stanza? (necessary?) > - export ARCH as an environment variable before make? > - OK, I''ve got no idea :) > > Marcus. > > > _______________________________________________ > Xen-users mailing list > Xen-users@lists.xensource.com > http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Thanks for your reply, the hint about the symlink was really helpful - > I got at least the driver for the IBM system management board (ibmsmb) > to compile and install (which was a tour de force in and of itself).Congratulations. Kernel modules are sent to try us.> btw: As your email suggests that you´re close (at least your mail > server is, geographically speaking) to the developers, I can´t help to > ask: The roadmap says 3.0 is likely to be released in June - any news > on that one?I''m only working on Xen as a short-term thing: the horses in the field have more clout with the developers than me. As to your question, I can confirm that Xen 3.0 is *unlikely* to be released in June or July 2005. :-> -- Stop the infinite loop, I want to get off! http://surreal.istic.org/ Paraphernalia/Never hides your broken bones,/ And I don''t know why you''d want to try:/ It''s plain to see you''re on your own. -- Paul Simon The documentation that can be written is not the true documentation. _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Marcus Brown
2005-Aug-04 12:27 UTC
Re: Spam:***, Re: [Xen-users] Kernel Headers for Xen Kernel
Hi guys, RE: Debian, Xen, make-kpkg, initrd and http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=311004 AFAIK, make-kpkg uses mkinitrd to create the initrd (makes sense?). I have a bootable Xen dom0 with an initrd made using mkinitrd (root on LVM). I suspect that a make-kpkg using my mkinitrd configs would work, however I haven''t tested it yet as I compile my kernels on a separate machine. Happy to post my configs if required. Marcus. Daniel Hulme wrote:>>Thanks for your reply, the hint about the symlink was really helpful - >>I got at least the driver for the IBM system management board (ibmsmb) >>to compile and install (which was a tour de force in and of itself). >> >> >Congratulations. Kernel modules are sent to try us. > > > >>btw: As your email suggests that you´re close (at least your mail >>server is, geographically speaking) to the developers, I can´t help to >>ask: The roadmap says 3.0 is likely to be released in June - any news >>on that one? >> >> >I''m only working on Xen as a short-term thing: the horses in the field >have more clout with the developers than me. As to your question, I can >confirm that Xen 3.0 is *unlikely* to be released in June or July 2005. >:-> > > > >------------------------------------------------------------------------ > >_______________________________________________ >Xen-users mailing list >Xen-users@lists.xensource.com >http://lists.xensource.com/xen-users >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Hi Olaf, Olaf Grewe wrote:> Hi Marcus, > > Thanks for taking the time to go through the post. Regarding your > remarks: > > I´m using stable, mainly because a while ago a post came round that > hiding PCI devices from dom0 isn´t working at the moment. >I''m using sid with xen-testing on my dom0 atm. Hiding seems to works well. # uptime 22:32:00 up 5 days, 7:28, 1 user, load average: 0.00, 0.00, 0.00 LOL ... OK, it''s not doing much by the looks of it! :) kernel /xen-2.0-testing.gz dom0_mem=131072 root=/dev/hda3 ro console=tty0 physdev_dom0_hide=(00:07.2) module /vmlinuz-2.6.11.12-xen0 root=/dev/hda3 ro console=tty0 My development server has a similar setup but uses modules and an initrd, with root on LVM.> The manpage gives both targets (kernel_headers, kernel-headers) as valid. > > Tried to toy around with the subarch - no luck. > > No luck either exporting ARCH=xen. >hmmm.> When you start using make-kpkg, maybe the following observations might > help: Installing the kernel-package that make-kpkg generated failed to > update grub´s menu.lst. The kernel is also named such that it won´t be > recognized by grub-update. As I don´t have physical access to the > machine I´m using, I haven´t tried the new kernel yet. However I used > it to boot a domU and that worked just fine. >I''ve noticed some strange Debian-related naming conventions for kernels and initrds when using make-kpkg ... I''ll keep an eye on it next time I do a batch.> Again, thanks for looking into it, I´d be interested to see how your > make-kpkg experience turns out. > Olaf >I''m about to upgrade the server (long story), so I''ll have a chance to do this soon. I hope to be able to make kernel packages on my workstation and copy them to the server for intstall. I''ll post results.> On Aug 2, 2005, at 3:32 AM, Marcus Brown wrote: > >> Hi Olaf, >> >> Olaf wrote: >> >>> Hi, >>> >>> My apologies for posting this question on this list but I figured that >>> the Debian aficionados on this list might be more familiar with the >>> issue than the general Debian user. As for the question itself, it >>> most likely will attest more to my lack of knowledge than any issue >>> with Xen. >>> >>> Ok, here we go: How do I generate the source header files for a >>> 2.6.11 kernel patched with Xen 2.0.6? >>> >>> Some background: I´m trying to compile a few special modules (ibmsmb, >>> for the IBM Director Agent, and zaphfc, for HFC-based ISDN cards, in >>> case anyone is interested) and their Makefiles assume the presence of >>> kernel source header files in case they are build against a 2.6 >>> kernel. That is, some meaningful code in /lib/modules/`uname >>> -r`/build/include/linux... >>> >>> I´m using the unstable packages kernel-source-2.6.11 and the >>> kernel-patch-xen to generate the source tree. I also copied the >>> .config from the xen0 directory created when downloading the xen 2.0.6 >>> source distribution. Trying to build a kernel package using >>> >>> make-kpkg --added patches=xen --config=menuconfig --arch=xen >>> --subarch=xen --revision=xenserver.0.1 kernel-image >>> >>> works just fine (but I should admit that I haven´t tried that kernel) >>> and generates a Debian kernel package in /usr/src. However trying the >>> same with >>> >>> make-kpkg --added patches=xen --config=menuconfig --arch=xen >>> --subarch=xen --revision=xenserver.0.1 kernel-image kernel_headers >>> >>> still generates only the kernel-package. >>> >>> Doing just a >>> >>> make-kpkg kernel_headers >>> >>> is successful in creating a kernel-headers package but I´m wondering >>> if that´s then for the right architecture. >>> >>> At this point I´m well willing to do away with the luxury of Debian >>> packages if only I could compile the darn modules. Hence the broad >>> question about _any_ way to generate the header files. If there´s a >>> neat way to generate a Debian package, that would be to good to be >>> true. I should also mention that I´d appreciate any not so subtle hint >>> what I´m missing here. >>> >>> Thanks in advance >>> Olaf >> >> >> I''ve been using Debian for my Xen, but I''m afraid I haven''t played with >> the idea of making packages yet. >> The way I''ve been doing it is >> - download and unpack the xen branch of choice (currently using >> testing), >> - install the appropriate kernel source using apt-get (ie. >> Debianised kernel source) >> - copy the source file into /usr/src/xen >> - do a ''make dist'' >> - cd to ./linux-2.6.xx-domU and do a ''make ARCH=xen menuconfig'' >> - repeat ''make dist'' >> - copy kernel/modules/... from ./dist/install/ to destination >> >> There''s probably a proper way of doing it, but this works for me. I >> actually use a >> number of different kernels depending on the task of the domU, so I''ve >> modified >> the KERNEL statement in my Makefile and added extra make scripts in >> ./buildconfigs >> for each kernel. >> >> Once I get my new Xen-based server going (I''ve decided the old one is >> too inefficient >> with both drive space and ram, etc) I too will be looking into make-kpkg >> to simplify (?) >> upgrades and maintenance. >> >> I''m not sure why your headers don''t build, but perhaps you could try: >> - kernel-headers instead of kernel_headers? (stab in dark:)) >> - remove the subarch stanza? (necessary?) >> - export ARCH as an environment variable before make? >> - OK, I''ve got no idea :) >> >> Marcus. >> >> >> _______________________________________________ >> Xen-users mailing list >> Xen-users@lists.xensource.com >> http://lists.xensource.com/xen-users >> >_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > I´m using stable, mainly because a while ago a post came round that > > hiding PCI devices from dom0 isn´t working at the moment. > > > I''m using sid with xen-testing on my dom0 atm. > Hiding seems to works well. > # uptime > 22:32:00 up 5 days, 7:28, 1 user, load average: 0.00, 0.00, 0.00 > LOL ... OK, it''s not doing much by the looks of it! :) > > kernel /xen-2.0-testing.gz dom0_mem=131072 root=/dev/hda3 ro > console=tty0 physdev_dom0_hide=(00:07.2) > module /vmlinuz-2.6.11.12-xen0 root=/dev/hda3 ro console=tty0 > > My development server has a similar setup but uses modules and an initrd, > with root on LVM.>From what I recall, it is the unstable tree that doesn''t supporthiding pci devices - anything in 2.0 (testing or stable) does (somebody please correct me if I''m wrong).> > When you start using make-kpkg, maybe the following observations might > > help: Installing the kernel-package that make-kpkg generated failed to > > update grub´s menu.lst. The kernel is also named such that it won´t be > > recognized by grub-update. As I don´t have physical access to the > > machine I´m using, I haven´t tried the new kernel yet. However I used > > it to boot a domU and that worked just fine. > > > I''ve noticed some strange Debian-related naming conventions for kernels > and initrds when using make-kpkg ... I''ll keep an eye on it next time I do a batch. > > > Again, thanks for looking into it, I´d be interested to see how your > > make-kpkg experience turns out. > > Olaf > > > I''m about to upgrade the server (long story), so I''ll have a chance to > do this soon. I hope to be able to make kernel packages on my workstation > and copy them to the server for intstall. > I''ll post results. >1) I often use make-kpkg to create new debian/xen kernels (http://www.option-c.com/xwiki/Custom_Xen_Kernels#Option_2:_From_the_Debian_Sources_with_the_Xen_Patches - sorry, I''m being a bit lazy with my forum posts today and just giving links). Although I was curious about the issues with the kernel_headers target, they appear to have been worked out. My only comment is that these days it''s not usually make-kpkg that''s the issue, it''s getting the config right... 2) As far as I can tell with my experiences (and I''m probably wrong)... *update-grub does rely on very specific naming conventions. If you use then xen kernel patches to build xen kernels (with make-kpkg), if prepends "xen-linux" which results in those kernels being ignored by update-grub *Even if the xen kernels weren''t ignored, update-grub (in debian sarge) does not currently support all the needed options to boot a xen kernel * I created a quick, temporary (and no doubt horrible) modified version of update-grub which "seems to work." It deals with "xen-linux" prepended kernels, and also with the xen binary install (the symlinks are a bit of a problem for update-grub). Anyhow, feel free to use it - the modified script is called update-grub-xen - the most recent version should be here: http://www.option-c.com/debian/pool/main/x/xen/ ...but if you want to have it run every time you install a new kernel, you''ll need to edit the hooks in /etc/kernel-img.conf. br, Yvette _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users