KSM on Proxmox 1.6

T

tincboy

Renowned Member
Apr 13, 2010
466
6
83
Thanks to Proxmox developers because of their new release 1.6
I can see in the roadmap of this version that KSM has been removed, but we are using it and we are very welcomed about it.
So isn't possible to use KSM in Proxmox 1.6? ( we really don't need OpenVZ at all ).
 
use the old kernel (2.6.32-2). we plan to have a KVM kernel only in future.
 
Tom,

Can you or the Proxmox team provide an estimate on the KVM only kernel release? Will it simply be the PVE kernel minus OpenVZ code and KSM enabled or will there be additional KVM optimization?

Thanks for all of your hard work.
 
Ninjix said:
Can you or the Proxmox team provide an estimate on the KVM only kernel release?
Click to expand...

no

Ninjix said:
Will it simply be the PVE kernel minus OpenVZ code and KSM enabled or will there be additional KVM optimization?
Click to expand...

We though about kernel 2.6.35 - but I am not sure if that is stable enough.
 
I did upgrade "accidentally" to proxmox 1.6 and now I have KSM off. I have like 4 same OS windows machines working under KVM using KSM and now I have the whole RAM occupied by them... I don't know If I can go back...
 
just install the KSM capable kernel, 2.6.32-2.

Code: 
wget ftp://download.proxmox.com/debian/dists/lenny/pve1.5/binary-amd64/pve-kernel-2.6.32-2-pve_2.6.32-7_amd64.deb
and

Code: 
dpkg -i pve-kernel-2.6.32-2-pve_2.6.32-7_amd64.deb
 
Hello, there is a security problem with this kernel i believe (the 1.5 repository did't get much love lately). Probably its time to add pve-kernel-2.6.32-4-ksm ;)
 
fortuik said:
Hello, there is a security problem with this kernel i believe (the 1.5 repository did't get much love lately). Probably its time to add pve-kernel-2.6.32-4-ksm ;)
Click to expand...
I feel that way :( I started to use massively proxmox with full kvm virtualization due to the KSM function but since 1.5 is obsolete is perturbing to stay there
 
We also had extreme staility issues with proxmox 1.5 and WIndows 2008 64bit vms which all went away with proxmox 1.6

Why dont we all put together some donations for the proxmox team and officially "order" a maintained kvm-only,KSM cabable proxmox kernel from them ? I perfectly understand that we all have to live somehow and need to be paid for our work.
 
as noted in the wiki, we do custom work if someone pays.

And yes, we need to get paid every day as we are really normal people here, need to eat every day :-)

Just a status regarding donation for a maintained KSM enabled kernel: € 0,0 - so there is place for improvements.

So it either looks no one is really interested or no-one know how opensource is working.

- Someone needs to do the work (maintaining a kernel branch is a lot)
- those who benefits should pay

will be interesting how much can be collected via this way but I am not that optimistic.
 
Hi Tom,

If you could give the community an indication of the target we need to collect to make this a reality I am sure those interested would be willing to make a contribution.

Leaving it as an open ended amount to collect does not help in my opinion.

Thanks,
Royce
 
I would do this but what do you expect? Just a one time kernel build or a long term supported kernel branch, fully tested and supported from us.

So you can imagine there is huge difference in costs between this. which one do you prefer?
 
Last edited:
I would suggest a kernel supported throughout the life of 1.6 as a start. Otherwise these email will start up again when you have to patch the kernel.

You seem to have indicated that ideally you would like proxmox to have one kernel supporting openVZ, KVM and KSM if possible but are constrained by openVZ. Is there anything that us, the community can do to help?
 
royceybaby said:
You seem to have indicated that ideally you would like proxmox to have one kernel supporting openVZ, KVM and KSM if possible but are constrained by openVZ. Is there anything that us, the community can do to help?
Click to expand...

Well, best would be if someone implements/fix KSM for OpenVZ.
 
Time ago I was planning just on forgiving the proxmox project just because the matter of the idea of keeping up the openvz.

At first I was very into on openvz but lately i don't like that solution as I would prefer to run a xen server, or a plain kvm with ksm server. But like some other features that proxmox give away and thats why i've kept into this project

With kernel 2.6.32 openvz was left behind, now it has come back. At the end there are two projects at last, kvm + openvz users (that mainly have ksm over windows machines and openvz for the rest) and the whole virtualization project under kvm. For example I did installed like 5 windows xp machines running just one single job based on one windows software that could not be run otherwise, but with KSM shared memory from all 5 servers where nearly the total of 1,5 with the positive thing of the relibility that if i did something wrong one one of the i could just wipe out that one maintaing the others

With openvz this is not a reality. Thing is there is a post just regarding this issues and a poll.
 
royceybaby said:
I would suggest a kernel supported throughout the life of 1.6 as a start. Otherwise these email will start up again when you have to patch the kernel.
?
Click to expand...
To become more concrete, I am willing to donate 500 Euro to the project of a maintained KSM capable kernel during the life of 1.6. I personally do not care if it supports openvz, I do not need that.
 
Just out of curiosity... How hard would it be for one of us KSM wanting types to take the Proxmox pve-kernel-2.6.32 source and disable the OpenVZ modules and enable KSM? Or maybe it would be easier to take the 1.5 version 2.6.32 source and apply its config to a vanilla kernel?

Just asking since this is FOSS. I really appreciate the quality and tuning the Proxmox team has done with their past kernel releases. Maybe a community maintained KSM kernel will alleviate the workload from Proxmox team members and let them concentrate their revenue making on officially supported kernels.
 
adoII said:
To become more concrete, I am willing to donate 500 Euro to the project of a maintained KSM capable kernel during the life of 1.6. I personally do not care if it supports openvz, I do not need that.
Click to expand...

yes, please do it. if you need an invoice for this donation pls contact martin@... directly. We plan to release a 2.6.35 kernel branch with KSM (no OpenVZ) - hopefully other users will follow your donation.
 
I'm a bit late for this new, but this is totally awesome for the community. Back to the power of KSM + proxmox base.

By the way, what means
pve-kernel-2.6.35 (2.6.35-7)
- update to Ubuntu-2.6.35-23.36

"update to ubuntu" kernel ?

can't this be a little bit "dangerous" for the system when coming from debian lenny based kernels in the past? My backup harddisk has gone to RMA, and I'm a little bit aware of making "big" modifications while i'm in this situ, so probably updating would not be a good idea, wouldn't it?

Regards
 
You must log in or register to reply here.
Top Bottom