Proxmox VE 1.8 released!

I'm running proxmox 1.8 w/ kernel 2.6.35 for KSM support. I have 2 Server 2008 R2 SP1 virtual machines, and one Windows 7 64-bit virtual machine, but KSM isn't reducing the pages:

proxmox:~# pveversion -v
pve-manager: 1.8-15 (pve-manager/1.8/5754)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.8-10
pve-kernel-2.6.32-4-pve: 2.6.32-32
pve-kernel-2.6.35-1-pve: 2.6.35-10
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-16
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-11
vzprocps: 2.0.11-1dso2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-2
ksm-control-daemon: 1.0-5
proxmox:~# uname -a
Linux proxmox 2.6.35-1-pve #1 SMP Tue Mar 1 13:18:55 CET 2011 x86_64 GNU/Linux

proxmox:~# cat /sys/kernel/mm/ksm/pages_shared
0

any ideas?
 
Update to the latest packages again, there is a fix for the ksm issue.

Sent from Mobile Phone using Tapatalk
 
Ok thanks, I updated, rebooted, and now have:

proxmox:/sys# pveversion -v
pve-manager: 1.8-15 (pve-manager/1.8/5754)
running kernel: 2.6.35-1-pve
proxmox-ve-2.6.35: 1.8-10
pve-kernel-2.6.32-4-pve: 2.6.32-32
pve-kernel-2.6.35-1-pve: 2.6.35-10
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-11
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-3
ksm-control-daemon: 1.0-5

Have the same 2 Server 2008 R2 SP1 systems and Win 7 64-bit SP1 systems booted, let them sit idle for an hour and still not sharing any memory pages:

proxmox:/sys# cat kernel/mm/ksm/pages_sharing
0
proxmox:/sys# cat kernel/mm/ksm/pages_shared
0

proxmox:/sys# uname -a
Linux proxmox 2.6.35-1-pve #1 SMP Tue Mar 1 13:18:55 CET 2011 x86_64 GNU/Linux
 
You packages looks right now, KSM should working as soon as 50 % of your physical RAM is used. How much RAM do you get in your physical host and how much do you assign to your KVM guests?
 
Oh, I didn't know that I had to use 50%+ of the physical ram before KSM is used. I have 16G of physical ram in my server, with it running proxmox serving a 512M linux host, 2 2048M Server 2008 R2 SP1, and 2048M Win7 Ultimate SP1. So I'm at 6.5G of ram for my hosts + however much ram proxmox uses, so that is less than 8G. Thanks for the information. I do plan to add more VMs in the coming days.
 
I have upgrade to Proxmox VE 1.8. The old virtual machine (OpenVZ container) works fine.
But if i create a new OpenVZ container with the same model (ubuntu 8.04 standard), the apache2 server use about 400 M ram by default.

My configuration is:
proxmox1:~# pveversion -v
pve-manager: 1.8-15 (pve-manager/1.8/5754)
running kernel: 2.6.32-4-pve
proxmox-ve-2.6.32: 1.8-32
pve-kernel-2.6.32-4-pve: 2.6.32-32
qemu-server: 1.1-30
pve-firmware: 1.0-11
libpve-storage-perl: 1.0-17
vncterm: 0.9-2
vzctl: 3.0.24-1pve4
vzdump: 1.2-11
vzprocps: 2.0.11-2
vzquota: 3.0.11-1
pve-qemu-kvm: 0.14.0-3
ksm-control-daemon: 1.0-5
 
I don´t think that this is related to the update of the Proxmox VE host (what did you use before), check the container.
 
i quote from http://www.lowendbox.com/blog/reduce...i-thread-apps/

Just a small tips for those trying to run multiple threaded applications on OpenVZ.
Personally I code quite a few multi-threaded applications in Python (as some things are just too hard to do asynchronisely). Very often a 6MB RSS application would eat up close to 100MB of VSZ. As one of the most important metrics on OpenVZ — not “guaranteed memory” but “burstable memory”, i.e. privvmpages — is counted on how much your processes have allocated, you’ll soon find your application, which actually only use 6MB of “real memory”, quickly died on your 64MB VPS with 128MB of burstable memory.

I have upgrade to Proxmox VE 1.8 from 1.7
Only new OpenVZ container have the problem with memory.
I used 3 different container (ubuntu 8.04, debian 6, centos 5.2) and the problem with apache allocation memory is the same.

best regards,
michele
 
which apache2 do you use?

try apache2-mpm-prefork (instead of apache2-mpm-worker)

Code: 
apt-get install apache2-mpm-prefork
 
Hi,

I would like to update proxmox from 1.6 to 1.8, should i do an update to 1.7 first or can i safely go for 1.8?
Also, what is the best method to update a running cluster with iscsi SAN?
Updating nodes one by one first and then the master? Maby adding a 1.8 node extra to move machines so if something goes wrong with the update, it is not a big deal to reinstall the node fast?
 
just update to the latest 1.8, start with a node.
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back