I managed to upgrade to qemu 4.1 on a test KVM host and I can confirm I can't 
repro the issue in this version.
Great news that is fixed in 4.1.

Thanks everyone for your inputs and the fast replies.

Kind regards,

Fernando

On vie, oct 25, 2019 at 12:28 PM, Fernando Casas Schössow 
<casasferna...@outlook.com> wrote:
Thanks for the reply Kevin.

I will do my best to upgrade to 4.1, test again and report back if this is 
fixed or not in that version.
Hopefully it is.

Fernando

On vie, oct 25, 2019 at 12:07 PM, Kevin Wolf <kw...@redhat.com> wrote:
Am 23.10.2019 um 19:28 hat Fernando Casas Schössow geschrieben:
Hi John, Thanks for looking into this. I can quickly repro the problem with 
qemu 4.0 binary with debugging symbols enabled as I have it available already. 
Doing the same with qemu 4.1 or development head may be too much hassle but if 
it's really the only way I can give it try.
We had a lot of iothread related fixes in 4.1, so this would really be the only 
way to tell if it's a bug that still exists. I suspect that it's already fixed 
(and to be more precise, I assume that commit d0ee0204f fixed it). Kevin




Reply via email to