Search results

yeah, it went away and came back again. This truely a mess and left unaddressed. Somehow nobody knows where these messages come from, how to stop them.

This is in the back of my mind actually. Linux is infamous for not providing user sensible memory reporting. To consume all possible RAM is 'by design' on unix systems, however, to report it is a different matter. Linux systems free, VIRT, MEM%, buffers, cache are essentially used all the time...

Interesting. I only see that temporarily when i restart all VM. Things i will try in the future is to stop some non-essential VMs which i suspect may play a role in this behavior disable the ballooning service in the VM if it is running without ballooning enabled disable KMS learn more about...

Hi, Yes, this looks very similar to what i'm observing. Reasoning is ZFS reserves half of available RAM, looking at the memory consumption i have not found such to be so. Also, in your cases that would put the RAM consumed at between 57-58GB usage. What i'm considering is KSM may actually be...

To my understandig this is all because of configuration issues. You may have set a default which now negatively affects performance. Also, this is exactly what kvm=off means. Literally ever single instruction is emulated now, which is about as fast as it can go without kvm.

the "issue" is back, no machine is running with ballooning enabled. edit: Note the server was not restarted, just all the VM, as such ZFS memory consumption is possibly not part of the growing memory consumption. Afaik it is not because of the memory reservation reported in MEM but that...

Not my impression. It showed 10GB KSM with 67% reported use as well. For reasons beyond me, while updating the forum the reported memory rose to 79%. The total of VM assigned account for much less than 93% of RAM, roughly 47GB of RAM is configured for all VM combined. Note i have stopped a 4GB...

obvioiusly, as we spoke it had to go near 80%

That file /etc/ksmtuned.conf is pristeen, all entries are commented. Which probably has the same outcome as the configuration you mention ?

Interesting. Are you absolutely sure about KSM ? My system showed over 10GB KSM out of 80GB total with just over 65% memory usage.

My impression is the ballooning may somehow negatively interplay with KSM sharing.

Yesterday i restarted ALL VM without restarting the server and after disabling all ballooning for memory. I've not observed excessive memory usage since. Prior to the VM restarts the overconsumption of memory whas noticeable throughout all VM, not just the single one where ballooning was...

closing this topic, found i had posted before looking :-)

After more review i think i understand better. Since neither 'zpool status', neither 'lsblk' shows the actual nvme device in any way i assume my attempt at reverting my actions was succesfull. Maybe not yet visible at the time last time i looked. This means i can actually try and redo my prior...

Recently added an extra NVME drive to the system, using ZFS. After adding it i'm lost as what is happening. ZFS appears to have 'absorbed' it but i cannot partition it. There appears no way to undo it etc. I've definitely done something wrong but cannot progress, any pointers ?

Thanks :) Sadly, since ballooning causes more problems than it solves, i only use ballooning for just one VM. Even when disabled (now) memory is at 94% while effective reservation is around 65%

? ALL of them ? Somehow proxmox consumes consistenly more memory than allocated. It is normal after a reboot, after a few vm have restarted it builds up and only goes down again after a restart of shutting down all vm and starting them again etc.

yes, running ZFS, to my memory with low memory consumption configured. from a shell I run glances and notice the assign memory is for example 5GB but the VIRT memory is 12GB which is cumbersome as it is what proxmox appears to really consume in terms of resources instead of the 5GB assigned...

After being faced a few times with extraordinary memory consumption i took a look at the shell using glances. out of principle i never count on swap space and don't configure it since my use cases don't call for it. While the RAM assigned is correctly estimated proxmox/kvm decided to consume...

Yeah, i do remember a lot of noise as well. I think what you are now seeing is exclusively due to filesystem permission issues or non existent file. Try something like: touch /var/lib/rrdcached/db/pve2-vm/100 and see what happens[/CODE] Yeah, i do remember a lot of noise as well. I think what...