New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32) [UPDATE]

[online24]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Hey, who have tested 2.6.18 kernel. CpuLimit works with or without problems?

 

[dietmar]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Dietmar, maybe this can help, initramfs output after installing 2.6.32 kernel

update-initramfs: Generating /boot/initrd.img-2.6.32-1-pve
W: Possible missing firmware /lib/firmware/bnx2/bnx2-rv2p-09ax-5.0.0.j3.fw for module bnx2

OK, I juste uploaded a new firmware package to the pvetest repository. Please can you update and test if it works now.

 

[chopeta]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

OK, I juste uploaded a new firmware package to the pvetest repository. Please can you update and test if it works now.

Just tested it... still no network... new logs sent by email.

pve-manager: 1.5-1 (pve-manager/1.5/4561)
running kernel: 2.6.24-9-pve
proxmox-ve-2.6.32: 1.5-2
pve-kernel-2.6.32-1-pve: 2.6.32-2
pve-kernel-2.6.24-7-pve: 2.6.24-11
pve-kernel-2.6.24-9-pve: 2.6.24-18
qemu-server: 1.1-10
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-6
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1
ksm-control-daemon: 1.0-1

 

[chopeta]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

OK, the new firmware was in there:

# ls -l /lib/firmware/bnx2/bnx2-mips-06-5.0.0.j3.fw
-rw-r--r-- 1 root root 93172 Dec 29 05:04 /lib/firmware/bnx2/bnx2-mips-06-5.0.0.j3.fw

Looks like I was just had to update my initrd image (thanks dietmar!)

# update-initramfs -u -t

Testing new kernel now, with virtio and 2 cores...

Thanks again PVE team for this awesome job!

Regards,
chopeta

 

[adis]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

I can also confirm that everything works now.

pve-manager: 1.5-1 (pve-manager/1.5/4561)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-2
pve-kernel-2.6.32-1-pve: 2.6.32-2
pve-kernel-2.6.24-10-pve: 2.6.24-21
qemu-server: 1.1-10
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-6
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1
ksm-control-daemon: 1.0-1

Additionally, the 2.6.32 kernel resolved another issue for me (freezing during KVM guest install, but only for openSuSE 11.2 32bit and 64bit, weird).

Thanks guys, you are really the best.

 

[online24]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Hey,

2.6.18 kernel works perfect with cpulimit ! Guys, You are the best

 

[eislon]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Installed the latest 2.6.32 kernel in a virtual proxmox.
It seems to work alright (except the openvz part ;-)

With pveversion -v I get the following information:

pveversion -v
pve-manager: 1.5-1 (pve-manager/1.5/4561)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-2
pve-kernel-2.6.32-1-pve: 2.6.32-2
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-10
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-6
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1
ksm-control-daemon: 1.0-2

Other tests have to be made.

 

[mr_cygi]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Hi,

2.6.18 is integrated with cpus parameter support?
When I install this kernel on pve-manager/1.4/4340 all will be ok?
OpenVZ is the most important for me.

 

[online24]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Hey, cpulimit and cpus works without problems. All will be fine.

 

[mr_cygi]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

But only for 2.6.18? That's right?

 

[online24]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

hey, yes. On 2.6.24 or 2.6.32 you must use cpuunits ;-)

 

[moula]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Bonne Année 2010 à toute l'équipe PVE et à tous.

I upgraded to 2.6.32 and after rebooting I cannot remove a Container(s) . i removed it manually. another problem i can't install a container. this is the message when i try to install it : --config pve.auto failed with exit code 5 : unable to open /dev/vzctl: No such file or directory , please check that vzdev kernel module is loaded ... but i don't find vzdev kernel!!!!

this is my pveversion :
pve-manager: 1.5-1 (pve-manager/1.5/4561)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-2
pve-kernel-2.6.32-1-pve: 2.6.32-2
qemu-server: 1.1-10
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-6
vncterm: 0.9-2
vzctl: 3.0.23-1pve3
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1
ksm-control-daemon: 1.0-2

Thnk's.

 

[dietmar]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

I upgraded to 2.6.32 and after rebooting I cannot remove a Container(s)

The 2.6.32 kernel does not have OpenVZ support - use 2.6.18 or 2.6.24 if you need OpenVZ.

 

[dietmar]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Installed the latest 2.6.32 kernel in a virtual proxmox.
It seems to work alright (except the openvz part ;-)

2.6.32 has no OpenVZ support.

 

[moula]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Ok, thank's. I'm going back to previous kernel.

 

[online24]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

