[PVE-User] Proxmox VE 2.0 beta3 released!

[Flavio Stanchina]

Martin Maurer wrote:
> We just released the third beta of Proxmox VE 2.0 [...]

I had a few errors on upgrade. Apparently, someone forgot to remove 
references to previously installed kernels which are now long gone.

This is an "expendable" machine I use for testing. I upgraded it from 
PVE 1.9 to PVE 2.0 beta a few weeks ago to check if that would work out: 
I had to remove all PVE packages, upgrade to squeeze then reinstall PVE. 
When it was running PVE 1.x it went through most of the available 
kernels, as you will see in a moment. I don't think this is a 2.0 
specific problem, I'd rather suspect something wrong in the pve-kernel 
prerm/postrm scripts, maybe related to the switch from Debian kernels to 
RH kernels.

The upgrade from beta2 to beta3 went like this:

[downloading, unpacking, etc.]
Setting up pve-kernel-2.6.32-6-pve (2.6.32-53) ...
update-initramfs: Generating /boot/initrd.img-2.6.32-6-pve
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-2.6.32-6-pve
Found initrd image: /boot/initrd.img-2.6.32-6-pve
Found memtest86+ image: /memtest86+.bin
Found memtest86+ multiboot image: /memtest86+_multiboot.bin
done
[other uneventful "Setting up ..." messages]
Setting up proxmox-ve-2.6.32 (2.0-53) ...
installing proxmox release key: OK
Processing triggers for initramfs-tools ...
update-initramfs: Generating /boot/initrd.img-2.6.35-1-pve
grep: /boot/config-2.6.35-1-pve: No such file or directory
WARNING: missing /lib/modules/2.6.35-1-pve
Device driver support needs thus be built-in linux image!
WARNING: Couldn't open directory /lib/modules/2.6.35-1-pve: No such file 
or directory
FATAL: Could not open /lib/modules/2.6.35-1-pve/modules.dep.temp for 
writing: No such file or directory
FATAL: Could not load /lib/modules/2.6.35-1-pve/modules.dep: No such 
file or directory
[followed by 50 errors like the last one]

Trying to update all initrds explicitly:

# update-initramfs -k all -u
/boot/initrd.img-2.6.35-1-pve does not exist. Cannot update.
update-initramfs: Generating /boot/initrd.img-2.6.32-6-pve
/boot/initrd.img-2.6.32-4-pve does not exist. Cannot update.
/boot/initrd.img-2.6.32-1-pve does not exist. Cannot update.
/boot/initrd.img-2.6.24-10-pve does not exist. Cannot update.

Some investigation reveals these files in /var/lib/initramfs-tools:

# ls -l /var/lib/initramfs-tools
total 20
-rw-r--r-- 1 root root 73 Feb 17  2010 2.6.24-10-pve
-rw-r--r-- 1 root root 72 Feb 15  2010 2.6.32-1-pve
-rw-r--r-- 1 root root 72 Oct  5 18:30 2.6.32-4-pve
-rw-r--r-- 1 root root 72 Nov 30 10:33 2.6.32-6-pve
-rw-r--r-- 1 root root 72 Nov 30 10:30 2.6.35-1-pve

Removing all stale files (i.e. all except 2.6.32-6-pve) fixes the problem.

-- 
Flavio Stanchina
Informatica e Servizi
Trento - Italy

Debugging is twice as hard as writing the code in the first place.
Therefore, if you write the code as cleverly as possible, you are,
by definition, not smart enough to debug it.
  -- Brian W. Kernighan