New 2.6.32 Kernel for Proxmox VE 1.9 stable

[martin]

We just uploaded a new kernel to 1.9 stable. This one is based on the latest stable OpenVZ kernel, additionally updated Intel NIC drivers.

Everybody should update as always.

Release notes

- pve-kernel-2.6.32 (2.6.32-55+ovzfix-1)

• rebase on vzkernel-2.6.32-042stab044.17.src.rpm

- update e1000e to 1.9.5
- update igb to 3.3.6
- update ixgbe to 3.7.17

__________________
Best regards,
Martin Maurer

 

[jleg]

We just uploaded a new kernel to 1.9 stable. This one is based on the latest stable OpenVZ kernel, additionally updated Intel NIC drivers.

Everybody should update as always.

Release notes

- pve-kernel-2.6.32 (2.6.32-55+ovzfix-1)

• rebase on vzkernel-2.6.32-042stab044.17.src.rpm

hm, was this intended?

a week ago:
[INSTALL, DEPENDENCIES] pve-kernel-2.6.32-7-pve
[UPGRADE] proxmox-ve-2.6.32 1.9-55 -> 1.9-56

now:
[REMOVE, NOT USED] pve-kernel-2.6.32-7-pve
[UPGRADE] proxmox-ve-2.6.32 1.9-56 -> 1.9-55+ovzfix-1

#pveversion -v
pve-kernel-2.6.32-6-pve: 2.6.32-55+ovzfix-1


versioning seems a bit out-of-standard?

 

[dietmar]

a week ago:
[INSTALL, DEPENDENCIES] pve-kernel-2.6.32-7-pve
[UPGRADE] proxmox-ve-2.6.32 1.9-55 -> 1.9-56

You are using the test repository?

 

[jleg]

You are using the test repository?

Yes...

 

[tom]

pvetest repository is using openvz testing kernels.
pve repository is using openvz stable kernels.

sometimes a openvz testing kernel is moved to stable, sometimes not - sorry for confusion.

 

[jleg]

pvetest repository is using openvz testing kernels.
pve repository is using openvz stable kernels.

sometimes a openvz testing kernel is moved to stable, sometimes not - sorry for confusion.

nevermind, nothing broke (so far - it was just noticable that our test server for the first time got a kernel with a "suffix" other than "-##" number, and that a sort of "version downgrade" took place (55 -> 56, 32-7 -> 32-6)...
[or did you mean that our prior version (-7) was from the non-test-repo? Hell, in fact our sources.lst does contain both (pvetest pve) - never noticed that before, but that would probably explain this "jump" then...]