Search results

I'm back I had some time recently to make tests, So yes, it works ! Same process on my host with 32GB of physical RAM: Start VM1, run stress-ng to take 100% (20GB) of RAM, stop stress-ng Start VM2, run a command that take slowly 18GB of ram by 10Mb/s (command : #</dev/zero head -c 18000m | pv...

I'll don't do overprovisionning but I have a small hosted server with soft raid (that's why i'm trying proxmox over vmware) with small amount of RAM (32GB) There are some important servers there and I don't want one of them to be killed that way for some RAM MB if I'm doing a small task that...

Ok i will do some further tests and i'll put some info here when done. thanks for your help @dcsapak

@dcsapak is saw this response already, but i have had other related questions earlier in this thread : Are you saying that if an app increases ram consumption very slowly, the feature will work then ? thanks

@Dunuin I don't use ZFS (i guess) i don't have any pool configured @dcsapak yes I know that thanks. Then why ballooning doesn't work when the ram is at 80%, then 90, then 100% (then pve kills my VM)

Hello, thanks for your reply ! I'm not using pci-passthrough for my test. I'm looking for replace my ESXis at work and I wanted to try the feature which btw works well on vsphere. Is there some tuning on proxmox about this ? If the feature is not fast, then it is not usable. Today test : RAM...

anyone ? I guess I don't use ZFS as pool list is empty. i'm with lvm-thin

Hello Guys, I'm new with proxmox. I have installed latest PVE on a small server with 32GB of physical ram (swap disabled during tests) I have seen many thread about this but I can't manage to get the ballooning memory working I have two guests (debian11) qemu-guest-agent installed and active...