Search results for query: memory usage

Hello @fiona . Thanks for you answer. Disk space is not even close to be used on that node: # pvesm status Name Type Status Total (KiB) Used (KiB) Available (KiB) % local dir active 3576569984 1040519040...

...In there, it seems that LXC memory usage is taken via PVE::LXC::CGroup->new($vmid)->get_memory_stat(); AND FINALLY.... This is the file of interest...

The horizontal bars have the same length although If I move my cursor to the first bar, usage: 21.90%, second bar: 19.44%, third bar: 4.95% As an enhancement, it would be nice to see the percentages as well. I assume if memory usage is too much, the color will change to red. PDM: 0.9.4 BETA

Hi @fweber, thanks a lot for your interest here! I completely understand that the whole situation about such (more or less similar) symptoms is misleading. Even for me, and for many others. Disclaimer: all our systems are tuned to maximum BIOS/HOST/GUEST performance, so no dynamic...

...which, if I interpret it correctly, suggests that proxmox should be using the value from /sys/fs/cgroup/lxc/119/memory.current for LXC memory usage. (119 is my LXC id) cat /sys/fs/cgroup/lxc/119/memory.current on the host (and cat /sys/fs/cgroup/memory.current within the LXC) both report...

...and error but I think you have the right idea in general but please test this before assuming it will work well in production. The rate that Proxmox takes away memory heavily depends on the speed that the total memory usage grows on the Proxmox host (when getting above the configured threshold).

This means, min memory in my case shouldn't be lower than the "base need", so no lower than apporx 1.7 GB as if it would be lower PVE could "steal" it from the VM with unpredictable results?

.... Make sure the min value is enough for the VM to function and the VM can handle a fast memory reduction (or memory usage increase as seen from inside the VM). Proxmox does not negotiate with the VM about the memory! It just takes it away the amount it calculated as described in the manual.

We have a Windows Server 2025 VM that has hung or crashed a couple of times over the past few months, requiring a reboot of the VM to recover. This is running on Proxmox VE 9.1.1. What I've checked so far: It seems to happen during a quiet period between 4am and 8am, with no scheduled events...

The reported memory usage of a VM in its summary and graphs includes RAM used by caching inside a VM. The reported memory usage of a node in its summary includes RAM used by caching inside VMs and LXCs. The reported memory usage of an LXC in its summary does not include RAM used by caching...

...Disk controller : SCSI (VirtIO SCSI) Host specifications : Intel Xeon-E 2388G, 64gb Symptoms Crash pattern : VM experiences high memory usage System starts heavy swapping I/O operations slow down dramatically SCSI timeouts appear in logs (not always) System becomes unresponsive and...

Same issue on my test cluster and another quick one i threw together to confirm. Issue carries on https://forum.proxmox.com/threads/proxmox-virtual-environment-9-1-available.176255/page-2#post-818562 Note, zero hardware issues or limited bandwidth between nodes, have had no issues prior to...

I am brand new to Proxmox. I have put together a server using parts I had laying around. I did buy some NVME drives and RAM. It is an Azrock X299 Taichi Motherboard. I have Quad Channel Memory going at 2400 with 4-32GB sticks of RAM for a total of 128 GB of RAM. I did purchase and install in...

Same hiere!. Screenshot from "inside" pfsense vm web frontend (low Ram usage) Screenshot from Proxmox 9 host (same time, indicates full RAM suturation)

Just an intermediate update: while I'm quite sure that at least my latest Patch 3 is more than competent and production-ready candidate, in the hunt of another WS2025-related problems on PVE I found a whole bunch of another threads about the same: 1) Completely saturated guest CPUs since the VM...

Looking at our prod cluster, MS Defender is taking up 1.5 CPUs per node, they has 64 cores so it's not nothing, but it's perfectly acceptable. We also have Rapid7 XDR on the nodes, which is mainly shipping logs, it doesn't show up in Top. We exclude the kvm processes, from Defender so there is...

Which impact on performance, cpu load and memory usage did you observe? Since I think it would be a good idea to cover the implications of installing such tools in the documentation I filed a bug on it: https://bugzilla.proxmox.com/show_bug.cgi?id=7035

...Honestly I'm completely lost at what it could be. The logs produce absolutely no errors before hanging and I don't see anything odd with memory usage, CPU usage or anything like that. Nothing out of the ordinary happens and there really isn't a trigger that causes it. The memory is quite...

Ich auch, sie haben aber das Problem potentiall angreifbar für eine sogenannte side-channel-Attacke zu sein: Die Frage ist natürlich wie man das bewertet, bei mir im Homelab nutze ich KSM sehr gerne, in Endeffekt habe ich da ja keine VMs, die ich nicht selbst angelegt habe und wenn erstmal ein...

...'set_password' failed - unable to connect to VM 103 qmp socket - timeout after 50 retries TASK ERROR: Failed to run vncproxy. And Host memory usage is 24.55 GiB (I only allocated 24GB). dmesg: [104.838121]vfio-pci0000:01:00.0:resetting [104.838196]vfio-pci0000:01:00.0:resetdone...