All of the same symptoms as before, no need to repost. Just review the beginning of this thread. Hoping it is resolved in the next QEMU or Proxmox update. I've shifted almost all windows VMS off of AMD Proxmox hosts and set the remaining machines to no longer balloon as a temporary measure.
We are back to a memory leak on windows vms on AMD hosts.
I have the latest virtio drivers and have updated to QEMU 9.0 implementation, but the leak persists. There had never been leak on this server until a recent kernel update.
CPU(s)
24 x AMD Ryzen 9 5900X 12-Core Processor (1 Socket)...
It's definitely a memory leak. If you read through this thread in detail, you'll see the full symptom report -- meaning that if not corrected and memory pushes over 100 %, the machine crashes. Windows itself will report that it is using 95% of ram, but if you add all values listed in the task...
So, just experienced a memory leak on a 2022 server on an AMD CPU.
I installed the most recent baloon driver *.225 and it immediately corrected the leak, even without a reboot.
@_gabriel
VM Disk settings are all similar to this for the 2022 VMS. Write back
Finally an update to this, I only have some 2016 servers that oddly aren't affected and the rest have upgraded to 2022 and the leaks are gone.
With 2019 the leaks would constantly reappear every couple of weeks and were terribly annoying. Looks like MS was the fix on this one!
Yes. Just read this. Looks like the exact issue. I have restorted to running those guests without the agent. Just tested again a couple days ago and same problem.
The following is still an issue for some CENTOS8 (CloudLinux 8) vms running cpanel whenever the guest agent is enabled. Just tested again today and it crashed the VM requiring a qm unlock and qm stop before disabling the agent and starting it again. I know this isn't new, but wondering if any...
Bump. This is still an issue. I just tried a brand new install of Cloud Linux. Backups worked fine with the guest agent enabled... Then I installed cpanel. Now same problem. Totally freezes the VM and requires a stop and start...
Any chance we can find the cause and correct this?
The nodes and vms have been restarted to ensure they are on the latest version. I even have a node that is running the current test repository updates and I've run tests since that update yesterday and I am continuing to get qmp command 'cont' failed - got timeout errors that sometimes break the...
From my experience, I don't think the assumption that it is tied to high load is correct. I have done tons of huge VMs that had to start a new bitmap and they normally work. The most common problem will even occur on the first VM of a set under light load. Again, this started with Proxmox 7 and...
It is not 100% reproducible. Some machines do it more often than others, but it could be Centos, Windows, Ubunut, etc
Sometimes for 2 days no errors happen, then the next day 2 or 3 happen...
It just happened on a CentOS VM and it broke it and I am performing a reboot now.
I updated to 6.0.0-4. It just broke a centOS VM.
INFO: resuming VM again
ERROR: VM 9327 qmp command 'cont' failed - got timeout
INFO: aborting backup job
INFO: resuming VM again
ERROR: Backup of VM 9327 failed - VM 9327 qmp command 'cont' failed - got timeout
The machine was not under a large...
Here's one more from a server 2016 that isn't stuck, but is unusuable..
root@v2:~# VM_PID=21653
root@v2:~# gdb attach $VM_PID -ex='thread apply all bt' -ex='quit'
GNU gdb (Debian 10.1-1.7) 10.1.90.20210103-git
Copyright (C) 2021 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3...
This just caused an Ubuntu 20.04.03 Server to go to read only access. It hasn't caused a CPU spike in this case. The machine will have to be rebooted and fsck will have to be manually performed to get it running again..
Also, the servers were freshly upgraded to 5.11.22-4-pve and this...
Also, this occurred to one VM. It was stuck with 1 core at 100% since a backup at 19:00 last night and when I ran another backup set this morning, it caused the machine to drop to normal utilization and it never totally froze. When the machines freeze, it's almost always 1 core being stuck at...
Just got the following on a backup and the CENTOS VM got stuck:
INFO: issuing guest-agent 'fs-freeze' command
INFO: issuing guest-agent 'fs-thaw' command
INFO: started backup task '419428ab-7767-4fa4-ae1e-27bd5a539bcf'
INFO: resuming VM again
ERROR: VM 9327 qmp command 'query-pbs-bitmap-info'...
@Stefan_R I believe you are right, which is why I noticed some improvement, because that error was fixed, while this one has not been.
Load around 2-6 at the time of the errors... The server is under very light utiliziation and these are small incremental backups. It can occur on virtual...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.