I am encountering an issue where the SATA controller cannot be reset.
Error Log:
kvm: vfio: Cannot reset device 0000:00:17.0, no available reset mechanism.
kvm: vfio: Cannot reset device 0000:00:17.0, no available reset mechanism.
Issue Description: The virtual machine, which has the SATA controller passed through, experiences intermittent crashes/hangs, especially when the virtual machine is performing load-intensive read/write operations on the hard disk under the SATA controller.
There was an instance where the virtual machine crashed at 9:51, but there seems to be no abnormal log for this time period in the Syslog panel of PVE:
Dec 27 08:17:01 pve CRON[93383]: pam_unix(cron:session): session closed for user root
...
Dec 27 11:06:28 pve pvedaemon[1231]: <root@pam> successful auth for user 'root@pam'
I am unsure why the “Cannot reset device 0000:00:17.0, no available reset mechanism” error would cause a crash. I suspect that the virtual machine might need full management functionality of the SATA controller.
PVE Version and Hardware Model: The current PVE version is the latest 8.1.3, and the kernel version is Linux pve 6.5.11-7-pve. When the kernel version was 6.2.16-xx, there were three devices that could not be reset: the network card, SATA controller, and graphics card.
After upgrading to 6.5.xxx, without any additional related settings, only one issue remains. Could this indicate that it is not a hardware fault?
root@pve:~# lspci -k
00:17.0 SATA controller: Intel Corporation Device 7a62 (rev 11)
DeviceName: Onboard - SATA
Subsystem: Intel Corporation Device 7270
Kernel driver in use: vfio-pci
Kernel modules: ahci
Please let me know if you need any additional information.
Error Log:
kvm: vfio: Cannot reset device 0000:00:17.0, no available reset mechanism.
kvm: vfio: Cannot reset device 0000:00:17.0, no available reset mechanism.
Issue Description: The virtual machine, which has the SATA controller passed through, experiences intermittent crashes/hangs, especially when the virtual machine is performing load-intensive read/write operations on the hard disk under the SATA controller.
There was an instance where the virtual machine crashed at 9:51, but there seems to be no abnormal log for this time period in the Syslog panel of PVE:
Dec 27 08:17:01 pve CRON[93383]: pam_unix(cron:session): session closed for user root
...
Dec 27 11:06:28 pve pvedaemon[1231]: <root@pam> successful auth for user 'root@pam'
I am unsure why the “Cannot reset device 0000:00:17.0, no available reset mechanism” error would cause a crash. I suspect that the virtual machine might need full management functionality of the SATA controller.
PVE Version and Hardware Model: The current PVE version is the latest 8.1.3, and the kernel version is Linux pve 6.5.11-7-pve. When the kernel version was 6.2.16-xx, there were three devices that could not be reset: the network card, SATA controller, and graphics card.
After upgrading to 6.5.xxx, without any additional related settings, only one issue remains. Could this indicate that it is not a hardware fault?
root@pve:~# lspci -k
00:17.0 SATA controller: Intel Corporation Device 7a62 (rev 11)
DeviceName: Onboard - SATA
Subsystem: Intel Corporation Device 7270
Kernel driver in use: vfio-pci
Kernel modules: ahci
Please let me know if you need any additional information.