From patchwork Fri Jan 4 10:02:41 2013 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: Fix : Enable qemu-img QED image commit support. Date: Fri, 04 Jan 2013 00:02:41 -0000 From: Onkar N Mahajan X-Patchwork-Id: 209495 Message-Id: <1357293761.2078.17.camel@oc2826874472.ibm.com> To: qemu-devel Cc: Anthony Liguori , Stefan Hajnoczi Running qemu-img commit on QED image gives this message even if the image is never committed. This patch fixes this. Do we need to do any L1, L2 table cleanup here ? I see that cleanup code is commented out in the case of qcow2 (qcow2_make_empty). before patching - # qemu-img commit -f qed ss.qed qemu-img: Image is already committed even before committing the image. after patching - # qemu-img commit -f qed ss.qed Image committed. and image is actually successfully committed. ------------------------------------------------------- Signed-off-by: Onkar N Mahajan/India/IBM Nacked-by: QEMU Patches --- block/qed.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) static BDRVQEDState *acb_to_s(QEDAIOCB *acb) diff --git a/block/qed.c b/block/qed.c index 6c182ca..32f1d53 100644 --- a/block/qed.c +++ b/block/qed.c @@ -695,7 +695,7 @@ static int coroutine_fn bdrv_qed_co_is_allocated(BlockDriverState *bs, static int bdrv_qed_make_empty(BlockDriverState *bs) { - return -ENOTSUP; + return 0; }