All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hailiang Zhang <zhang.zhanghailiang@huawei.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: xuquan8@huawei.com, qemu-devel@nongnu.org, qemu-block@nongnu.org,
	kwolf@redhat.com, vsementsov@virtuozzo.com
Subject: Re: [Qemu-devel] [QEMU-2.8] Source QEMU crashes with: "bdrv_co_pwritev: Assertion `!(bs->open_flags & BDRV_O_INACTIVE)' failed"
Date: Tue, 25 Apr 2017 15:58:19 +0800	[thread overview]
Message-ID: <58FF019B.4040505@huawei.com> (raw)
In-Reply-To: <20170424075955.5s72guumt35dhmlb@eukaryote>

On 2017/4/24 15:59, Kashyap Chamarthy wrote:
> On Sat, Apr 22, 2017 at 05:23:49PM +0800, Hailiang Zhang wrote:
>> Hi,
> Hi Hailiang,
>
>> I think the bellow patch can fix your problme.
>> [PATCH 2/4] qmp-cont: invalidate on RUN_STATE_PRELAUNCH
>> https://patchwork.kernel.org/patch/9591885/
> Hmm, the above patch ("qmp-cont: invalidate on RUN_STATE_PRELAUNCH") is
> not merged in Git, as it's stalled on design discussion between Kevin
> Wolf and Vladimir.
>
> And the below patch, from you, seems to be not submitted upstream (2.8
> stable tree, perhaps).  Do you intend to do so?

Er, since this patch does the same thing with the above patch, I'm not sure if i should
send this patch ...

>> Actually, we encounter the same problem in our test, we fix it with the follow patch:
>>
>>       From 0e4d6d706afd9909b5fd71536b45c58af60892f8 Mon Sep 17 00:00:00 2001
>>       From: zhanghailiang<zhang.zhanghailiang@huawei.com>
>>       Date: Tue, 21 Mar 2017 09:44:36 +0800
>>       Subject: [PATCH] migration: Re-activate blocks whenever migration been
>>        cancelled
>>
>>       In commit 1d2acc3162d9c7772510c973f446353fbdd1f9a8, we try to fix the bug
>>       'bdrv_co_do_pwritev: Assertion `!(bs->open_flags & 0x0800)' failed'
>>       which occured in migration cancelling process.
>>
>>       But it seems that we didn't cover all the cases, we caught such a case which
>>       slipped from the old fixup in our test: if libvirtd cancelled the migration
>>       process for a shutting down VM, it will send 'system_reset' command first,
>>       and then 'cont' command behind, after VM resumes to run, it will trigger the above
>>       error reports, because we didn't regain the control of blocks for VM.
>>
>>       Signed-off-by: zhanghailiang<zhang.zhanghailiang@huawei.com>
>>       Signed-off-by: Hongyang Yang<yanghongyang@huawei.com>
>>       ---
>>        block.c                       | 12 +++++++++++-
>>        include/block/block.h         |  1 +
>>        include/migration/migration.h |  3 ---
>>        migration/migration.c         |  7 +------
>>        qmp.c                         |  4 +---
>>        5 files changed, 14 insertions(+), 13 deletions(-)
> [...]
>

      reply	other threads:[~2017-04-25  7:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-21 20:41 [Qemu-devel] [QEMU-2.8] Source QEMU crashes with: "bdrv_co_pwritev: Assertion `!(bs->open_flags & BDRV_O_INACTIVE)' failed" Kashyap Chamarthy
2017-04-22  9:23 ` Hailiang Zhang
2017-04-24  7:59   ` Kashyap Chamarthy
2017-04-25  7:58     ` Hailiang Zhang [this message]

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=58FF019B.4040505@huawei.com \
    --to=zhang.zhanghailiang@huawei.com \
    --cc=kchamart@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=vsementsov@virtuozzo.com \
    --cc=xuquan8@huawei.com \
    /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.