From: Eric Blake <eblake@redhat.com>
To: Bug 1712818 <1712818@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1712818] [NEW] live migration with storage encounter assert(!(bs->open_flags & BDRV_O_INACTIVE)) crashes
Date: Thu, 24 Aug 2017 11:48:53 -0500 [thread overview]
Message-ID: <104369c1-ccfd-bfda-5d1e-97e8e874f45d@redhat.com> (raw)
In-Reply-To: <150357954932.16920.8202218494274187188.malonedeb@gac.canonical.com>
[-- Attachment #1: Type: text/plain, Size: 823 bytes --]
On 08/24/2017 07:59 AM, meeho yuen wrote:
> Public bug reported:
>
> The vm guest runs a iotest program, and i migrate it with virsh --copy-
> storage-all,then the qemu process on the source host happens to crash
> with the following message:
>
> kvm: block/io.c:1543: bdrv_co_pwritev: Assertion `!(bs->open_flags & 0x0800)' failed.
> 2017-08-24 11:43:45.919+0000: shutting down, reason=crashed
> here is the release:
> qemu 2.7 & 2.10.rc3 were tested.
The just-tagged 2.10-rc4 includes a fix that should be addressing that
issue during live migration; can you please re-test with that? (see
also https://lists.gnu.org/archive/html/qemu-devel/2017-08/msg04513.html)
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 619 bytes --]
next prev parent reply other threads:[~2017-08-24 16:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 12:59 [Qemu-devel] [Bug 1712818] [NEW] live migration with storage encounter assert(!(bs->open_flags & BDRV_O_INACTIVE)) crashes meeho yuen
2017-08-24 16:48 ` Eric Blake [this message]
2017-08-25 1:25 ` [Qemu-devel] [Bug 1712818] " meeho yuen
2017-08-25 3:24 ` meeho yuen
2017-12-28 21:50 ` Matthew Schumacher
2018-08-09 7:45 ` meeho yuen
2020-09-05 12:19 ` Thomas Huth
2020-11-05 4:17 ` Launchpad Bug Tracker
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=104369c1-ccfd-bfda-5d1e-97e8e874f45d@redhat.com \
--to=eblake@redhat.com \
--cc=1712818@bugs.launchpad.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).