** Changed in: qemu
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1681688
Title:
qemu live migration failed
Status in QEMU:
Confirmed
Bug description:
q
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1681688
Title:
qemu live migration failed
Status in QEMU:
Incomplete
Bug description:
qemu l
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
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
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
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
blk->root->perm is 1 when blk_new_open.
the blk->root->perm is update to 3 during virtio_blk_device_realize.
but after this commit, the blk->root->perm is still 1. and cause
bdrv_aligned_pwritev failed.
Breakpoint 1, blk_set_perm (blk=0x14c32b0, perm=3, shared_perm=29,
errp=0x7fffd380) at b
