hugetlbfs and proxmox 1.2

[mspock2010]

I used to use hugetlbfs in proxmox 1.1 (by passing the following parameter to the kvm: -mem-path /hugetlbfs using the args: line in the proxmox vm config). This was working just fine.

I have since upgraded to 1.2, and found that this no longer worked. KVM has since changed the -mem-path parameter to -mempath, and more seriously now requires the MMU_NOTIFIER to be supported.

Would it be possible to request that this be made a standard option in the Proxmox 1.2 kernel? And make that available via apt-get? I am sure that I am not the only one using the hugetlbfs option to optimize the guest vms ...

Thanks and best regards ...

 

[dietmar]

I used to use hugetlbfs in proxmox 1.1 (by passing the following parameter to the kvm: -mem-path /hugetlbfs using the args: line in the proxmox vm config). This was working just fine.

I have since upgraded to 1.2, and found that this no longer worked. KVM has since changed the -mem-path parameter to -mempath, and more seriously now requires the MMU_NOTIFIER to be supported.

That option is still not stable - that is one resason why we do not support it. Besides, I can find much documentation about that feature - where can I find it?

Would it be possible to request that this be made a standard option in the Proxmox 1.2 kernel? And make that available via apt-get? I am sure that I am not the only one using the hugetlbfs option to optimize the guest vms ...

AFAIK kernel 2.6.24 does not support MMU_NOTIFIER.

- Dietmar

 

[mspock2010]

Hi Dietmar,

Thanks for that clarification. In that case, I agree with you that it would be best for us to wait until things are more stable (as far as hugetlbfs and KVM are concerned) ... hopefully by the next version of Proxmox.

This is where I usually get my info on KVM ... http://www.linux-kvm.com/

Best regards ...