Public bug reported:
When using io_perf corruption can be detected when using qemu-kvm-1.0.
A test case can be downloaded here:
http://people.canonical.com/~arges/lp1189926/lnv-382.tgz
Extract the contents and run ./create-disk, then ./test-kvm to test the
currently installed KVM. Keep in mind that 100GB+ of disk is required to run
the test.
This affects the qemu-kvm version in Precise, but is fixed in Quantal
and beyond.
It is expected that running the test case results in no disk corruption;
however we detect corruption on Precise.
Running git bisect on this test finds that commit
68d100e905453ebbeea8e915f4f18a2bd4339fe8 introduced the problem between v0.15.0
and v1.0.
Running git bisect in reverse finds that commit
b7ab0fea37c15ca9e249c42c46f5c48fd1a0943c fixes the issue between v1.1.2 and
v1.2.0.
However, b7ab0fea cannot be easily backported to v1.0 and 68d100e9 is a
large change to revert. However, both changes seem to indicate that the
problem lies in the qcow2 parts of the code.
bug 1040033 seems to be a related issue.
** Affects: qemu-kvm (Ubuntu)
Importance: Undecided
Status: Fix Released
** Affects: qemu-kvm (Ubuntu Precise)
Importance: High
Status: New
** Affects: qemu-kvm (Ubuntu Quantal)
Importance: Undecided
Status: Fix Released
** Also affects: qemu-kvm (Ubuntu Precise)
Importance: Undecided
Status: New
** Also affects: qemu-kvm (Ubuntu Quantal)
Importance: Undecided
Status: New
** Changed in: qemu-kvm (Ubuntu Precise)
Importance: Undecided => High
** Changed in: qemu-kvm (Ubuntu)
Importance: High => Undecided
** Changed in: qemu-kvm (Ubuntu)
Status: New => Fix Released
** Changed in: qemu-kvm (Ubuntu Quantal)
Status: New => Fix Released
** Description changed:
When using io_perf corruption can be detected when using qemu-kvm-1.0.
+ A test case can be downloaded here:
+ http://people.canonical.com/~arges/lp1189926/lnv-382.tgz
+ Extract the contents and run ./create-disk, then ./test-kvm to test the
currently installed KVM. Keep in mind that 100GB+ of disk is required to run
the test.
This affects the qemu-kvm version in Precise, but is fixed in Quantal
and beyond.
It is expected that running the test case results in no disk corruption;
however we detect corruption on Precise.
Running git bisect on this test finds that commit
68d100e905453ebbeea8e915f4f18a2bd4339fe8 introduced the problem between v0.15.0
and v1.0.
Running git bisect in reverse finds that commit
b7ab0fea37c15ca9e249c42c46f5c48fd1a0943c fixes the issue between v1.1.2 and
v1.2.0.
However, b7ab0fea cannot be easily backported to v1.0 and 68d100e9 is a
large change to revert. However, both changes seem to indicate that the
problem lies in the qcow2 parts of the code.
bug 1040033 seems to be a related issue.
--
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/1189926
Title:
data corruption in storage attached to VM using KVM
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1189926/+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
