[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1ade56b5-083f-bb6f-d3e0-3ddcf78f4d26@de.ibm.com>
Date: Thu, 6 Feb 2020 16:12:21 +0100
From: Christian Borntraeger <borntraeger@...ibm.com>
To: eperezma@...hat.com
Cc: "Michael S. Tsirkin" <mst@...hat.com>,
"virtualization@...ts.linux-foundation.org"
<virtualization@...ts.linux-foundation.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
kvm list <kvm@...r.kernel.org>,
Halil Pasic <pasic@...ux.ibm.com>
Subject: Re: vhost changes (batched) in linux-next after 12/13 trigger random
crashes in KVM guests after reboot
On 06.02.20 15:22, eperezma@...hat.com wrote:
> 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)
Powered by blists - more mailing lists