Comment 9 for bug 1947422

I was able to reproduce this issue in a local VM. The VM was created and managed using virt-manager on a Focal host. I could reproduce this on a guest running focal:linux, focal:linux-hwe-5.15, and focal:linux-kvm.

(5.15.0-60-generic) ubuntu@focal-vm-2:~$ lspci -nn
00:00.0 Host bridge [0600]: Intel Corporation 440FX - 82441FX PMC [Natoma] [8086:1237] (rev 02)
00:01.0 ISA bridge [0601]: Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II] [8086:7000]
00:01.1 IDE interface [0101]: Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II] [8086:7010]
00:01.3 Bridge [0680]: Intel Corporation 82371AB/EB/MB PIIX4 ACPI [8086:7113] (rev 03)
00:02.0 VGA compatible controller [0300]: Red Hat, Inc. QXL paravirtual graphic card [1b36:0100] (rev 04)
00:03.0 Ethernet controller [0200]: Red Hat, Inc. Virtio network device [1af4:1000]
00:04.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 03)
00:05.0 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 [8086:2934] (rev 03)
00:05.1 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 [8086:2935] (rev 03)
00:05.2 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 [8086:2936] (rev 03)
00:05.7 USB controller [0c03]: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 [8086:293a] (rev 03)
00:06.0 SATA controller [0106]: Intel Corporation 82801IR/IO/IH (ICH9R/DO/DH) 6 port SATA Controller [AHCI mode] [8086:2922] (rev 02)
00:08.0 SCSI storage controller [0100]: Red Hat, Inc. Virtio block device [1af4:1001]
00:09.0 Unclassified device [00ff]: Red Hat, Inc. Virtio memory balloon [1af4:1002]
00:0a.0 Unclassified device [00ff]: Red Hat, Inc. Virtio RNG [1af4:1005]

I could only reproduce it while using the emulated i440FX chipset. This issue does not seem to apply to the Q35 chipset. Perhaps this is related to the i440FX only supporting PCI and the Q35 chipset supporting PCIe.

Additionally, I was able to reproduce this after running test 12 on either the 00:08.0 SCSI storage controller, or the 00:03.0 Ethernet controller.

With the SCSI storage controller, a system hang would occur when attempting read data from the disk that had not been cached (e.g. running a program that was not run since boot).

With the Ethernet controller, a system hang would occur if I set the network link down (i.e. # ip link set ens3 down), but not from a ping test, which did not have any successful pings get through, but also did not hang.