Recent content by Kizu

Got CVE-2024-38540 at my pve8 new installation (btw its about #post-651061 ). When do you plan to upgrade kernel to >=6.8.12?

We have to use pve-kernel-5.13 at all nodes to avoid this problem:(

https://forum.proxmox.com/threads/is-issue-known-vms-can-stuck-after-live-migration.116315/post-503414

Good afternoon! On the VM-free cluster nodes, I made a kernel downgrade to pve-kernel-5.13 and did more tests. I will attach all the results here for clarity: pve-kernel-5.13 Silver 4210 -> E5-2650 v4 : VM OK Silver 4210 -> E5-2620 v3 : VM OK Silver 4210 -> E7- 4860 : VM OK E5-2650 v4 ->...

Yes, the server is old, but it is powerful and stable enough to do its job. When working with proxmox-6 cluster there were no complaints to it. And here before installing kernel 5.19 too. All firmware is updated to the latest available versions. The intel-microcode/non-free package was...

I have to admit that I was wrong in the first post due to the lack of tests and test equipment. The behavior of pve-kernel-5.19 is different and partly solves the problem and partly creates a new one with a CPU that did not have it. When upgrading nodes for tests, the problem with The problem...

Additional statistics. Each migration test was performed five times. The results are the same for each of the five migrations. Each node using pve-kernel-5.15. Each CPU is Intel Xeon. Silver 4210 -> E5-2650 v4 : VM STUCK, MANUALLY RESET TO RECOVER Silver 4210 -> Silver 4114 : VM OK Silver 4210...

pve402 - HPE ProLiant DL360 Gen10 - Intel(R) Xeon(R) Silver 4210 CPU @ 2.20GHz - pve-kernel-5.15 pve403 - HP ProLiant DL380 Gen9 - Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz - pve-kernel-5.15 pve406 - HPE ProLiant DL360 Gen10 - Intel(R) Xeon(R) Silver 4114 CPU @ 2.20GHz - pve-kernel-5.15...

Unfortunately we don't have detailed statistics because we only have a cluster of productive environments. If we take a short one, today migrations(10+ tests) from Dell R430 to Dell R910 were successful, and from Dell R910 to Dell R430 always(10+tests) with hangs. After downgrading on these...

Thank you for your reply. No, we are using CPU default(kvm64) everywhere for all VMs. We also do not adjust the cpu flag settings when creating the VM. Our infrastructure growth is gradual and unfortunately our budget does not allow us to make such large purchases of exactly the same hardware.

Good day! Cluster of 9 nodes proxmox-ve 7.2 Updated regularly. VM(windows and linux of different variations) based on KVM+CEPH. Observed and can easily reproduce the problem of the VM hanging right after live-migration. Main indications: - 100% usage of CPU cores allocated to the virtual...

Good afternoon! Any news on non-ascii characters and the above issues? https://bugzilla.proxmox.com/show_bug.cgi?id=2465 https://bugzilla.proxmox.com/show_bug.cgi?id=3005 We are using pmg7, and issue is still exists.

Thanks. Will wait.

Thanks, but this problem, as I can see, not only with ldap. With user-management(first spoiler), with mail filter(second spoiler) for example. Sometimes /api2/json/* returns not utf encoded characters https://10.205.255.2:8006/api2/json/access/users {"data":[{"username":"root"...

Good day. Got some troubles with PMG WebUI and Cyrillic characters. Now tested at our production pmg/6.3-4(with subscription) and fresh installed 6.3-4(without subscription). This problem was in the past, but we decided report it now.