From: Ed Swierk <eswierk@skyportsystems.com>
To: John Snow <jsnow@redhat.com>
Cc: Fam Zheng <famz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [Qemu-devel] New iotest repros failures on virtio external snapshot with iothread
Date: Thu, 30 Mar 2017 16:26:26 -0700 [thread overview]
Message-ID: <CAO_EM_mk+8a=x3KP3s-BP7W5RaGHg2aDe0m3-qLnqY6BGMMOKA@mail.gmail.com> (raw)
In-Reply-To: <dd90d073-5a24-4d89-5be4-1c51af748091@redhat.com>
On Thu, Mar 30, 2017 at 4:06 PM, John Snow <jsnow@redhat.com> wrote:
> On 03/29/2017 10:01 PM, Ed Swierk via Qemu-devel wrote:
>> * 2.9.0-rc2
>> - guest, virtio-blk, iothread, single snapshot create+commit:
>> "include/block/aio.h:457: aio_enable_external: Assertion
>> `ctx->external_disable_cnt > 0' failed." after snapshot create
>> - guest, virtio-blk, iothread, repeated snapshot create+commit: same as above
>> - guest, virtio-scsi, iothread, single snapshot create+commit: same as above
>> - guest, virtio-scsi, iothread, repeated snapshot create+commit: same as above
>> - no guest, virtio-blk, iothread, repeated snapshot create+commit: same as above
>> - no guest, virtio-scsi, iothread, single snapshot create+commit: same as above
>> - no guest, virtio-scsi, iothread, repeated snapshot create+commit:
>> same as above
>
> Do you mean to say that all of these 2.9.0-rc2 cases produce the same
> aio.h assertion?
Correct.
--Ed
next prev parent reply other threads:[~2017-03-30 23:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 2:01 [Qemu-devel] New iotest repros failures on virtio external snapshot with iothread Ed Swierk
2017-03-30 2:16 ` Eric Blake
2017-03-30 23:43 ` Laszlo Ersek
2017-04-07 13:58 ` Max Reitz
2017-03-30 23:06 ` John Snow
2017-03-30 23:26 ` Ed Swierk [this message]
2017-04-03 16:57 ` [Qemu-devel] [Qemu-block] " Stefan Hajnoczi
2017-04-04 14:13 ` Alex Bennée
2017-04-06 9:10 ` Stefan Hajnoczi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAO_EM_mk+8a=x3KP3s-BP7W5RaGHg2aDe0m3-qLnqY6BGMMOKA@mail.gmail.com' \
--to=eswierk@skyportsystems.com \
--cc=famz@redhat.com \
--cc=jsnow@redhat.com \
--cc=kwolf@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.