Recent content by monkfish

With respect, disagree - yes there is an issue but seemingly cosmetic. There is a suggestion that if you dont enable iothreads then you're not even affected. Discussed elsewhere - its "test" repo for a reason. Yes there's that issue but early adopters also have a chance to test what else they...

Running great on test lab, small cluster of Dell 7070. CPU(s) - 8 x Intel(R) Core(TM) i7-9700T CPU @ 2.00GHz (1 Socket) Kernel Version - Linux 7.0.0-1-rc6-pve (2026-03-30T09:17Z) Boot Mode- EFI (Secure Boot) Manager Version - pve-manager/9.1.7/16b139a017452f16 No ZFS here, all LVM (thin volume...

Sorry, I'm out. All of the above is on you. Who told you to implement the "test" repository in "an enterprise-grade environment of this scale". It is not published in either pve-no-subscription or pve-enterprise repositories. I don't dispute you experienced an issue - however remember one...

Inneresting! I did not have that occur on mine. For sure the proxmox team will identify the reason why - lets remember this is a package published to test so those of us brave enough to use that will know the caveats. I reckon you might want to limit your 47 servers to a small subset exposed to...

Excellent! Thing is, as alluded to previously, I dont actually think its increased io. I'm not the worlds best at iotop but I wasnt seeing any difference - only in the realtime bar i/o delay and the io pressure stall graph. Good luck hunting, happy to test and/or give any other logs you might...

Interesting. Here is mine for comparison. No zfs on this box all lvmthin. can find one if more results desired. Initial findings after reinstalling pve-qemu-kvm 10.2.1-1, uplift of all Windows VMs to pc-q35-10.2 and flipping aio=threads on all disks. Proper shutdown and restart conducted of all...

Thank you OP for testing and workaround! Same experiences on lesser hardware, small cluster of Dell Optiplex 7070. Unfortunately for me it coincided with research on zswap implementation so spent time eliminating that as a symptom first. For me, applying workaround returned io state and cpu...

You know what? I did actually log a ticket with detailed information. Turns out there was a very old (2021, 2022?) ticket that had precisely one line it it, logged against version 7 with zero activity. More up to date ticket closed as duplicate against this one which has not been touched in 4...

Ta muchly. I'll be honest and say I looked, didnt immediately jump out at me hence the above. Cheers for pointer, will post.

Hello, just a small one. Any chance of adding a reboot button to the NoVNC console like right-click from main webgui? Also maybe align descriptions on the two menus, assuming of course that "stop=hard stop", "hibernate=suspend" and "reset=hard reset". Just a minor thing to improve usability...

Hi Dominik, I should have perhaps phrased that better or logged a ticket before. My bad. Its specifically PBS installed on top of Debian that yields secure boot issues. Pretty much, if you perform a Debian install with custom partitioning with a nod to hardening compliance on partitions then...

Said it was minor - workaround is as per other installs - after configuring repos and updating boot shims from proxmox repo, we don't reboot until PDM install complete including kernel. This allows my machine to remain with secure boot enabled. Still a discrepancy over proxmox kernel installing...

I usually do all my Proxmox installs on top of a Debian deployment, that way I can customise disk partitioning etc. I am happy this works for me. Sometimes I'm keeping the default kernel to work around secure boot issues (PBS in particular - wholly operational with default Debian kernel and...

Gem of an answer thanking you indeed! Lost a previously deployed LXC for reasons of I am stupid, went to deploy new one hit exact issue. At time of writing a few months after the above, this fix appears to be the only current permanent solution and also of time of writing Proxmox itself does...

Hi Fabian, thank you for your reply Same as you - prime256v1 with ecDSA however pleased to report now working, may have been spurious line space or similar particularly when constructing .pem file. Will do thanks for confirming it fails. So I went back through manual copy steps, with .key and...