Hi Matthew Ruffell
First of all, thank you for your response.
If you want to reproduce this issue, you can try the following steps:
1. Boot the Ubuntu 24 system and modify the kernel boot parameters to include virtio_pci.force_legacy=1.
2. Use perf-tools or ftrace to trace the return value of the virtio_pci_legacy_probe function.
3. Insert a virtio network card or disk, and observe the return value of the virtio_pci_legacy_probe function within the guest OS to confirm a successful return of 0x0, indicating that the virtio device has been enabled using virtio_pci_legacy_probe.
4. Remove the network card or disk, and you should be able to reproduce the issue.
Hi Matthew Ruffell
First of all, thank you for your response.
If you want to reproduce this issue, you can try the following steps:
1. Boot the Ubuntu 24 system and modify the kernel boot parameters to include virtio_ pci.force_ legacy= 1. pci_legacy_ probe function. pci_legacy_ probe function within the guest OS to confirm a successful return of 0x0, indicating that the virtio device has been enabled using virtio_ pci_legacy_ probe.
2. Use perf-tools or ftrace to trace the return value of the virtio_
3. Insert a virtio network card or disk, and observe the return value of the virtio_
4. Remove the network card or disk, and you should be able to reproduce the issue.
I have installed and tested the test kernel you built on Ubuntu 24, and it's working fine. Additionally, I have also backported the patch from https:/ /github. com/torvalds/ linux/commit/ c8fae27d141a32a 1624d0d0d5419d9 4252824498 (virtio-pci: Check if is_avq is NULL) and compiled the Ubuntu kernel, which also has no issues.