bump version to 2.6.2-2

[pve-qemu-kvm.git] / debian / patches / pve / 0014-vma-restore-tolerate-a-size-difference-up-to-4M.patch

From b60a9ba781fc9e4f1a8c7d177f20933340cf4fc4 Mon Sep 17 00:00:00 2001
From: Dietmar Maurer <dietmar@proxmox.com>
Date: Tue, 26 Mar 2013 06:21:16 +0100
Subject: [PATCH 14/55] vma restore: tolerate a size difference up to 4M

Signed-off-by: Dietmar Maurer <dietmar@proxmox.com>
---
 vma-reader.c | 8 +++++++-
 1 file changed, 7 insertions(+), 1 deletion(-)

diff --git a/vma-reader.c b/vma-reader.c
index 9d92c6a..d9f43fe 100644
--- a/vma-reader.c
+++ b/vma-reader.c
@@ -465,7 +465,13 @@ int vma_reader_register_bs(VmaReader *vmar, guint8 dev_id, BlockDriverState *bs,
     assert(vmar->rstate[dev_id].bs == NULL);
 
     int64_t size = bdrv_getlength(bs);
-    if (size != vmar->devinfo[dev_id].size) {
+    int64_t size_diff = size - vmar->devinfo[dev_id].size;
+
+    /* storage types can have different size restrictions, so it
+     * is not always possible to create an image with exact size.
+     * So we tolerate a size difference up to 4MB.
+     */
+    if ((size_diff < 0) || (size_diff > 4*1024*1024)) {
         error_setg(errp, "vma_reader_register_bs for stream %s failed - "
                    "unexpected size %zd != %zd", vmar->devinfo[dev_id].devname,
                    size, vmar->devinfo[dev_id].size);
-- 
2.1.4