[Qemu-devel] [PATCH] MAINTAINERS: update my email address

From: Zhang Chen <zhangchen.f...@cn.fujitsu.com> I'm leaving my job at Fujitsu, this email address will stop working this week. Update it to one that I will have access to later. Signed-off-by: Xie Changlong <xiecl.f...@cn.fujitsu.com> --- MAINTAINERS | 2 +- 1 file changed, 1 ins

Re: [Qemu-devel] [PATCH v4 2/6] replication: add shared-disk and shared-disk-id options

On 04/12/2017 10:05 PM, zhanghailiang wrote: We use these two options to identify which disk is shared Signed-off-by: zhanghailiang Signed-off-by: Wen Congyang Signed-off-by: Zhang Chen --- v4: - Add

Re: [Qemu-devel] [PULL 2/8] replication: clarify permissions

On 04/18/2017 09:36 AM, Hailiang Zhang wrote: On 2017/4/18 9:23, Eric Blake wrote: On 03/17/2017 08:15 AM, Kevin Wolf wrote: From: Changlong Xie Even if hidden_disk, secondary_disk are backing files, they all need write permissions in replication scenario.

Re: [Qemu-devel] [PATCH] file-posix: Clear out first sector in hdev_create

在 8/10/2017 4:01 PM, Fam Zheng 写道: People get surprised when, after "qemu-imc create -f raw /dev/sdX", they s/qemu-imc/qemu-img/ still see qcow2 with "qemu-img info", if previously the bdev had a qcow2 -- Thanks -Xie

Re: [Qemu-devel] block replication

在 8/10/2017 8:26 PM, Vladimir Sementsov-Ogievskiy 写道: 09.08.2017 17:11, Vladimir Sementsov-Ogievskiy wrote: Hi Wen! I'm trying to understand block/replication code and have a question. Why should we block the region from intersecting cow requests when read? If I understand correctly

Re: [Qemu-devel] About the trace framework

在 7/11/2017 9:33 AM, Wang Dong 写道: On 07/10/2017 01:24 PM, Xie Changlong wrote: 在 7/9/2017 5:57 PM, Wang Dong 写道: Hi, I am new to QEMU. But I got some problem so that I want to figure it out. So I try to debug qemu to see what happened. And I found trace framework. I think

Re: [Qemu-devel] About the trace framework

在 7/9/2017 5:57 PM, Wang Dong 写道: Hi, I am new to QEMU. But I got some problem so that I want to figure it out. So I try to debug qemu to see what happened. And I found trace framework. I think this will help me understand the point. So I compiled qemu with option: ##

Re: [Qemu-devel] [PATCH 5/6] block: Fix write/resize permissions for inactive images

在 5/5/2017 12:52 AM, Kevin Wolf 写道: +/* Returns whether the image file can be written to right now */ +bool bdrv_is_writable(BlockDriverState *bs) +{ +return !bdrv_is_read_only(bs) && !(bs->open_flags & BDRV_O_INACTIVE); +} + This commit use BDRV_O_INACTIVE to judge whether the image

Re: [Qemu-devel] [Question] How can we confirm hot-plug disk succesfully?

在 6/19/2017 6:49 PM, Kevin Wolf 写道: 'info block' shows nothing, but we can't add drive who's id is'drive-virtio-disk1' too. Yes, the old BlockBackend is only fully freed when the guest actually unplugs the device. Specifically, we would have to free the QemuOpts in DriveInfo that keeps the ID

[Qemu-devel] [Question] How can we confirm hot-plug disk succesfully?

Hi all In device hot-remove scenario, if we don't probe acpiphp module on the guest, 'device_del' will never emit DEVICE_DELETED event(because guest will not write to __EJ0) . So we can confirm that hot-remove failed. But IIUC, there is no event such as DEVICE_ADDED, so 1) How can we confirm

Re: [Qemu-devel] [Question] How can we confirm hot-plug disk succesfully?

Resend 在 6/18/2017 3:21 PM, Xie Changlong 写道: Hi all In device hot-remove scenario, if we don't probe acpiphp module on the guest, 'device_del' will never emit DEVICE_DELETED event(because guest will not write to __EJ0) . So we can confirm that hot-remove failed. But IIUC, there is no event

Re: [Qemu-devel] [Question] How can we confirm hot-plug disk succesfully?

在 6/19/2017 3:27 PM, Kevin Wolf 写道: Am 18.06.2017 um 09:21 hat Xie Changlong geschrieben: In device hot-remove scenario, if we don't probe acpiphp module on the guest, 'device_del' will never emit DEVICE_DELETED event(because guest will not write to __EJ0) . So we can confirm that hot-remove

Re: [Qemu-devel] [PATCH v3 20/20] block: Make bdrv_is_allocated_above() byte-based

t.c| 20 block/io.c| 42 -- block/mirror.c| 5 - block/replication.c | 17 - For replication part: Reviewed-by: Xie Changlong <xiechangl...@cmss.chinamobile.com> block

Re: [Qemu-devel] [PATCH v3 15/20] backup: Switch block_backup.h to byte-based

- v2: change a couple more parameter names --- include/block/block_backup.h | 11 +-- block/backup.c | 33 - block/replication.c | 12 Reviewed-by: Xie Changlong <xiechangl...@cmss.chinamobile.com> 3 files chan

Re: [Qemu-devel] [PATCH] replication: Fix replication open fail

ng.guan...@zte.com.cn> > Signed-off-by: Wang Yong <wang.yong...@zte.com.cn> Thanks, this patch fixs the problem in http://lists.nongnu.org/archive/html/qemu-devel/2017-08/msg03358.html. Reviewed-by: Xie Changlong <xiechangl...@cmss.chinamobile.com> > --- > block/replica