If everything works as expected with a previous kernel, an option would be to install PVE 9, pin [0] the kernel that works (i.e. 6.14) and then upgrade to PVE 9.1.
If it works, you could pin the same kernel on the rest of the nodes before...
I did not dismiss anything, I just try to understand your odd accusations, given that nothing changed for your existing PVE subscriptions.
You still get exactly the same value of our lowest subscription tier you choose to pay for, nothing more...
Well you could also think that it's bargain for enterprise environments that it's enough to have a support subscription for all your PBS and PVE nodes to have PDM without the nag and access to the enterprise repo instead of having to pay for PDM...
Same here. Using VE 9 with an HP DL 380 Gen10 and a RAID-Controller HPE MR416i-p Gen10+
May thats related to this: https://bugzilla.kernel.org/show_bug.cgi?id=220693
Rollback to 6.14 resolved it for now.
Sorry, I misunderstood. In that case you can leave it.
Sure. So Proxmox uses the good default of 16k volblocksize.
That means that all your VMs ZFS raw disks, are offered 16k blocks.
Now lets look how ZFS provides 16k blocks.
You have RAIDZ1...
I would recommend you to do
- Backup the VMs
- Backup your Proxmox settings
- destroy, reinstall Proxmox
- use mirrors!
- reimport the VMs
I would not use 5 drives as a RAIDZ1. With the default of 16k volblocksize you only get 66% and not your...
Same here, but with fully updated PBS 4.1 and enterprise repos. The server is an HP DL360 Gen10+, and the RAID controller an HP MR416i-a Gen10+.
When the server hits the issue, we have to do a hard reset since some processess get stuck in D...
I just did this yesterday, using the Proxmox GUI. YMMV I suppose, but since I added the new drives first, what I did was:
Out the OSD. This will start to rebalance in the background but all PGs remain blue or green. (blue I believe was due to...
This is what I've already suggested in my original post:
Yesterday evening I made some waves to finally get some attention of the maintainers (I've tagged them at least few times in the manner: "maintainers may decide" - last attempt was in...
Perhaps the Proxmox team could consider building its own version of virtio drivers with its own installer, signed by Proxmox. This would allow for faster patch deployment, as is done for other subsystems (ZFS, etc.).
@fweber