Re: [Qemu-devel] [Bug 1025244] Re: qcow2 image increasing disk size above the virtual limit
On Tue, Dec 18, 2012 at 10:18:20AM -, Andy Menzel wrote: > Any solution right now? I have a similar problem like Todor Andreev; > Our daily backup of some virtual machines (qcow2) looks like that: > > 1. shutdown the VM > 2. create a snapshot via: "qemu-img snapshot -c nameofsnapshot..." > 3. boot the VM > 4. backup the snapshot to another virtual disk via: "qemu-img convert -f > qcow2 -O qcow2 -s nameofsnapshot..." > 5. DELETE the snapshot from VM via: qemu-img snapshot -d nameofsnapshot... It's not safe to modify the qcow2 file while the guest is running. This means Step 5 is not really safe and could result in an inconsistent image. This may also be causing the problem: the QEMU process has a variable with the next free cluster index. Since Step 5 runs as a separate process it does not update the QEMU process' next free cluster index variable. QEMU doesn't know that there are now free clusters within the image file because you updated the file behind QEMU's back - the result is that it grows the file. Please try deleting the last backup snapshot between Step 1 and Step 2. This way you'll free the space while QEMU isn't accessing the image file. When you boot up the image file again QEMU should reuse the freed clusters. Stefan -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in 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/qemu/+bug/1025244/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1079713] Re: [Qemu-devel] [PATCH 1.3] qapi: handle visitor->type_size() in QapiDeallocVisitor
On Mon, Nov 26, 2012 at 1:43 PM, Andreas Färber wrote: > Am 26.11.2012 13:10, schrieb Stefan Hajnoczi: >> visit_type_size() requires either visitor->type_size() or >> visitor_uint64() to be implemented, otherwise a NULL function pointer is >> invoked. >> >> It is possible to trigger this crash as follows: >> >> $ qemu-system-x86_64 -netdev tap,sndbuf=0,id=netdev0 \ >>-device virtio-blk-pci,netdev=netdev0 >> >> The 'sndbuf' option has type "size". >> >> Signed-off-by: Stefan Hajnoczi >> --- >> This patch ensures that -netdev tap,sndbuf=X works in QEMU 1.3. > > Reviewed-by: Andreas Färber > > Did you check whether any other types were unhandled? The visitors do not handle all types. Only the opts visitor and now the dealloc visitor handle ->type_size(). This will not cause a problem yet because only the netdev options include fields with the 'size' type. That code path is now covered. In the longer term we should clean up the int, number, uint64, size type proliferation and handle them consistently. > Should a comment be added somewhere along the lines of "If you add a > hook here you also need to implement one there" to avoid such > inconsistency for the future? There is no single point like register_visitor() where we could check that callbacks are set up. That would have been a nice way to prevent incomplete visitors. The issue is that qapi/qapi-visit-core.h says type_uint64 and type_size may be NULL, but it documents that visit_type_size() falls back to type_uint64() if type_size() is NULL. The case we hit was that type_uint64() is also NULL. Should it fall back to type_int() (int64_t)? Stefan -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1079713 Title: failed to set sndbuf on VMs network interface To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1079713/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 658610] Re: Check whether images have write permissions
Can you please add steps to reproduce this bug? It's not clear to me when this happens. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/658610 Title: Check whether images have write permissions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
