I was the original submitter of the qcow2 corruption observed, fixed by
reverting old change thread on the qemu-de...@nongnu.org list, after
finding corruption when testing kvm-83.
I've just submitted an update to the qemu and kvm lists, saying that the
symptom I observed (a blue screen while
See also bug #404394, which suggests there are still qcow2 bugs in the
Ubuntu package.
--
qcow2 corruption
https://bugs.launchpad.net/bugs/361938
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This bug was fixed in the package kvm - 1:84+dfsg-0ubuntu11
---
kvm (1:84+dfsg-0ubuntu11) jaunty; urgency=low
* debian/patches/add-all-virtio-drives.patch: Fix bugs where the caller
does not specify a perfectly defined list of virtio drives starting at
index=0 and having no
http://git.kernel.org/?p=virt/kvm/kvm-
userspace.git;a=commitdiff;h=385aae33c08e17ec63671b9fa1c503c21283bc1f;hp=b335c2b5762259c827bae487dca26441497a96cb
qcow2's get_cluster_offset() scans forward in the l2 table to find other
clusters that have the same allocation status as the first cluster.
