Search results

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...

Maybe this post can help https://forum.proxmox.com/threads/rrdc-and-rrd-update-errors.76219/post-345702

now it is clear to me. As an admin i still call such a session albeit not based on a session-ID it does use a form of session identifier (ticket, right ?) Time based or not, as long as connectivity is permitted a session exists, although here purely in an permit window based on what i assume is...

Thanks for explaining. If i understand correctly this implies the signature is valid across service restarts and no new tickets have to be issues after restart ?

Not even the session-id generated for the cookies ?

There you go :) Well, restarting a service does more than just that. It also reinitiates sessions and regenerates relevant ID's. Much same as clearing cookies. Could it be browser and services have a proxy in between which strips or rewrites part of the header ?

is this not because of an accidental cache clear or session time-out ?

awesome you want to try it, keep us posted. in my experience disabling the 'network-adaptive display quality' if you're working on a home network and setting ' request a specific framerate' to '60FPS' may also help. As does sliding the quality slider. Note you have to connect to the session to...

The 60 FPS framerate is normal for modern remote desktop software. nomachine.com delivers exactly that, with GPU acceleration included.