** Description changed: Binary package hint: qemu-kvm See this bug: http://sourceforge.net/tracker/index.php?func=detail&aid=2933400&group_id=180599&atid=893831 I have confirmed that this happens with 10.04 host and guest. Giving kvm a logical virtio volume of 1024 GB works; a logical volume of 1048 GB fails to install and produces disk errors on the guest (but not on the host). Changing the kvm configuration to use an IDE volume instead works fine even with a 1.7TB volume. - Note that, because this can introduce disk corruption, this *really* - needs to go into the release notes. + SRU Justification: + + 1. Impact: Use of > 1Tb virtio disk in kvm will almost certainly cause data corruption + 2. How bug addressed: A minimal patch was cherry-picked from upstream, which addresses the fact that the difference between the start addresses of two requests can be > sizeof(int). + 3. Patch: See lp:~serge-hallyn/ubuntu/lucid/qemu-kvm/virtio-corrupt, in particular the patch block-fix-sector-comparison.patch. + 4. To reproduce: Create a 1.3Tb qemu disk or LVM partition. Run kvm with this as the virtio hard drive and a natty installer as cdrom. Select the default drive configurations (use whole disk with LVM). The installer will hang at this step. + qemu-img create -f raw test.img 1300G + kvm -cdrom natty-server-amd64.iso -drive file=test.img,if=virtio,index=0 -boot d -m 2G + 5. Regression potential: The patch is taken from upstream. If there is a regression, it can only impact qemu-kvm itself.
** Tags added: verification-needed ** Description changed: Binary package hint: qemu-kvm See this bug: http://sourceforge.net/tracker/index.php?func=detail&aid=2933400&group_id=180599&atid=893831 I have confirmed that this happens with 10.04 host and guest. Giving kvm a logical virtio volume of 1024 GB works; a logical volume of 1048 GB fails to install and produces disk errors on the guest (but not on the host). Changing the kvm configuration to use an IDE volume instead works fine even with a 1.7TB volume. SRU Justification: 1. Impact: Use of > 1Tb virtio disk in kvm will almost certainly cause data corruption 2. How bug addressed: A minimal patch was cherry-picked from upstream, which addresses the fact that the difference between the start addresses of two requests can be > sizeof(int). - 3. Patch: See lp:~serge-hallyn/ubuntu/lucid/qemu-kvm/virtio-corrupt, in particular the patch block-fix-sector-comparison.patch. + 3. Patch: See lp:~serge-hallyn/ubuntu/lucid/qemu-kvm/virtio-corrupt, in particular the patch block-fix-sector-comparison.patch. 4. To reproduce: Create a 1.3Tb qemu disk or LVM partition. Run kvm with this as the virtio hard drive and a natty installer as cdrom. Select the default drive configurations (use whole disk with LVM). The installer will hang at this step. - qemu-img create -f raw test.img 1300G - kvm -cdrom natty-server-amd64.iso -drive file=test.img,if=virtio,index=0 -boot d -m 2G + qemu-img create -f raw test.img 1300G + kvm -cdrom natty-server-amd64.iso -drive file=test.img,if=virtio,index=0 -boot d -m 2G + Re-test with the packages from the attached qemu-virtio-tst1.tgz tarball. The VM should now successfully install and be fully, reliably useful. 5. Regression potential: The patch is taken from upstream. If there is a regression, it can only impact qemu-kvm itself. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/574665 Title: kvm + virtio disk corrupts large volumes (>1TB). -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
