https://bugzilla.kernel.org/show_bug.cgi?id=198205 --- Comment #3 from Mark Mielke (mark.mielke@xxxxxxxxx) --- I should add some other clarifications: 1) The guests usually don't lock up on an idle host. To make it fail, I normally need to busy the network and storage. This has a side effect of busying the CPU, but I haven't seen CPU as a primary trigger for me. 2) The guests that lock up include both a CentOS 7 guest, and Fedora 27 guests. The Fedora 27 guests had both Linux 4.13 and Linux 4.14. The Fedora 27 guests are currently running Linux 4.14.11, and they locked up. The CentOS 7 guest is Linux 3.10.0-514.21.1.el7.x86_64. There is no particular order to the failures. The CentOS 7 guest seems to fail with the same probability and triggers as the Fedora 27 guests. 3) The host uses OpenVSwitch 2.8.1. The guests are attached to an OVS bridge. vhost-net is active. The host also uses LVM thin volumes mounted on Intel SSD 750 NVMe drives as backing store for the guest volumes. 4) Force Reset, or Force Off, then Force On, usually clears it for a particular guest for a particular time. Also, the guest can be suspended and resumed. I did play with setting up libvirt to run "qemu -s" and running remote GDB debugger on the guests, but this was too new to me to make complete sense. I was able to see it was spinning inside the guest (not on the host), but I wasn't able to see what it was doing in the guest, or why it was doing it. -- You are receiving this mail because: You are watching the assignee of the bug.
