Compatibility of Windows VM with PVE kernel and QEMU?

[1582130940]

I'm not sure if it's a hardware or software issue; all I can say is that it can boot up, but it takes a long time.

After upgrading to kernel 6.17 and QEMU 10, Windows virtual devices can boot, but it takes a very long time..

After successful startup, resource usage will return to normal.

In the PVE WebGUI, the following error message appears:
error writing '1' to '/sys/bus/pci/devices/0000:01:00.0/reset': Inappropriate ioctl for device
failed to reset PCI device '0000:01:00.0', but trying to continue as not all devices need a reset

For VNC:
VM 103 qmp command 'set_password' failed - unable to connect to VM 103 qmp socket - timeout after 50 retries
TASK ERROR: Failed to run vncproxy.

And Host memory usage is 24.55 GiB (I only allocated 24GB).

dmesg:
[104.838121]vfio-pci0000:01:00.0:resetting
[104.838196]vfio-pci0000:01:00.0:resetdone
[104.889170]vfio-pci0000:06:00.0:resetting
[104.913505]vfio-pci0000:06:00.0:resetdone
[104.939945]vfio-pci0000:08:00.0:resetting
[105.069841]vfio-pci0000:08:00.0:resetdone
[105.096065]vfio-pci0000:09:00.0:resetting
[105.120393]vfio-pci0000:09:00.0:resetdone
[105.148021]vfio-pci0000:01:00.0:resetting
[105.148059]vfio-pci0000:01:00.1:resetting
[105.285789]vfio-pci0000:01:00.0:resetdone
[105.285813]vfio-pci0000:01:00.1:resetdone
[105.296823]vfio-pci0000:09:00.0:resetting
[105.445848]vfio-pci0000:09:00.0:resetdone
[105.446104]vfio-pci0000:08:00.0:resetting
[105.573768]vfio-pci0000:08:00.0:resetdone
[105.573914]vfio-pci0000:06:00.0:resetting
[105.701882]vfio-pci0000:06:00.0:resetdone
[154.071012]hrtimer:interrupttook126218961ns


[393.867405]watchdog:BUG:softlockup-CPU#8stuckfor22s![vhost-2275:2306]
[394.540632]CPU:8UID:0PID:2306Comm:vhost-2275TaintedUO6.17.2-1-pve#1PREEMPT(voluntary)
[394.582708]Tainted:[P]=PROPRIETARY_MODULE,=USER,[O]=OOT_MODULE
[394.582709]Hardwarename:ASUSSystemProductName/TUFGAMINGZ790-PROWIFI,BIOS182005/14/2025
[394.582709]RIP:0010:hrtimer_start_range_ns+0x41/0x460
[394.624785]Code:564989f641554989d541544989fc534883ec38807f3a00894dd40f94c238d00f8571030000498b5
c2430<48>81fb80aedc840f84bb020000488b3be82a49ff0048
[394.624786]RSP:0018:ffffcc840d9f7550EFLAGS:00000246
[394.624788]RAX:0000000000000001RBX:ffff8a423fca1440RCX:0000000000000002
[394.666860]RDX:0000000000000001RSI:0000005bc7592db2RDI:ffff8a3318d8c1f8
[394.666861]RBP:ffffcc840d9f75b0R08:0000000000000000R09:0000005bc70ce272
[394.666862]R10:00000000000005eaR11:0000000000000000R12:ffff8a3318d8c1f8
[394.666862]R13:0000000000000000R14:0000005bc7592db2R15:0000000000000009
[394.666863]FS:00007adfd9490840(0000)GS:ffff8a42ba586000(0000)knlGS:0000000000000000
[394.666863]CS:0010DS:0000ES:0000CR0:0000000080050033
[394.666864]CR2:0000000001448348CR3:0000000134206001CR4:0000000000f72ef0
[394.708938]PKRU:55555554
[394.708938]CallTrace:
[394.708939]
[394.708942]qdisc_watchdog_schedule_range_ns+0x63/0x80
[394.751017]cake_dequeue+0xb31/0xea0[sch_cake]
[394.793093]__qdisc_run+0x8e/0x650
[394.835169]__dev_queue_xmit+0x5fd/0xfa0
[394.835170]?asm_sysvec_apic_timer_interrupt+0x1b/0x20
[394.835171]?asm_sysvec_apic_timer_interrupt+0x1b/0x20
[394.877245]?_raw_read_unlock_bh+0x20/0x30
[394.919322]?ebt_do_table+0x839/0x8c0[ebtables]
[394.919324]br_dev_queue_push_xmit+0x168/0x1f0
[394.919325]br_forward_finish+0x4d/0xf0
[394.961399]?__pfx_br_dev_queue_push_xmit+0x10/0x10
[394.961400]__br_forward+0x189/0x200
[394.961401]?__pfx_br_forward_finish+0x10/0x10
[394.961402]br_forward+0x134/0x170
[394.961403]br_handle_frame_finish+0x408/0x690
[395.003477]br_handle_frame+0x32b/0x450
[395.003478]?__pfx_br_handle_frame_finish+0x10/0x10
[395.003479]__netif_receive_skb_core.constprop.0+0x620/0x1400
[395.045553]?sysvec_apic_timer_interrupt+0x57/0xc0
[395.045556]__netif_receive_skb_one_core+0x3b/0xa0
[395.087629]__netif_receive_skb+0x15/0x60
[395.087631]netif_receive_skb+0x127/0x180
[395.087632]tun_sendmsg+0x504/0x980
[395.129708]vhost_tx_batch.isra.0+0xdc/0x2a0[vhost_net]
[395.129709]handle_tx_copy+0x3dd/0x630[vhost_net]
[395.129711]handle_tx+0xbc/0xc0[vhost_net]
[395.171784]handle_tx_kick+0x15/0x20[vhost_net]
[395.171786]vhost_run_work_list+0x47/0x80[vhost]
[395.213861]vhost_task_fn+0x54/0x100
[395.213863]?finish_task_switch.isra.0+0x9c/0x340
[395.255939]?__pfx_vhost_task_fn+0x10/0x10
[395.255940]?calculate_sigpending+0x33/0x40
[395.298015]?__pfx_vhost_task_fn+0x10/0x10
[395.298016]ret_from_fork+0x205/0x240
[395.298018]?__pfx_vhost_task_fn+0x10/0x10
[395.340092]ret_from_fork_asm+0x1a/0x30
[395.340093]RIP:0033:0x0
[395.340094]Code:Unabletoaccessopcodebytesat0xffffffffffffffd6.
[395.340095]RSP:002b:0000000000000000EFLAGS:00000246ORIG_RAX:0000000000000010
[395.382169]RAX:0000000000000000RBX:0000640d679fd210RCX:00007adfdc71e8db
[395.382169]RDX:0000000000000000RSI:000000000000af01RDI:0000000000000021
[395.382170]RBP:00007ffe5bf6bd10R08:00007ffe5bf6bcb0R09:0000000000000001
[395.382170]R10:00007adfdc7f9b60R11:0000000000000246R12:0000000000000020
[395.382171]R13:00007ffe5bf6bd08R14:0000640d679fd210R15:0000000000000000

