Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I happen to run into various problems regarding grub and kernels. I don't really care about the kernel internas. All I want is VMware server in that dedicated root-server.

1.) What is a bzImage vs. vmlinuz?

kaze:~# ls /boot/  bzImage-   config-  initrd.img-2.6.32-5-amd64    bzImage-   config-  vmlinuz-2.6.32-5-amd64    config-2.6.32-5-amd64  grub

I updated my menu.lst (grub2):

timeout 5
default         0
fallback 1

    kernel (hd0,1)/boot/vmlinuz-2.6.32-5-amd64 root=/dev/sda2 panic=60 noapic acpi=off

    kernel (hd0,1)/boot//bzImage- root=/dev/sda2 panic=60  noapic acpi=off

    kernel (hd0,1)/boot//bzImage- root=/dev/sda2 panic=60  noapic acpi=off

That doesn't do well... I think the vmlinuz file is missing initrd or so. Dunno. In fact I don't give too much about kernel boot voodoo as long as it works. update-grub(2) does not work. Does anybody know what magical trick there is to get the 2.6.32-5 booting?

2.) I thought t follow the Deban wiki.. I cannot get header-files for the installed 35.6 or 33.2 kernel in the repositories. I cannot build foreign headers because they will not match the running kernel. So how does one deal with that situtation? I'd prefer not to have to downgrade the kernel.

Thanks for any answers!

share|improve this question

closed as too localized by voretaq7 Nov 16 '12 at 20:12

This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, visit the help center.If this question can be reworded to fit the rules in the help center, please edit the question.

Oh god, VMWare server is EOL. Use a supported and current product. – MDMarra Jun 7 '12 at 20:59

Well from the looks these 2.6.33 and 2.6.35 images were built by someone by hand... because once you build your kernel from source kernel image is named bzImage, and whoever made it just moved bzImage file to /boot and appended the version to the name. There is no difference in vmlinuz and bzImage; it's just convention once you install the kernel in boot you name it vmlinuz. Now those made by hand probably don't need initrd for booting but the 2.6.32-5-amd64 one needs it.

Try adding the line

initrd /boot/initrd.img-2.6.32-5-amd64

in the block after kernel line.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.