2.6.18 is buged on PVE 1,4. VPS'es didint reboot; syslog send messages: "
unregister_netdevice: waiting for venet0=ffff81033940b800 to become free. Usage count = 3 ve=181
unregister_netdevice: waiting for venet0=ffff81033940b800 to become free. Usage count = 3 ve=181
unregister_netdevice: waiting for venet0=ffff81033940b800 to become free. Usage count = 3 ve=181
unregister_netdevice: waiting for venet0=ffff81033940b800 to become free. Usage count = 3 ve=181
unregister_netdevice: waiting for venet0=ffff81033940b800 to become free. Usage count = 3 ve=181
unregister_netdevice: device ffff81033940b800 marked to leak
free_netdev: device venet0=ffff81033940b800 leaked
unregister_netdevice: waiting for lo=ffff810328acd800 to become free. Usage count = 6 ve=181
unregister_netdevice: waiting for lo=ffff810328acd800 to become free. Usage count = 6 ve=181
unregister_netdevice: waiting for lo=ffff810328acd800 to become free. Usage count = 6 ve=181
unregister_netdevice: waiting for lo=ffff810328acd800 to become free. Usage count = 6 ve=181
unregister_netdevice: waiting for lo=ffff810328acd800 to become free. Usage count = 6 ve=181
unregister_netdevice: device ffff810328acd800 marked to leak
free_netdev: device lo=ffff810328acd800 leaked
"

 

[eislon]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

2.6.32 has no OpenVZ support.

I know, that why i place a smile behind it...
I just wanted to tell that the installation gave no problems with that proxmox installation.

 

[garrettwp]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

I updated to Kernel 2.6.32 as I only use KVM and the KSM feature looks promising. The update went well except for the fact that my one network card is acting weird. The card detects fine, but I can not get network activity from it. It was working fine before the update. Here is the info via lspci:

02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8053 PCI-E Gigabit Ethernet Controller (rev 20)

proxmox:~# pveversion -v
pve-manager: 1.5-1 (pve-manager/1.5/4561)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-2
pve-kernel-2.6.32-1-pve: 2.6.32-2
pve-kernel-2.6.24-7-pve: 2.6.24-11
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-10
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-6
vncterm: 0.9-2
vzctl: not correctly installed
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1
ksm-control-daemon: 1.0-2

Does anyone have any suggestions to try? I have two network cards and I am currently using the working one until I can get this figured out.

- Garrett

 

[udo]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

Hi Garret,
the Nic isn't renamed in /etc/udev/rules.d/70-persistent-net.rules?

Udo

 

[prometheanfire]

Re: New Proxmox VE Kernels (2.6.18 - 2.6.24 - 2.6.32)

I had an issue with the update on reboot. The update went fine, great even but when it tried to boot up my VMs I had an issue with them freezing, I'll post the configs of how I got it working (I didn't think to create a backup of the config to post a before and after).

NOT WORKING CONFIG

cat /etc/qemu-server/105.conf
name: mail
bootdisk: virtio0
virtio0: os-images:vm-105-disk-1
vlan3: virtio=BE:86A:22:C0:96
ostype: l26
memory: 256
onboot: 1
sockets: 1
boot: c
freeze: 0
cpuunits: 1000
acpi: 1
kvm: 1
description: postfixadmin<br>10.0.1.6<br>
cores: 1
​

WORKING CONFIG

cat /etc/qemu-server/101.conf
name: http
bootdisk: virtio0
ostype: l26
memory: 512
onboot: 1
sockets: 1
boot: c
freeze: 0
cpuunits: 1000
acpi: 1
kvm: 1
cores: 1
virtio0: os-images:vm-101-disk-3
description: dns,wiki,blog
vlan3: virtio=12:12:12:12:12:12
​

They should be about identical.
I got rid of the CDROM as that seemed to help the others boot somehow.
The kernel version that is running on the guest is gentoo-hardened-2.6.28-r9 and had an uptime of 72 days before I rebooted the server earlier. If you want the server config I'll post that for you.

here is additional info

pveversion -v
pve-manager: 1.5-1 (pve-manager/1.5/4561)
running kernel: 2.6.32-1-pve
proxmox-ve-2.6.32: 1.5-2
pve-kernel-2.6.32-1-pve: 2.6.32-2
pve-kernel-2.6.24-9-pve: 2.6.24-18
pve-kernel-2.6.24-8-pve: 2.6.24-16
qemu-server: 1.1-10
pve-firmware: 1.0-3
libpve-storage-perl: 1.0-6
vncterm: 0.9-2
vzctl: 3.0.23-1pve4
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.11.1-1
ksm-control-daemon: 1.0-2
​

It is working now, I am guessing it is a guest issue, I hope it doesn't flare up in any other way when the kernel eventually gets updated.