Search results

In that case "host", but normally we use "Default (kvm64)", and the behaviour is the same. source:~$ pveversion -v proxmox-ve: 7.4-1 (running kernel: 5.19.17-2-pve) pve-manager: 7.4-15 (running version: 7.4-15/a5d2a31e) pve-kernel-5.15: 7.4-3 pve-kernel-5.19: 7.2-15 pve-kernel-5.4: 6.4-20...

Hi, we still have the problem, here are some messages from a VM that got stuck: kernel:[2261815.282065] watchdog: BUG: soft lockup - CPU#2 stuck for 22s! [JournalFlusher:870] Message from syslogd@graylog5 at Sep 11 14:13:07 ... kernel:[2261815.283198] watchdog: BUG: soft lockup - CPU#0 stuck...

Hi, we still noticed a strange behavior, after restarting ceph.target: 3 and only 3 VMs out of 200 still suffer the problem that backups crash and crash the VM itself. In particular, these are VMs with windows 2019 os and a disk (P) dedicated to the 15GB pagefile, a configuration different...

Hi, I confirm that problem is still present on ceph version 16.2.10 pacific (stable) and that tha solution worked for me, too, for one VM. As soon as I get the OK to proceed with others I'll do. Thanks for writing down your solution and to floh8 who pointed me to this thread! Matteo

Hello, since some weeks some VMs (5 over 250) have problems during backup on PBS. We have the same problem on any cluster node we move the VMs on: What we can see but that we can't fully comprehend is that these VMs at a certain point (always the same) get stuck, that is both backup and the...

... until few weeks ago: VMs with CPU at 100% While kernel 5.19 seems it fixed the original problem, it also seems it introduced another one that we didn't have in previous versions of PVE on the same hardware. Do you know if by chance what solved the problem of live migration in version 5.19...

Thanks, yes, we installed a 5.19 kernel just by suggestion in these forums to solve the problem of migrating VMs to nodes with different CPU frequencies: Live migration problems between higher to lower frequencies CPUs While this seemed it fixed the problem, it also seems it introduced another...

Hi everyone, we are experiencing a strange problem; since the update, a couple of months ago, to: occasionally we find some machine with 100% CPU and completely unusable. We found that just by live-migrating th VM to another node it starts working again, without reset. Has anyone had...

Yes, I thought it, too, but the problem is that it happens with almost all the VMs turned on from a certain point on (so with those turned on before the problem occurrd, at least it seems). However, it also happens when the minimum RAM is raised to 8 or 16 GB out of 32: when processes that...

Yes, "out of memory" inside the machine. Also, with "info balloon" in monitor we see that "actual" memory is low and processes on guests do not start or get killed with OoM error. Also, on windows machines we have the same situation in which we do not have all configured RAM available. This is...

In fact, we opened the ticket because it seems to us that it already occurs at 50% use and not at 80%.

Still having the problem: why ballooning occurs so early and so heavily?

Hi, I can finally confirm that from the tests done so far, with all nodes at kernel v.5.19.17-1 and PVE 7.3.3, the VM migration works perfectly! Thanks and have a good day, Matteo

Thanks, I'm not a ZFS expert, but as far as I can see ARC usage is low: # arc_summary -g ARC: 4.3 GiB (0.9 %) MFU: 3.9 GiB MRU: 196.7 MiB META: 440.8 MiB (377.9 GiB) DNODE 107.5 MiB (37.8 GiB) +----------------------------------------------------------+ |...

Hi, we experience problems about RAM, expecially on a node that appears to not have very high usage: Despite this we note that some machines go "out of memory": Any ideas? Regards, Matteo

Hi, we didn't test it because we prefer not to stop the new node with all VMs onto it to update it. Now the plan is to see if we can use other nodes to complete cluster upgrade without any restart of VMs, updating them to kernel 5.19. It will take a couple of weeks, but I'll keep this post...

Good evening, we experience problems when migrating to hosts between a host with CPU: 64 x Intel(R) Xeon(R) Gold 6326 CPU @ 2.90GHz (2 Sockets) to a host with CPU: 40 x Intel(R) Xeon(R) CPU E5-2650 v3 @ 2.30GHz (2 Sockets) No problem in the opposite direction. On both host we have the same...

Yes, this is precisely the problem, it seems to me that it already happens to us at 60%. The image indicates that there are 43.248.196 KB out of 128 GB of RAM occupied by a dummy process created by ballooning. Thanks, we plan to upgrade to Proxmox 7 shortly. # info balloon balloon...

Good morning, on a node of our cluster with 1TB of RAM occupied at 60% we have a problem with ballooning. Specifically, on a windows server 2019 VM with 128GB of RAM: On the node with Proxmox VE 6.4-13 with Community subscription we see this: $ free total used...

Thank you very much!