From: Laurent Vivier <lvivier@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>, 858585 jemmy <jemmy858585@gmail.com>
Cc: Bug 1681688 <1681688@bugs.launchpad.net>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1681688] Re: qemu live migration failed
Date: Tue, 11 Apr 2017 16:00:06 +0200 [thread overview]
Message-ID: <fe15d207-3e01-dd4a-737d-1a3e1acd2f15@redhat.com> (raw)
In-Reply-To: <20170411135700.GM4516@noname.str.redhat.com>
On 11/04/2017 15:57, Kevin Wolf wrote:
> Am 11.04.2017 um 15:35 hat 858585 jemmy geschrieben:
>> Hi Kevin:
>> Can you provide some information about the original bug which you want fix?
>>
>> the original comment:
>> Usually guest devices don't like other writers to the same image, so
>> they use blk_set_perm() to prevent this from happening.
>>
>> i don't find where the dest qemu will use blk_set_perm during migration.
>> but after apply this patch, blkconf_apply_backend_options don't update the
>> blk->root->perm.
>
> Do I understand correctly that this is not simply live migration, but
> block live migration (with 'migrate -b')?
>
> Can you please post a backtrace not of the successful case, but of the
> failing assertion?
Kevin,
I've also reproduced this problem without the block live migration while
I was testing my patch to fix the virtio-rng migration.
Laurent
next prev parent reply other threads:[~2017-04-11 14:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-11 8:01 [Qemu-devel] [Bug 1681688] [NEW] qemu live migration failed Lidong Chen
2017-04-11 8:21 ` [Qemu-devel] [Bug 1681688] " Lidong Chen
2017-04-11 13:35 ` 858585 jemmy
2017-04-11 13:57 ` Kevin Wolf
2017-04-11 14:00 ` Laurent Vivier [this message]
2017-04-11 14:05 ` Laurent Vivier
2017-04-18 19:42 ` pranith
2017-04-18 20:10 ` pranith
2020-11-17 11:52 ` Thomas Huth
2021-01-17 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=fe15d207-3e01-dd4a-737d-1a3e1acd2f15@redhat.com \
--to=lvivier@redhat.com \
--cc=1681688@bugs.launchpad.net \
--cc=jemmy858585@gmail.com \
--cc=kwolf@redhat.com \
--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).