The resolving commit for mentioned vioscsi (and viostor) bug was merged 21 Jan 2026 into virtio master (commit cade4cb, corresponding tag mm315).
So if the to-be-released version will be tagged as >= mm315, the patch will be there.
As of me...
Hello!
We encountered a similar NCCL issue with CUDA error: operation not supported.
Our H200s were managed by vGPU. We uninstalled the vGPU drivers (on the Proxmox host and the VM) and installed on the VM the latest Nvidia Linux driver. After...
I did exactly what is described above with 8 hugepages of 1GB
cat /proc/cmdline
initrd=\EFI\proxmox\6.17.4-2-pve\initrd.img-6.17.4-2-pve root=ZFS=rpool/ROOT/pve-1 boot=zfs intel_iommu=on iommu=pt transparent_hugepage=never default_hugepagesz=1G...
@fweber @fiona
Is there any progress on NVMe disk emulation?
FYI:
https://techcommunity.microsoft.com/blog/windowsservernewsandbestpractices/announcing-native-nvme-in-windows-server-2025-ushering-in-a-new-era-of-storage-p/4477353
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
Check this Post in thread 'Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive"'...