Can one of you give some more information about the qcow2 image that can't be opened any more? What is new is a sanity check of the snapshot metadata (name, date, etc.) size. It is currently limited to 64 MB, which should be plenty of space for any real use cases.
I suspect that your qcow2 got somehow corrupted (before the update; the update only made the problem apparent) and this is not real snapshot data. If you have the qemu sources, you can run 'tests/qemu-iotests/qcow2.py /tmp/test.qcow2 dump-header' (with your image file instead of test.qcow2, of course) and check the values of nb_snapshots and snapshot_offset. If you could post a hexdump of a few kilobytes starting at $snapshot_offset, that could be helpful as well. -- You received this bug notification because you are a member of qemu- devel-ml, which is subscribed to QEMU. https://bugs.launchpad.net/bugs/1354167 Title: On VM restart: Could not open 'poppy.qcow2': Could not read snapshots: File too large Status in QEMU: New Bug description: I'm unable to restart a VM. virt-manager is giving me: Error starting domain: internal error: process exited while connecting to monitor: qemu-system-x86_64: -drive file=/var/lib/libvirt/images/poppy.qcow2,if=none,id=drive-virtio- disk0,format=qcow2: could not open disk image /var/lib/libvirt/images/poppy.qcow2: Could not read snapshots: File too large From the command line trying to check the image also gives me: qemu-img check poppy.qcow2 qemu-img: Could not open 'poppy.qcow2': Could not read snapshots: File too large This bug appears with both the default install of qemu for ubuntu 14.04: qemu-img version 2.0.0, Copyright (c) 2004-2008 Fabrice Bellard And the latest version. qemu-img version 2.1.50, Copyright (c) 2004-2008 Fabrice Bellard Host: Dual E5-2650 v2 @ 2.60GHz 32GB Memory 4TB Disk space (2.1TB Free) Host OS: Ubuntu 14.04.1 LTS 64bit Guest: Ubuntu 14.04 64bit Storage Size: 500gb To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1354167/+subscriptions
