@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"'...
And @fweber, of course I understand the omnipresent DEV buzz, so all is OK, just please, there should be some regular "bumps" in the rising threads from the Proxmox staff. We, as a community, are quite mighty and capable, but definitely not...
@JonKohler
That was a very informative KFM Forum presentation. Thanks for all the RTFM you did on that one, especially the fine print.
Can you comment on where the resolutions are at today? Still making their way into upstream KVM / QEMU I...
Just an intermediate update: while I'm quite sure that at least my latest Patch 3 is more than competent and production-ready candidate, in the hunt of another WS2025-related problems on PVE I found a whole bunch of another threads about the...
I've already completed the full driver downgrade, so let's see what happens. I hope the yellow triangles and the damn IO error stop. I’ll keep you updated.
If you use virtio drivers 1.285 check this thread: https://forum.proxmox.com/threads/redhat-virtio-developers-would-like-to-coordinate-with-proxmox-devs-re-vioscsi-reset-to-device-system-unresponsive.139160/post-814067
As far as I know, profile type C is best suited for AI (requires a vCS license, but works with a vDWS license as well).
Unfortunately, I have no other ideas.
Subscribed to the post.
I see the AnonHugePages increased when starting the VM, but the default is set to 2M. Apparently this works if you don’t need IOMMU. If I needed to pass hardware /GPUs through then you’d need those to be static like your config AFAIK. That being...
Please check
cat /proc/meminfo| grep Huge
In my setup I had to define:
hugepagesz=1G hugepages=N default_hugepagesz=1024M
Where N - is number of HP with respect to VM memory size
P.S as far as I know 1G and 2M hugepages cannot be combined...
To use giant pages (hugepages 1024Mb) u need:
- explicitly set fixed number of such pages in boot loader (/etc/default/grub or /etc/kernel/cmdline)
- set hugepages: 1024 in vm conf file (manually)
I would also recommend setting up numa topology...
This can be hard, because there's no clear initial condition. We have another two VMs with WS2025 and SQL2022, but there's a low traffic/load, so these errors/issues are quite rare and no service hangs so far.
But I'm quite sure that majority of...
In our environment, we use dozens of Windows Server 2019/2022, and we don't see any issues with version 1.285 drivers. However, there is only 1 server with the MSSQL database engine (2019, if I'm not mistaken), and I'm not entirely sure if it has...
Hi @Whatever, not yet. But I moved the focus on the thread I've been active since the last year: Redhat VirtIO developers would like to coordinate
In my view, the problem with the virtio github is the low/lower interest of the core (RHEL) devs...