New KVM 0.12.4 in pvetest repo (Kernel branch 2.6.24 and 2.6.32)

martin

Proxmox Staff Member
Staff member
Apr 28, 2005
754
1,742
223
Hi all,

Just uploaded the latest KVM 0.12.4 to the pvetest repository!
(deb http://download.proxmox.com/debian lenny pvetest)

Kernel 2.6.32 (KVM only)
Code:
pveversion -v

pve-manager: 1.5-9 (pve-manager/1.5/4728)
running kernel: 2.6.32-2-pve
proxmox-ve-2.6.32: 1.5-7
pve-kernel-2.6.32-2-pve: 2.6.32-7
qemu-server: 1.1-14
pve-firmware: 1.0-4
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
ksm-control-daemon: 1.0-3
Kernel 2.6.24 (KVM and OpenVZ)
Code:
pveversion -v

pve-manager: 1.5-9 (pve-manager/1.5/4728)
running kernel: 2.6.24-11-pve
proxmox-ve-2.6.24: 1.5-22
pve-kernel-2.6.24-11-pve: 2.6.24-22
qemu-server: 1.1-14
pve-firmware: 1.0-4
libpve-storage-perl: 1.0-13
vncterm: 0.9-2
vzctl: 3.0.23-1pve11
vzdump: 1.2-5
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.12.4-1
We appreciate all feedback and bug reports in this forum.

Best regards,

Martin
 
Nice to know. Today I was at OpenSource Day in Warsaw and talked to RedHat technician. He said that KSM is working with current RHEL5 kernel, it just needs ksm-daemon, that's all. Maybe it's worth trying? If it's true - we've got briliant mix of KVM + KSM and OpenVZ platform :). RHVE is now using 2.6.18 and it supports KSM.

Also good news is that he confirmed that RHEL6 is going to use "kernel something in between 2.6.32 and 2.6.33", what means it's 2.6.32 with many things backported from 2.6.33.
 
yes, KSM works in 2.6.18 but not together with the OpenVZ patches.
 
yes, ongoing and no issues so far.
 
Since the proxmox project doesn't have a repo to check the PVE source against and no change log how can we truly tell what has or has not been fixed. I'm currently plagued with ipv6 issues in 2.6.18, 2.6.24-10 and 11.

/b
 
Since the proxmox project doesn't have a repo to check the PVE source against and no change log how can we truly tell what has or has not been fixed.

Proxmox assembles code from various sources - you need to use the changlog from those sources.