Please check if this commit has solved the issue:
https://git.qemu.org/?p=qemu.git;a=commit;h=ebb6ff25cd888a52a64a9adc3692541c6d1d9a42
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1839428
Title:
I found the commit that introduced this regression.
commit 57830a499f7c815bb0cb325c94a3d8c910d13cfa (HEAD)
Author: Denis Plotnikov
Date: Fri Feb 15 16:03:25 2019 +0300
block: don't set the same context
Adds a fast path on aio context setting preventing
unnecessary context setting
This issue is very hard to reproduce.
It sometimes crashes, so I could mark few commits 'bad' while bisecting,
but since it is not reliable, I'm not sure a commit is 'good' when there
is no crash.
For now after hours of testing I could reduce Xujun Ma's range to
qemu-v3.1.0..1d31f1872b:
commit 1
** Changed in: qemu
Status: New => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1839428
Title:
qemu core dumped when repeat "system_reset" multiple times during
guest boot
Sta
Upstream qemu-v3.1.0 pass
Upstream qemu-v3.1.1 pass
Upstream qemu-v4.0.0 fail
Upstream qemu-v4.0.0-rc0 fail
So the problem occurs due to patch between qemu-v3.1.1 to
qemu-v4.0.0-rc0.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
ht