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

[_gabriel]

switching the SCSI Controller to Default (LSI 53C895A)

isn't required as controller isn't used when no scsi devices attached.
are you able to reproduce issue with SATA type disk keeping VirtIO SCSI controller ?!

edit: add your storage type, here is local storage only to exclude others factors.

 

[complexplaster27]

isn't required as controller isn't used when no scsi devices attached.
are you able to reproduce issue with SATA type disk keeping VirtIO SCSI controller ?!

edit: add your storage type, here is local storage only to exclude others factors.

I've been a fly on the wall for this issue but especially with MSSQL servers I can replicate the vioscsi disk reset. I'm using Ceph as the storage locally.

 

[dsjfshdfjklsdjfkkjv]

I have had the issue with VirtIO SCSI on pretty much all drivers and configurations. I just switched these over to SATA and will see if the issue improves at all.

All local storage, with VMs running on ZFS and physical disks passed through on native NTFS.

 

[kellogs]

is this only affecting Windows VM or Linux as well?

 

[proteus]

Proxmox 8.2.4, ZFS Mirror with 2 x NVME PM9A3
Windows Server 2022 VM with 3 disks, OS, SQL, SQL Backups, drivers used: virtio-win-0.1.240-1.
Zabbix gives me a warning that the disk is overloaded with a high utilization, when I RDP into the VM I can't access the disk with the SQL
Databases. When I checked Event Viewer I got allot of "Reset to device, \Device\RaidPort2, was issued."

 

[_gabriel]

Current mitigations is downgrade virtio-scsi driver to version 0.1.208, within Windows Device Manager.

https://forum.proxmox.com/threads/r...device-system-unresponsive.139160/post-691337