Search results

As i mentioned on my first post: i'm not using containers. I mentioned that specifically, to be clear that swapping is not related to containers, but to proxmox kernel. I also tested with swappiness = 1, result is same, still swapping.

So, does this mean that kernel will not swap at all if vm.swappiness is set to 0? What i'm trying to achieve is that kernel would not swap unless memory runs out. Be that swappines 0 or 1. Yesterday i checked again, if parameter is set (vm.swappiness = 0) then i disabled swap with "swapoff"...

This was true previously, when swappiness 0 meant that swapping will occur when physical memory starts to run out. Now, apparently, things have changed, according to several sources (including kernel code) this is no longer so (kernel 3.5 and above)...

Hi It seems like latest proxmox kernel does not honor swappiness parameter. Does anybody have same problem, or i'm just missing something here. (I'm not using linux containers) ZFS ARC is restricted to 8GB root@cd02 ~ # sysctl vm.swappiness vm.swappiness = 0 root@cd02 ~ # cat...

Update: Two days ago, one VM locked up again. Proxmox v 3.4-11 VM was 64bit debian 7 and disk was format=raw cache=none Relevalt data: Dec 4 08:15:41 zabbix kernel: [66812.896175] ata3.00: exception Emask 0x0 SAct 0x10000 SErr 0x0 action 0x6 frozen Dec 4 08:15:41 zabbix kernel: [66812.897001]...

Great, thanx. Converted disk to raw and i also changed cache=none Underlaying conf is RAID0 with SSD's, and seems that write speeds are pretty much same as was with cache=writetrough Now, we'll wait and see.

Hi Just had VM lockup for same reason. VM is Debian 7 and disk is qcow2 format. Can anybody confirm: does changing disk format to raw fixes this problem?

In addition, user permissions are not deleted when VM is deleted. if you did not delete user permission to VM, before you deleted VM, then these permissions are active on new VM with the id of VM that has been previously deleted. Be aware, if you have many users!!!