Update with the bigger-VM test (VM 162, the original 6 TiB
problem case from my first post). Cluster: 12 OSDs, 3 mon,
HEALTH_OK, replication 3.
=== rbd bench (scratch image in pool_nvme_vm, deleted after) ===
| Test...
Der RAM ist bei diesem laut Hersteller (obwohl an anderer Stelle wieder steht, er würde S0s verarbeiten) nicht erweiterungsfähig. Die eingebauten 8 GByte x 4(?) sind langsamer als zwei Module zu 16.
Die TDP von 45 Watt bremst einen 8C16T aus...
Thanks @YG-Infra ,
File hash is good and I can boot from a Windows 11 ISO on the same device using the same USB stick. Not sure by Etcher and Rufus are playing up with this ISO. I'll keep trying and follow up on your recovery suggestions once I...
As it seems relevant here: We've been running our CI/CD for PVE9 with Kernel 7 since it was announced on the forum and have not had any issues.
Note that our testing is targeted at storage rather than networking functionality of the PVE.
Cheers...
Just noting later versions of PVE 8 and PBS 3 both have a NIC name pinning tool. We did that before upgrading.
Edit:
https://pve.proxmox.com/pve-docs-8/pve-admin-guide.html#network_override_device_names...
@dakralex Thank you very much for the answer! That clears things up a lot.
As for the modes, I think we will just need to try the modes and see what happens. TOPSIS sounds best for our production clusters as they are usually memory limited...
7.0 already contained the relevant commit upstream prior to it being cut:
https://git.kernel.org/linus/a664bf3d603dc3bdcf9ae47cc21e0daec706d7a5 (7.0-rc7)
Actually it's a known issue since Dec 24 2025...
=> https://forum.proxmox.com/threads/kernel-6-17-bug-with-megaraid-sas-hpe-mr416.178370/
It's the same issue type.
They also speak about memory leak with network card drivers, I guess they're...
It would be incorrect to say that 7.0 "is not affected". It is affected but patches have been released. Including in the PVE distribution.
Cheers
Blockbridge : Ultra low latency all-NVME shared storage for Proxmox -...
@EllerholdAG my staging clusters are running no-subscription repos and there the 5.2.0 pve-ha-manager is already available. I have yet to roll it out on the enterprise ones.
Hi!
Thanks for the feedback!
The load balancer takes both memory and CPU in account. Ad weighing, see the next paragraphs.
The load balancer can score the balancing migrations by either one of these methods.
The brute-force method (as in...
For reference, sent a patch for this already [0], no need for a bugzilla entry, thanks!
[0] https://lore.proxmox.com/pbs-devel/20260430135931.722979-1-c.ebner@proxmox.com/T/
Thanks for your reply. I managed to boot the server by
apt reinstall grub-efi-amd64
and added a corresponding fstab entry:
UUID=539B-6D66 /boot/efi vfat umask=0077 0 1
fix also found here
I have experience with SAS-connected tape drives/libraries as well as FC-connected disk-/flash-based storage arrays, but not with FC-connected tape technology.
However, for the two cases I can tell you something about, the answer is yes...
I installed a new kernel on one of my servers. It seems to be running well so far — I haven’t noticed any performance changes, but memory usage appears to have decreased slightly.