Recent content by monkfish

Ah now I thought but didn't write that, its still a method to solve the issue of whether or not the drive is shown on stock Debian, if it is then all tings point to drivers. cheers for reminder must make my posts clearer Happy Proxmox!

I had previous dealings with this card, once you get over little nuances then a reasonable replacement for the Broadcom MegaRAID 9560 series. Hetzner always used to have the Megaraid cards, at the time I was lucky enough to get battery backup as well. I am fairly sure the linkdata card is...

Joining in with the following observations; over a year since last driver refresh, there have been driver updates but no binaries released until now. Upstream changelogs minimal to say the least. This is Not the fault of Proxmox team. We know older versions of windows are dropped from support on...

No Not rude, just asking the niche case? From 4 years ago?

Wheres the thumbs down on this forum for, umm, some posts. Askin' like. Just askin'. Exactly What is prohibiting an installation of Proxmox from either source ISO or Debian and overlay on top? Perhaps the superb devs at Proxmox have better things to focus on that a niche case. Respect to Proxmox.

I concur. Thanks team! I am using nested virtualisation on my dev environment to provide a full-on hyper-v test lab. This does help. Anecdotally (with absolutely no graph evidence to back this up for I am a doofus and not yet finished my monitoring!) a side-effect of specifically...

Keep in mind what ARC is when it comes to ZFS - "Adaptive Replacement Cache". Thus caching already happens in main memory. I dug through my previous notes, there's mention of it here https://forum.proxmox.com/threads/vm-virtual-hdd-cache-settings-for-ssd-backed-zfs.114928/ but I have in mind...

Might I suggest you also review the caching you have set on the VM disk? In OP I'm reading that the subsystem is ZFS. Its my undertanding the recommendation is not to set any caching on VM disks themselves when using ZFS to avoid precisely what your seeing ... CPU lockups, duplicate data writes...

Hello, got me an odd one here. Within a last few batch of updates I get a massive negative CPU readout when rebooting any of my containers. Once restarted it settles down but I wouldn't have expected to see this level of oddness. Systems hardened in accordance with CIS but I doubt this causes...

@fiona Thanks for that - I see pve-qemu-kvm-10.2.1-2 in pve-test as of time of writing. I had 2 updates on my test lab whether or not the other one is applicable to this bug or just coincidence wouldn't know. For those that used workaround from @uzumo to hold back pve-qemu-kvm, remember to...

Well... not so much freezing but I have something - non-issue I am proper pushing that box to its limits, its only a dev box. There is no bug or no reason why other than I have, purposely, crammed that box full. This is not on Debian, Proxmox or anything except my empty wallet to add another...

Here you go - in case you've not already found it this is courtesy of @uzumo in this thread...

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...