On Tue, 09/27 19:55, Roman Penyaev wrote: > > The bug is 100% deterministic. Just boot up a guest with -drive > > format=qcow2,aio=native. > > It turns out to be that everything is broken. I started all my > tests with format=raw,aio=native and immediately got coroutine > recursive. That is completely weird. > > So, what I did is the following: > > 1. Took latest master (nothing works) > 2. Did interactive rebase to 12c8720 > 12c8720 2016-06-28 | Merge remote-tracking branch > 'remotes/stefanha/tags/block-pull-request' into staging [Peter > Maydell] > > this merge request includes all your patches related to > virtio-blk and MQ support. > > 3. Applied 0ed93d84edab. Everything works fine.
Have you tried qcow2 at this point? raw crashes with 1a62d0accdf85 doesn't mean qcow2 is fine without it. Fam > > 4. Rebased up till 0647d47: > 0647d47 2016-09-13 | qcow2: avoid memcpy(dst, NULL, len) [Stefan Hajnoczi] > > this is the point, after which 0ed93d84edab was applied > on master. > > Got recursive coroutine, so nothing works. > > 5. Did a besect, which shows this commit: > > -- > commit 1a62d0accdf85fbeac149018ee8d1728e754de73 > Author: Eric Blake <ebl...@redhat.com> > Date: Fri Jul 15 12:31:59 2016 -0600 > > block: Fragment reads to max transfer length > -- > > So after this commit my commit 0ed93d84edab stops working. > And now for me is completely not clear what is happening there. > > -- > Roman >
