Redhat VirtIO developers would like to coordinate with Proxmox devs re: "[vioscsi] Reset to device ... system unresponsive"
- Thread starter ylluminate
- Start date
-
- Tags
- virtio virtio disk virtio scsi
Can anyone confirm if the 0.1.266-1 driver bundle from the Fedora Download site is supposed to fix this issue?
I'm still seeing "Reset to device, \Device\RaidPort1, was issued." with this version, and having looked at the source RPMs, they don't appear to have all of the commits mentioned on Github.
I'm still seeing "Reset to device, \Device\RaidPort1, was issued." with this version, and having looked at the source RPMs, they don't appear to have all of the commits mentioned on Github.
oh, yes you're right. I'm not too sure which bits are most relvevant though. I switched my VMs to virtio block (which is viostor driver, right?) and all looks OK so far. Strangely only one of my systems was affected anyway. I saw it when opening the very large event log while it was installing windows updates.
https://github.com/virtio-win/kvm-guest-drivers-windows/pull/1196#issuecomment-2490465751
Last edited:
no, virtio block is another driver, which currently missing io thread.
fix here is for virtio scsi driver, used when vdisk attached as scsi + scsi controller set to virtio scsi single.
Hi, sorry for the question, but was the fix for virtioscsi included in 0.1.266-1?
I seem to see conflicting answers about whether it is included and the problem is solved or not, from corresponding tag in the github repository result not included (if I checked correctly), so even if someone wrote here that he has no problems with the latest version the problem remains, and therefore I have to use maximum version 0.1.208 for virtioscsi to be sure to avoid the issue?
I'm trying to figure out which version of virtio I should put (to avoid the problem) on some windows servers with critical services that I'll migrate to proxmox soon.
I seem to see conflicting answers about whether it is included and the problem is solved or not, from corresponding tag in the github repository result not included (if I checked correctly), so even if someone wrote here that he has no problems with the latest version the problem remains, and therefore I have to use maximum version 0.1.208 for virtioscsi to be sure to avoid the issue?
I'm trying to figure out which version of virtio I should put (to avoid the problem) on some windows servers with critical services that I'll migrate to proxmox soon.
Just to clear up any confusion:
Per Vadim's comment above that post, the next stable public build will be released in mid-end of January 2025.
This should include the fixes for
- The fixes for the
viostor(VirtIO SCSI Controller) driver are NOT in v266. - The fixes for the
vioscsi(VirtIO SCSI pass-through controller) driver are in v266.
Per Vadim's comment above that post, the next stable public build will be released in mid-end of January 2025.
This should include the fixes for
viostor.Thanks for the reply and details.
I started to update virtio 0.1.266-1 on 2 servers with low usage, one windows 2019 and one windows 2022, on both after reboot network interface partially lost the configuration, easily solvable if you mark the configuration before the update and then check it and set what is missing but knowing the problem could be useful to avoid problems if someone updates virtio but does not check (maybe for mass updates remotely or with reboot afterwards).
Has this issue been seen by others?
I started to update virtio 0.1.266-1 on 2 servers with low usage, one windows 2019 and one windows 2022, on both after reboot network interface partially lost the configuration, easily solvable if you mark the configuration before the update and then check it and set what is missing but knowing the problem could be useful to avoid problems if someone updates virtio but does not check (maybe for mass updates remotely or with reboot afterwards).
Has this issue been seen by others?