[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <43a5dbaa-9129-e220-8483-45c60a82c945@de.ibm.com>
Date: Mon, 10 Feb 2020 12:01:56 +0100
From: Christian Borntraeger <borntraeger@...ibm.com>
To: Eugenio Perez Martin <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>,
Cornelia Huck <cohuck@...hat.com>
Subject: Re: vhost changes (batched) in linux-next after 12/13 trigger random
crashes in KVM guests after reboot
On 10.02.20 10:47, Eugenio Perez Martin wrote:
> 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.
Powered by blists - more mailing lists