root@pve:~# dpkg --list | grep proxmox
ii libproxmox-acme-perl 1.7.0 all Proxmox ACME integration perl library
ii libproxmox-acme-plugins 1.7.0 all Proxmox acme.sh wrapper for DNS API plugins
ii libproxmox-backup-qemu0 2.0.1 amd64 Proxmox Backup Server client library for QEMU
ii libproxmox-rs-perl 0.4.1 all PVE/PMG common perl parts for Rust perlmod bindings
ii proxmox-archive-keyring 4.0 all Proxmox APT archive keyring
ii proxmox-backup-client 4.0.19-1 amd64 Proxmox Backup Client tools
ii proxmox-backup-file-restore 4.0.19-1 amd64 Proxmox Backup single file restore tools for pxar and block device backups
ii proxmox-backup-restore-image 1.0.0 amd64 Kernel/initramfs images for Proxmox Backup single-file restore.
ii proxmox-default-kernel 2.0.1 all Default Proxmox Kernel Image
ii proxmox-firewall 1.2.0 amd64 Proxmox's nftables-based firewall written in rust
ii proxmox-grub 2.12-9+pmx2 amd64 Empty package to ensure Proxmox Grub packages are installed
ii proxmox-headers-6.17 6.17.2-1 all Latest Proxmox Kernel Headers
ii proxmox-headers-6.17.2-1-pve 6.17.2-1 amd64 Proxmox Kernel Headers
ii proxmox-kernel-6.17 6.17.2-1 all Latest Proxmox Kernel Image
ii proxmox-kernel-6.17.2-1-pve-signed 6.17.2-1 amd64 Proxmox Kernel Image (signed)
ii proxmox-kernel-helper 9.0.4 all Function for various kernel maintenance tasks.
ii proxmox-mail-forward 1.0.2 amd64 Proxmox mail forward helper
ii proxmox-mini-journalreader 1.6 amd64 Minimal systemd Journal Reader
ii proxmox-offline-mirror-docs 0.7.3 all Proxmox offline repository mirror and subscription key manager
ii proxmox-offline-mirror-helper 0.7.3 amd64 Proxmox offline repository mirror and subscription key manager helper
ii proxmox-termproxy 2.0.3 amd64 Wrapper proxy for executing programs in the system terminal
ii proxmox-ve 9.0.0 all Proxmox Virtual Environment
ii proxmox-websocket-tunnel 1.0.0 amd64 Proxmox websocket tunneling helper
ii proxmox-widget-toolkit 5.1.0 all Core Widgets and ExtJS Helper Classes for Proxmox Web UIs

 

[SteveITS]

If you are using host try a generic CPU type.

What version of Windows and drivers?

R

Post in thread 'Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive"'

Nov 5, 2025

OK, I'm quite confident that I've found and isolated the problem (and will drop it on github soon).

So let's start with the analysis. At first, be careful that virtio releases in time are not relevant to the commit dates.
I mean that if you see e.g. version 0.1.271 was released on fedorapeople.org at 2025-04-07, it was definitely not committed this date.
If you're really interested what is inside, you have to download *.src.rpm package from the same path (here e.g. virtio-win-0.1.271-1).
This can be done within the Windows (VM), no Linux needed. It's just double 7-zipped...

• RoCE-geek

• 

Boot disk is SCSI?