Whatever's latest activity
-
WWhatever reacted to RoCE-geek's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with
Like.
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... -
WWhatever reacted to DerDieDas's post in the thread vGPU doesn't work with pytorch/nccl/vllm with Like.
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...
-
WI 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...
-
WWith the way things have been going, we won't see ZFS 2.4 integration until proxmox v10...
-
W@proxmox_team ZFS 2.3.5 has been released more than a month ago Any chance to get it integrated to PVE in a meanwhile? Thanks
-
WWhatever reacted to benyamin's post in the thread Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive" with Like.
I think v0.1.285 is still the latest release, so use v1.0.271 for now. AFAIK, the fixes have not yet merged.