Re: vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot
From: Christian Borntraeger <hidden>
Date: 2020-02-11 10:08:09
Also in:
kvm, linux-next, lkml
Possibly related (same subject, not in this thread)
- 2020-02-10 · Re: vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot · Christian Borntraeger <hidden>
- 2020-02-07 · Re: vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot · "Michael S. Tsirkin" <mst@redhat.com>
- 2020-02-07 · Re: vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot · Cornelia Huck <cohuck@redhat.com>
- 2020-02-07 · Re: vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot · Christian Borntraeger <hidden>
- 2020-02-07 · Re: vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot · "Michael S. Tsirkin" <mst@redhat.com>
On 11.02.20 10:56, Christian Borntraeger wrote:
On 11.02.20 10:33, Eugenio Pérez wrote:quoted
On Mon, 2020-02-10 at 12:01 +0100, Christian Borntraeger wrote:quoted
On 10.02.20 10:47, Eugenio Perez Martin wrote:quoted
Hi Christian. I'm not able to reproduce the failure with eccb852f1fe6bede630e2e4f1a121a81e34354ab commit. Could you add more data? Your configuration (libvirt or qemu line), and host's dmesg output if any? Thanks!If it was not obvious, this is on s390x, a big endian system.Hi Christian. Thank you very much for the hints. Could we add some debug traces? Something like the inline patch should give us some clues.attached. this time the guest crashed (and no guest moved message)
And here with Guest moved vq after some reboots.