New 2.6.32 Kernel for 1.9

martin

martin

Proxmox Staff Member
Staff member
Apr 28, 2005
756
2,013
263
We just moved a new kernel from the pvetest repository to stable. This one is based on the latest stable OpenVZ kernel.

Everybody should update as always.

Release notes:

- pve-kernel-2.6.32 (2.6.32-55)
  • rebase on vzkernel-2.6.32-042stab044.11.src.rpm
__________________
Best regards,
Martin Maurer
 
I can't use usb_add host:0529:0001 after this upgrade. This command crashes kvm machine with linux.
I've tried:
- using linux 32 instead of 64
- using last updated linux with latest kernels
- disabling KVM (it was the last chance)
- replacing virtio by ide
Nothing helped. Bios is okay, grub is okay, than KVM stars to boot linux and crashes.
 
downgrade the pve-qemu-kvm package.

Code: 
wget http://download.proxmox.com/debian/dists/lenny/pve/binary-amd64/pve-qemu-kvm_0.15.0-1_amd64.deb

dpkg -i binary-amd64/pve-qemu-kvm_0.15.0-1_amd64.deb

does this help?
 
Hello Martin,

It works! Thanks a bunch!

Before downgrade
*************************************************************************
virt1:/tmp# qm start 107
kvm: usb_create: no bus specified, using "usb.0" for "usb-host"

husb: open device 3.2
husb: grabbed usb device 3.2
*************************************************************************

After downgrade
*************************************************************************
virt1:/tmp# qm start 107
kvm: usb_create: no bus specified, using "usb.0" for "usb-host"

husb: open device 3.2
husb: config #1 need -1
husb: 1 interfaces claimed for configuration 1
husb: grabbed usb device 3.2
*************************************************************************


Stas
 
I have the same problem.
A Aladdin-Dongle works fine, a CodeMeter-Stick lets crashes the kvm machine.
A downgrade solve the problem.
 
After update to this new kernel a simple "ping -R" crashes our proxmox servers, downgrading from 2.6.32-55 to 2.6.32-50 helped to fix this problem.
Thank you for your good work, maybe you can help to solve this problem with the new 2.6.32 kernel...

Message from syslogd@vhost10 at Jan 5 20:22:17 ...
kernel:Oops: 0000 [#1] SMP

Message from syslogd@vhost10 at Jan 5 20:22:17 ...
kernel:last sysfs file: /sys/kernel/mm/ksm/run

Message from syslogd@vhost10 at Jan 5 20:22:17 ...
kernel:Stack:

Message from syslogd@vhost10 at Jan 5 20:22:17 ...
kernel:Call Trace:

Message from syslogd@vhost10 at Jan 5 20:22:17 ...
kernel: <IRQ>
Write failed: Broken pipe


Best regards!
 
dietmar said:
I am unable to reproduce that. What driver do you use exactly?
Click to expand...

i am able to reproduce this as well (server hangs, nothing in logs) - though it seems it does not happen with every pinged site:

Ethernet controller: Intel Corporation 82576 Gigabit Network Connection (rev 01)

filename: /lib/modules/2.6.32-6-pve/kernel/drivers/net/igb/igb.ko
version: 3.2.10
license: GPL
description: Intel(R) Gigabit Ethernet Network Driver
author: Intel Corporation, <e1000-devel@lists.sourceforge.net>
srcversion: BAAD5948059DD794C854151

pve-manager: 1.9-26 (pve-manager/1.9/6567)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 1.9-55
 
dietmar said:
I am unable to reproduce that. What driver do you use exactly?
Click to expand...
Hi Dietmar,
one system which generate an kernel-dump use e1000e:
Code: 
modinfo e1000e
filename:       /lib/modules/2.6.32-6-pve/kernel/drivers/net/e1000e/e1000e.ko
version:        1.6.3-NAPI
license:        GPL
description:    Intel(R) PRO/1000 Network Driver
author:         Intel Corporation, <linux.nics@intel.com>
srcversion:     573097600A023AE89AF9AF5
Networkconfig plain (only vmbr0 - without vlantagging).

Udo
 
dietmar said:
I am unable to reproduce that. What driver do you use exactly?
Click to expand...
Hi,
the same happens with another box - solarflare-nic with vlan-tagging:
Code: 
modinfo sfc
filename:       /lib/modules/2.6.32-6-pve/kernel/drivers/net/sfc/sfc.ko
license:        GPL
description:    Solarflare Communications network driver
author:         Solarflare Communications and Michael Brown <mbrown@fensystems.co.uk>
srcversion:     FD7AF0ECCCBF1333E8EC1A9
alias:          pci:v00001924d00000813sv*sd*bc*sc*i*
...

pveversion -v
pve-manager: 2.0-18 (pve-manager/2.0/16283a5a)
running kernel: 2.6.32-6-pve
proxmox-ve-2.6.32: 2.0-55
pve-kernel-2.6.32-6-pve: 2.6.32-55
lvm2: 2.02.88-2pve1
clvm: 2.02.88-2pve1
corosync-pve: 1.4.1-1
openais-pve: 1.1.4-1
libqb: 0.6.0-1
redhat-cluster-pve: 3.1.8-3
pve-cluster: 1.0-17
qemu-server: 2.0-13
pve-firmware: 1.0-14
libpve-common-perl: 1.0-11
libpve-access-control: 1.0-5
libpve-storage-perl: 2.0-9
vncterm: 1.0-2
vzctl: 3.0.29-3pve8
vzprocps: 2.0.11-2
vzquota: 3.0.12-3
pve-qemu-kvm: 1.0-1
ksm-control-daemon: 1.1-1
Udo
 
Is there a workaround for the ping -R bug, because this behave in all Kernels from the 1.9 release
and also in the 2.0 beta
 
we will provide new kernels as soon as released from openvz.org, see bugreport from above.
 
Hello,

i want to ask about some root exploits that are presented in all Linux Kernel 64 bits < 2.6.36-rc4: .
I have testet the PVE 1.9 but the host machine have Kernel version: Linux version 2.6.32-4-pve

Are these Kernels patched to block ia32syscall emulation vulnerability ??

Thank you
Melisa
 
2.6.32-4-pve is outdated and not maintained, use 2.6.32-6-pve.
 
hi
Whether proxmox 1.9 support of HBA HP controler dual port fiber
please give part number this hba device
thanks
 
You must log in or register to reply here.
Top Bottom