This bug was fixed in the package qemu-kvm - 0.12.3+noroms-0ubuntu9.5
---
qemu-kvm (0.12.3+noroms-0ubuntu9.5) lucid-proposed; urgency=low
* debian/patches/block-fix-sector-comparison.patch: Fix virtio disk
corruption with large (1Tb) volumes (LP: #574665)
-- Serge Hallyn
** Branch linked: lp:ubuntu/lucid-updates/qemu-kvm
--
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/574665
Title:
kvm + virtio disk corrupts large volumes (1TB).
--
I've tested the packages (especially qemu*) from lucid-proposed
successfully. This time on a different machine but same hard- and
software setup as before. Intense read and write tests on a 2TB
filesystem ran for 24h without corrupting the filesystem.
--
You received this bug notification
** Tags added: verification-done
** Tags removed: verification-needed
--
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/574665
Title:
kvm + virtio disk corrupts large volumes (1TB).
Accepted qemu-kvm into lucid-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: qemu-kvm (Ubuntu Lucid)
Thanks for this patch! I can confirm its functionality. I'm using a
(host) - hardware raid 1 - lvm - drbd [2TB] - (virtual machine)
setup that fails (corrupts filesystems) repeatedly using the stock qemu-
kvm implementation in lucid. After exchanging the the original qemu
packages with the patched
Thanks very much, Richard!
** Tags added: verification-done
** Tags removed: verification-needed
--
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/574665
Title:
kvm + virtio disk
Removed verification-done .. as the package hasn't been tested from
lucid-proposed yet.
** Tags removed: verification-done
--
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/574665
** Branch linked: lp:~serge-hallyn/ubuntu/lucid/qemu-kvm/virtio-
corrupt-2
--
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/574665
Title:
kvm + virtio disk corrupts large volumes
proposed, should be accepted.
--
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/574665
Title:
kvm + virtio disk corrupts large volumes (1TB).
--
Ubuntu-server-bugs mailing list
Thank you for backporting this patch, Serge! What will it take to get
things rolling again for this to be included in lucid-updates? Are you
just waiting for someone else to verify that the patch works in their
setup? If so, we could probably give it a shot.
--
You received this bug notification
Thanks, Brian, yes I need someone other than myself to confirm the fix.
Greatly appreciated if you could!
--
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/574665
Title:
kvm + virtio
OK, a fellow sysadmin here is going to test the patch in our setup.
He'll post the result here. There's a good chance he'll be able to do it
this week, or perhaps next week.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
packages created by https://code.launchpad.net/~serge-
hallyn/ubuntu/lucid/qemu-kvm/virtio-corrupt.
** Attachment added: qemu-virtio-tst1.tgz
https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/574665/+attachment/1822480/+files/qemu-virtio-tst1.tgz
--
You received this bug notification
My first few tests appear to verify that (a) stock lucid qemu-kvm
succeeds with 1.1T virtio disk (on a raw LVM partition), fails with 1.3T
virtio disk, and that the qemu-kvm from the attached qemu-virtio-
tst1.tgz tarball (which is compiled from lp:~serge-hallyn/ubuntu/lucid
Several more tests have been 100% successful.
--
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/574665
Title:
kvm + virtio disk corrupts large volumes (1TB).
--
Ubuntu-server-bugs
** Description changed:
Binary package hint: qemu-kvm
See this bug:
http://sourceforge.net/tracker/index.php?func=detailaid=2933400group_id=180599atid=893831
I have confirmed that this happens with 10.04 host and guest. Giving kvm
a logical virtio volume of 1024 GB works; a
Quoting Unlogic (574...@bugs.launchpad.net):
Good point!
Why keep struggling with patches for 0.12.4 instead of just moving on to
0.12.5 as in 10.10?
10.10 has it's own set of bugs, pertaining to 32-bit guests and hosts,
which I've not quite had the hardware to faithfully reproduce.
--
You
** Changed in: qemu-kvm (Ubuntu Lucid)
Status: Triaged = In Progress
--
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/574665
Title:
kvm + virtio disk corrupts large volumes
I've taken the proposed patch from http://marc.info/?l=qemu-
develm=127436114712437 and applied it to lucid's qemu-kvm. The
resulting source is at https://code.launchpad.net/~serge-
hallyn/ubuntu/lucid/qemu-kvm/virtio-corrupt and the package is building
in ppa:serge-hallyn/virt.
Could you please
Unfortunately, I no longer have that particular configuration available
for testing. (It's now in production, and I can no longer risk destroying
the data on the disks.)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
just out of curiosity, 0.12.5 works well, why not just use it?
even dist-upgrade to 10.10 which has 0.12.5 would probably be less
painful than having to test/deal with this bug.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm
Good point!
Why keep struggling with patches for 0.12.4 instead of just moving on to
0.12.5 as in 10.10?
--
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/574665
Title:
kvm + virtio
Is there any way to speedup the backports process cause kvm 0.12.3 that
currently ships with Lucid has a few serious bugs which are fixed in
0.12.5.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
@Kendall: I wouldn't be surprised, there have been lots of disk corruption bugs
in the 0.12 series and the qemu-kvm project obviously has problems with project
management (bug reports being ignored, poor QA etc).
Anyway, see:
http://www.linux-kvm.com/content/qemu-kvm-0125-released-bugfixes
(backport requested with LP: #632528)
--
kvm + virtio disk corrupts large volumes (1TB).
https://bugs.launchpad.net/bugs/574665
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Is there any chance this bug can still affect an ext4 filesystem on a
partition that is just slightly under 1TB? I originally experience this
bug and, to work around it, re-partitioned my 1.5 TB drive into two
partitions. Since then I've not experience any issues until today when I
got some
Note that this is fixed in 0.12.5 which is currently in Maverick.
** Changed in: qemu-kvm (Ubuntu Maverick)
Status: Triaged = Fix Released
--
kvm + virtio disk corrupts large volumes (1TB).
https://bugs.launchpad.net/bugs/574665
You received this bug notification because you are a member
In the next week, I intend to push 0.12.5 to lucid-backports. Will update when
the merge has been proposed.
--
kvm + virtio disk corrupts large volumes (1TB).
https://bugs.launchpad.net/bugs/574665
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Dustin, any progress on this one ?
If you don't have the time to work on it, maybe reassign to Serge.
--
kvm + virtio disk corrupts large volumes (1TB).
https://bugs.launchpad.net/bugs/574665
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
** Changed in: qemu-kvm (Ubuntu Lucid)
Assignee: Dustin Kirkland (kirkland) = Serge Hallyn (serge-hallyn)
** Changed in: qemu-kvm (Ubuntu Maverick)
Assignee: Dustin Kirkland (kirkland) = Serge Hallyn (serge-hallyn)
--
kvm + virtio disk corrupts large volumes (1TB).
Seems more tricky to patch than expected, more things contributing to this
defect.
There was some regression on gentoo as well, patched/fixed in -r1 and
re-introduced in -r2 although the previous patch was in.
Most efficient solution will be not to patch. Update to 0.12.5 which
fixes the
I'm experiencing a similar issue, albeit with slightly different
hardware. I have several VMs backed by SAN storage, accessed through a
QLogic 2560 controller. All of my volumes that are 1TB seem to
function without issue. On the larger volumes (one in particular is
7TB with an XFS filesystem),
On 2010-06-24 22:24 - (Thu), Steven Wagner wrote:
As mentioned in comment #3, could this be related to a specific SATA
chipset?...Ive noticed no difference for if the guest is using virtio
or ide mode.
For me the guests work fine in IDE mode; it's only virtio that has a
problem. So, in a
@curt: did you try copying 60gb from one raw ide disk to another within
ubuntu guest?
--
kvm + virtio disk corrupts large volumes (1TB).
https://bugs.launchpad.net/bugs/574665
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in
@steven: what you're describing seems to be a different issue though, sounds
rather host related.
anyway the whole ide guest story is a bit offtopic here, Ill open a new bug for
this as soon as I have time to do more tests.
--
kvm + virtio disk corrupts large volumes (1TB).
As mentioned in comment #3, could this be related to a specific SATA
chipset? I have a Intel 82801JI ICH10 SATA AHCI Controller, and have
experienced random disk corruption on guests. Guests are both Linux and
Win2k3. High usage on the sata controller seemed to be the trigger. Ive
noticed no
Yes. That seemed to help. 0.12.4 + patch.
--
kvm + virtio disk corrupts large volumes (1TB).
https://bugs.launchpad.net/bugs/574665
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Ubuntu-server-bugs mailing list
Ubuntu Developers: Is there any chance to bump qemu-kvm to 0.12.4 in
lucid? This would also fix a few other bugs.
If not we should have to backport a few other commits who are possible
related to this bug.
--
kvm + virtio disk corrupts large volumes (1TB).
The patch has now been pushed to qemu as well as qemu-kvm
http://git.savannah.gnu.org/cgit/qemu.git/commit/?id=77be4366baface6613cfc312ba281f8e5860997c
http://git.kernel.org/?p=virt/kvm/qemu-kvm.git;a=commit;h=77be4366baface6613cfc312ba281f8e5860997c
--
kvm + virtio disk corrupts large volumes
I patched qemu-kvm (0.12.3+noroms-0ubuntu9) with patch
(http://marc.info/?l=qemu-develm=127436114712437) and compiled but
still my 4TB partition corrupts.
I have setup where I have 4TB partition (from LVM) as a virtio-device in
qemu-kvm. I have LVM also inside virtual machine and having 4GB
try to patch qemu-kvm 0.12.4, seemed to me there were other changes
contributing to this fix in 0.12.4.
I verified that it works on gentoo
http://bugs.gentoo.org/show_bug.cgi?id=321005, at least using 1.5TB disk.
** Bug watch added: Gentoo Bugzilla #321005
This is fixed by http://marc.info/?l=qemu-develm=127436114712437
--
kvm + virtio disk corrupts large volumes (1TB).
https://bugs.launchpad.net/bugs/574665
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to qemu-kvm in ubuntu.
--
Thanks for the pointer, Michael. I don't see where this has landed in
either the upstream qemu or qemu-kvm git yet. As soon as it does, I'll
cherry pick the fix for Ubuntu 10.04. Thanks.
** Changed in: qemu-kvm (Ubuntu)
Status: Confirmed = In Progress
** Changed in: qemu-kvm (Ubuntu)
i can confirm this issue. virtio plus guest volumes (qcow2/raw seems
irrelevant, tried both with errors) 1T causes image corruption. the
used disk space in the guests did not matter in my case. io errors
showed sometimes at 10gb, sometimes later when already ~750gb were
copied onto the virtual
masc, the bug you pointed out appears to be when using a particular
hardware SATA chipset; KVM isn't mentioned anywhere there. Are you
saying that this happens with KVM guests when running on hosts without
this problem?
Using dd, I wrote new 60GB file (writing zeros) on a guest using the KVM
IDE
yes, writing is not enough though. try copying 60 GB from one ide disk
to another.
there's plenty of those ata exception bugs floating around, I just picked the
closest example.
failures during WRITE_DMA_EXT are most common.
--
kvm + virtio disk corrupts large volumes (1TB).
Marking Confirmed/High, added upstream bug.
** Bug watch added: SourceForge.net Tracker #2933400
http://sourceforge.net/support/tracker.php?aid=2933400
** Also affects: kvm via
http://sourceforge.net/support/tracker.php?aid=2933400
Importance: Unknown
Status: Unknown
** Changed
Even though there's no corruption, ide cannot be considered an
acceptable workaround with kvm.
Ata exceptions will occur mostly when writing large files. (eg.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/279693). Proposed
workarounds like putting cd in drive don't work with kvm. All
49 matches
Mail list logo
