New 2.6.32 Kernel released to stable

[martin]

We just released a new Kernel to the stable repository, also some updates in pve-manager and vzctl. Many thanks for all testers, these packages are just moved from the pvetest repository to pve.Release notes:- pve-kernel-2.6.32-6-pve (2.6.32-50)

• update to vzkernel-2.6.32-042stab039.10.src.rpm
• update e1000e to 1.6.3
• update igb to 3.2.10
• update ixgbe to 3.6.7

- vzctl 3.0.29-3pve1

• include ipv6 default route patch (f0d50feef9521318e80fb5ea8e4da980f9f13fe7)

- pve-manager 1.9-26

• fix chown call (bug #23)

__________________Best regards,Martin Maurer

 

[hk@]

Hi
I know this has been brought up in the past, but I would like to try to argue for it:
"uname -a" on proxmox tells me no details about which iteration of the pve-kernel 2.6.32-6 the system is running.
Therefore in case of updates like this one there is no way of telling with a simple command and check which kernel is running and if the system should be rebooted or not. Doing some "dpkg -l" won't get me far either, as there I see the already "installed" new package and again no means to tell whether this is already running or not...
This is my argument to show a bit more details on the pve kernel version.

best
hk

 

[tom]

I understand your request but that's the standard way on Debian. I see no fast way to change this.

You need to check the build date to be sure you got the right one (uname -a shows the date).

 

[hk@]

Hi Tom,
thank you for your reply - please then add the "latest stable build date" somehow to eg. http://pve.proxmox.com/wiki/Proxmox_VE_Kernel or any other page you see fit for sysadmins to get a clear head in upgrading their systems.

Kindest Regards,
hk

 

[tom]

done. http://pve.proxmox.com/wiki/Proxmox_VE_Kernel#Kernel_2.6.32_.28recommended.29

 

[hk@]

Hi
first thanks and then I have to ask
I guess you do something like this some time after you configured and modified your kernel to your likeing:
fakeroot make-kpkg --initrd --revision=custom.1.0 kernel_image
Now, I admit it has been some years since I built my last very own kernel (btw. then I was doing some stuff around linux-vserver project and UMLs and so on), but maybe you could consider some revision-string for PVE kernels where one could easily figure "ok, I'm on latest stable all is well", this would make system-update-monitoring a bigger charm for all I guess.

Kindest Regards
hk