I started playing with this by just doing: qemu-img create -f qcow2 x.img 2G (boot a vm from a cdrom/iso into rescue mode with x.img as a drive, and there do): dd if=/dev/zero of=/mnt/zero1 bs=1M count=1000 and then cp /mnt/zero1 /mnt/zero2 rm /mnt/zero2 cp /mnt/zero1 /mnt/zero3 (etc)
Here the volume doesn't exceed it's allocation (which was 2G). I created snapshots but still did not exceed 2G. When I started adding more real data (booted from an installed server virtual disk, but I don't believe that made a difference) as well as creating snapshots, I worked up to a 3.2G real disk. In the disk you showed in the bug description, had you created any snapshots? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1025244 Title: qcow2 image increasing disk size above the virtual limit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1025244/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
