Recent content by Whatever

@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

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

Try, check and report

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.

Did you chose correct vgpu profile and set Nvidia license token in vm? Do you mind to show nvidia-smi nvidia-smi -q From vm?

Check this reply: https://forum.proxmox.com/threads/correct-vm-numa-config-on-2-sockets-host.173595/post-807464

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 (once again check /proc/memory)

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 in vm config file (manually) - check PVE docs With...

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 been updated to the virtio drives version 1.285...

Have you fired bug report on virtio github?

Thank It's all clear now. Thanks.

Good day Help me figure out and implement the correct virtual machine configuration for a dual-socket motherboard (PVE 8.4, 6.8.12 kernel) Given: root@pve-node-04840:~# lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Address sizes: 46 bits physical, 48 bits virtual Byte Order...

Try: sysctl kernel.numa_balancing=0