Search results for query: memory usage

Interesting. Here is mine for comparison. No zfs on this box all lvmthin. can find one if more results desired. Initial findings after reinstalling pve-qemu-kvm 10.2.1-1, uplift of all Windows VMs to pc-q35-10.2 and flipping aio=threads on all disks. Proper shutdown and restart conducted of all...

I moved some VMs to another freshly setup host and could remove the USB network adapter. With these actions, the memory usage dropped to around 50%, kernel logs during backup, see below. But the VM connectivity issues are still there. Mar 27 00:05:05 proxmox4 kernel: usb 2-7: reset SuperSpeed...

...I run Gatus to monitor them and the times of outage is not the same for all VMs. Also the host does not become unreachable. Memory usage is pretty high: 87.23% (54.24 GiB of 62.18 GiB) is in use. I lowered this a little to check if this makes the situation better. Thx for you insights.

If can really confirm that memory allocator impact librbd latency. you can with a simple fio 4k randread or write. my last qemu patch from 2023 : https://lists.proxmox.com/pipermail/pve-devel/2023-May/056815.html default malloc: 60k iops 4k randread tcmalloc : 90k iops 4k randread (can be...

...run into this. I think this happens because macOS doesn't have a balloon driver. I ran into the same thing where OS X always shows 100% memory usage. In my adventures with OS X on prox mox I ended up writing my own guest agent and as a result accidentally fixed this issue (at least it's...

First, some context on why this matters even for a single-DC setup. Without `rbd_read_from_replica_policy = localize`, every read goes to the primary OSD regardless of where it lives — even if a replica of that object sits on the same hypervisor node as the VM. The network round-trip is always...

Fleecing on or off does not make a difference. There is no PBS instance involved. Storage is single NVME (2TB KIOXIA XG8 Series) with LVM volume. Graphs below definately show the issues, mouse cursor is at start of backup job. Memory usage is also pretty high: 87.23% (54.24 GiB of 62.18 GiB)

I am novice into Proxmox pass-through and have adopted unprivileged, no nesting LXC container as my go to for services and what not. Trying to get a humble NVIDIA T400 4GB working with Jellyfin was a complete mess trying to follow posts so this is how I got it working novice style: Proxmox...

...lightweight external frontend So I wrote this in Rust to keep it: lightweight fast easy to move from one Proxmox host to another low memory usage low runtime dependency footprint safer than glueing everything together with shell scripts Current features terminal live dashboard host...

Host is using software rendering, not using host-owned GPU for vm guests configured with virtio-gpu/gl. This might be just a normal graphics driver issue, but I've exhausted my minimal knowledge on the subject and from all the net searching, I have the impression that basic virtio-gpu/virgl...

...meant with the error message lacking context. This is not intentional needs improvement. Not from the top of my head, but you could check the max memory usage when running the client with the limit set, running into the limit. this will at least give you an estimate of what doubling might imply.

...The pbs-client needs to hold a list of directory entries and their stat metadata [0]. The limit is there to protect against excessive memory usage for environments where that is not acceptable (e.g. container backps in PVE). [0]...

...in Dec of the same machine.. That is also acting the same way now.please let us know how we can recoover the VM? it was very important machine. In the summary the CPU and Memory usage was showing very high but there wasnt any unsual acticities as per our knowledge. after thatmachine is not...

Hi everyone, I've just released an unofficial early-access Proxmox VE kernel based on Linux 7.0.0-rc3. This is not an official Proxmox build — it's a custom rebase on the latest Ubuntu kernel sources with Proxmox defaults and local-build tweaks. Full source and GitHub release here...

Hmm, interesting point. I hadn't noticed that pattern and don't reboot my guests often, which is why I haven't responded to provide logs yet. I'll have to keep an eye on this... the node where I run the most guests is usually above 80% memory usage.

...do all kind of "act smart" intelligent thingy although i turned on things like SSD, NUMA etc at the disk level settings in Proxmox VE. Memory usage was being reported at 100.74% consistently at the summary but within the Windows console itself, anti malware is taking about 200-250MB ram...

Thanks for your input! That's a valid point regarding the total LXC swap usage versus the available swap on the host. I'm still not entirely sure if that's the primary cause in my case, so I'll keep investigating other possibilities as well and see how it goes. Appreciate the advice!

Thank you for your support. After updating the BIOS, the issue is reversed: RTX2080Ti is recognised, while RTX5090 is not. After some try and error. I managed to make everything work by using OVMF BIOS in the VM. Please mark this post as resolved! nvidia-smi Wed Mar 4 09:40:36 2026...

Hi, I have a VM running Windows Server 2022 with RDS farm + FSLogix. Environment: Proxmox VE 9 Kernel: Linux 6.17.4-2-pve (2025-12-19T07:49Z) Host CPU: AMD EPYC 7443P (24 cores, 1 socket) VM CPU: 24 vCPUs (host type) VirtIO drivers version: 0.1.285 Issue: At random moments the VM CPU usage...

...have enough overhead. However, this issue has already happened twice now: whenever that high-load CT experiences a spike and its memory usage exceeds 90%, the entire PVE physical host crashes abruptly without warning. I have monitoring alerts set up, so I receive notifications just before it...