On 18.07.2018 [11:10:27 -0400], Farhan Ali wrote:
>
>
> On 07/18/2018 09:42 AM, Farhan Ali wrote:
> >
> >
> > On 07/17/2018 04:52 PM, Nishanth Aravamudan wrote:
> > > iiuc, this possibly implies AIO was not actually used previously on this
> > > guest (it might have silently been falling back
On 07/18/2018 09:42 AM, Farhan Ali wrote:
On 07/17/2018 04:52 PM, Nishanth Aravamudan wrote:
iiuc, this possibly implies AIO was not actually used previously on this
guest (it might have silently been falling back to threaded IO?). I
don't have access to s390x, but would it be possible to
On 07/17/2018 04:52 PM, Nishanth Aravamudan wrote:
iiuc, this possibly implies AIO was not actually used previously on this
guest (it might have silently been falling back to threaded IO?). I
don't have access to s390x, but would it be possible to run qemu under
gdb and see if
On 17.07.2018 [13:25:53 -0400], Farhan Ali wrote:
> Hi,
>
> I am seeing some strange QEMU assertion failures for qemu on s390x,
> which prevents a guest from starting.
>
> Git bisecting points to the following commit as the source of the error.
>
> commit
Hi,
I am seeing some strange QEMU assertion failures for qemu on s390x,
which prevents a guest from starting.
Git bisecting points to the following commit as the source of the error.
commit ed6e2161715c527330f936d44af4c547f25f687e
Author: Nishanth Aravamudan
Date: Fri Jun 22 12:37:00 2018
