Thread (21 messages) 21 messages, 4 authors, 2020-02-07

Re: vhost changes (batched) in linux-next after 12/13 trigger random crashes in KVM guests after reboot

From: "Michael S. Tsirkin" <mst@redhat.com>
Date: 2020-02-06 22:17:33
Also in: kvm, lkml, virtualization

On Thu, Feb 06, 2020 at 04:12:21PM +0100, Christian Borntraeger wrote:

On 06.02.20 15:22, eperezma@redhat.com wrote:
quoted
Hi Christian.

Could you try this patch on top of ("38ced0208491 vhost: use batched version by default")?

It will not solve your first random crash but it should help with the lost of network connectivity.

Please let me know how does it goes.

38ced0208491 + this seem to be ok.

Not sure if you can make out anything of this (and the previous git bisect log)
Yes it does - that this is just bad split-up of patches, and there's
still a real bug that caused worse crashes :)

So I just pushed batch-v4.
I expect that will fail, and bisect to give us
    vhost: batching fetches
Can you try that please?

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help