Search results

  1. A

    KVM allocate memory failure - buff/cache not released

    Hi @spirit, Unfortunatelly even after changing the cache to none, the buff/cache again reached a high number and no longer possible to boot a new vm even if there is free memory. total used free shared buff/cache available Mem: 47G 22G 458M 80M 24G 24G Swap: 30G 4.1G 26G Anyone else has an...
  2. A

    KVM allocate memory failure - buff/cache not released

    Hi @spirit, Thank you for your answer. Yes, I had write back cache enabled on Windows VM. I have changed to cache=none as you proposed. The Windows VM are used as CI, so lots of build/write. It is possible that it is the reason of the cache size. Otherwise all you VM disks use zvol. I will...
  3. A

    KVM allocate memory failure - buff/cache not released

    Hi, My proxmox have 47G Mem with 30G swap. It is using a local ZFS pool. After a time, the buff/cache of the node totally use all the free memory (unused by current VM) and makes impossible to start a new VM or run a backup. From what I understood, backup is the same as starting a VM. The VM...

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!

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!