I believe that was a KVM bug that got fixed a few years ago.

Also, you need to pass through disks by ID (the current default in proxmox Gui) and not by /dev/sdX

Well many governments see their citizens as hostile actors, so its not really a change, is it?

Back luck Brian kernel developer.

You are absolutely correct. I am not sure I would be able to stay that diciplined for this long.

At some point, I expect they wont care about having an excuse and start escalating the violence anyway.

I am lucky not to be in america, and I am not in that position, but if an Ice agent does this to a pregnant woman in front of me, I am sure as hell going to do something emotional in that moment.

I am suprised we have not really seen crowds jumping small groups of Ice agents to rescue their neighbours.

My exprience with Trunas has been that ZFS does not like virtual disks. Especially when the Proxmox host also uses ZFS. Two layers of ZFS arc caching creates some memory issues. Setting the Host datasets to Metadata only may help.

But the most reliable method would be doing hardware passthrough of physical disks to the VM. It gets you most of the bare metal reliability benefits without having to commit the entire hardware box to one OS.

You may also want to disable memory ballooning in your VMs. It works well when you have lots of small VMs, but if you have a few large ones, it can cause issues if you overallocate Ram to VMs, beyond what the OS has available. I suspect it could also be interferring the zfs arc as well.

Lastly, check that your VM is set to use the “host” Cpu type. Freenas would likely benefit from having access to more CPU functions.