Does Proxmox VE 1.3 safely work with kernel 2.6.24-2-pve

Smanux

Renowned Member
Jun 29, 2009
39
4
73
Hi,

I upgraded a server from Proxmox 1.1 to 1.3 but I have some troubles booting on the 2.6.24-7-pve kernel. The previous one, 2.6.24-2-pve, still seems to work though. I wonder if I can safely keep using this kernel? Is there a major risk doing so? The server hosts only 3 OpenVZ containers, there is no KVM guest.

Thank you
 
Hi,

I upgraded a server from Proxmox 1.1 to 1.3 but I have some troubles booting on the 2.6.24-7-pve kernel. The previous one, 2.6.24-2-pve, still seems to work though. I wonder if I can safely keep using this kernel? Is there a major risk doing so? The server hosts only 3 OpenVZ containers, there is no KVM guest.

Thank you

what kind of booting problems? any details? the new Kernel mainly contains new drivers and new KVM.
 
what kind of booting problems? any details? the new Kernel mainly contains new drivers and new KVM.

Thank you for your reply. I don't know exactly what happens since I can't see the console during the boot sequence. I'm just sure it doesn't boot at all since the files in /var/log are not updated when the new kernel is enabled.

This is on a server hosted at OVH. I ran the update script and followed the instructions at http://travaux.ovh.net/?do=details&id=3077 to recreate the initrd file (I ran update-initramfs twice for the kernels 2.6.24-5-pve and 2.6.24-7-pve). The server is a Quad Opteron 1354 with a hardware RAID and a simple partitioning scheme:

Code:
   Device Boot      Start         End      Blocks   Id  System
/dev/sda1   *           1         653     5245191   83  Linux
/dev/sda2             654       91136   726804697+  83  Linux
/dev/sda3           91137       91201      522112+  82  Linux swap / Solaris
Here is the content of the /boot directory:

Code:
rescue:/mnt/sda1# ll -h -R boot
boot:
total 68M
-rw-r--r--  1 root root 1.2M Jan 14 12:00 System.map-2.6.24-2-pve
-rw-r--r--  1 root root 1.2M May 12 09:07 System.map-2.6.24-5-pve
-rw-r--r--  1 root root 1.2M Jun  2 08:06 System.map-2.6.24-7-pve
-rw-r--r--  1 root root  82K Jan 14 12:00 config-2.6.24-2-pve
-rw-r--r--  1 root root  82K May 12 09:07 config-2.6.24-5-pve
-rw-r--r--  1 root root  82K Jun  2 08:06 config-2.6.24-7-pve
drwxr-xr-x  2 root root 4.0K Jun 28 23:47 grub
-rw-r--r--  1 root root 3.5M Jun 28 23:46 initrd.img-2.6.24-2-pve
-rw-r--r--  1 root root 3.4M Apr 17 10:00 initrd.img-2.6.24-2-pve.bak
-rw-r--r--  1 root root 3.7M Jun 28 23:52 initrd.img-2.6.24-5-pve
-rw-r--r--  1 root root  14M May 12 09:10 initrd.img-2.6.24-5-pve.bak
-rw-r--r--  1 root root 3.7M Jun 29 00:14 initrd.img-2.6.24-7-pve
-rw-r--r--  1 root root  13M Jun  2 08:09 initrd.img-2.6.24-7-pve.bak
-rw-r--r--  1 root root 122K Oct  8  2008 memtest86+.bin
-rw-r--r--  1 root root 1.2M Sep  8  2008 old.System.map-2.6.24-proxmox
-rw-r--r--  1 root root 3.4M Sep  8  2008 old.bzImage-2.6.24-proxmox
-rw-r--r--  1 root root  41K Sep  8  2008 old.config-2.6.24-proxmox
-rw-r--r--  1 root root  13M Jan 14 12:01 old.initrd.img-2.6.24-2-pve
-rw-r--r--  1 root root 2.0M Jan 14 12:00 vmlinuz-2.6.24-2-pve
-rw-r--r--  1 root root 2.1M May 12 09:07 vmlinuz-2.6.24-5-pve
-rw-r--r--  1 root root 2.1M Jun  2 08:06 vmlinuz-2.6.24-7-pve

boot/grub:
total 192K
-rw-r--r--  1 root root  197 Mar 13 20:00 default
-rw-r--r--  1 root root   15 Mar 13 20:00 device.map
-rw-r--r--  1 root root 7.5K Mar 13 20:00 e2fs_stage1_5
-rw-r--r--  1 root root 7.4K Mar 13 20:00 fat_stage1_5
-rw-r--r--  1 root root 8.0K Mar 13 20:00 jfs_stage1_5
-rw-r--r--  1 root root 3.2K Jun 28 23:47 menu.lst
-rw-r--r--  1 root root 3.8K Feb  3 23:11 menu.lst.bak
-rw-r--r--  1 root root 3.2K Jun 28 23:47 menu.lst~
-rw-r--r--  1 root root 6.8K Mar 13 20:00 minix_stage1_5
-rw-r--r--  1 root root 9.1K Mar 13 20:00 reiserfs_stage1_5
-rw-r--r--  1 root root  512 Mar 13 20:00 stage1
-rw-r--r--  1 root root 107K Mar 13 20:00 stage2
-rw-r--r--  1 root root 8.7K Mar 13 20:00 xfs_stage1_5
After running the upgrade script the file /boot/grub/menu.lst contained this:

Code:
title           Debian GNU/Linux, kernel 2.6.24-7-pve
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.24-7-pve root=/dev/sda1 ro 
initrd          /boot/initrd.img-2.6.24-7-pve
I reverted to this to get the server to boot again:

Code:
title           Debian GNU/Linux, kernel 2.6.24-2-pve
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.24-2-pve root=/dev/sda1 ro 
initrd          /boot/initrd.img-2.6.24-2-pve
savedefault

title           Debian GNU/Linux, kernel 2.6.24-2-pve (single-user mode)
root            (hd0,0)
kernel          /boot/vmlinuz-2.6.24-2-pve root=/dev/sda1 ro single
initrd          /boot/initrd.img-2.6.24-2-pve
savedefault
 
AFAIK OVH uses a modified kernel - You need to ask OVH support for details about kernel upgrades.
 

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!