On 03/07/2010 04:28 AM, Michael Tokarev wrote:
Antoine Martin wrote:
Hi,
With qemu-kvm-0.12.3:
./qemu-system-x86_64 [..] -drive file=/dev/sdc9,if=virtio,cache=none [..]
[ 1.882843] vdc:
[ 2.365154] udev: starting version 146
[ 2.693768] end_request: I/O error, dev vdc, sector 126
[ 2.693772] Buffer I/O error on device vdc, logical block 126
[ 2.693775] Buffer I/O error on device vdc, logical block 127
[ 2.693777] Buffer I/O error on device vdc, logical block 128
..
[ 3.550076] end_request: I/O error, dev vdc, sector 0
Works fine with kvm-88:
cp /usr/src/KVM/kvm-88/pc-bios/*bin ./
cp /usr/src/KVM/kvm-88/x86_64-softmmu/qemu-system-x86_64 ./
./qemu-system-x86_64 [..] -drive file=/dev/sdc9,if=virtio,cache=none [..]
[ 1.650274] vdc: unknown partition table
[ 112.704164] EXT4-fs (vdc): mounted filesystem with ordered data mode
I've tried running as root, using the block device directly (as shown
above) rather than using a softlink, etc..
Something broke.
Host and guest are both running 2.6.33 and latest KVM.
https://sourceforge.net/tracker/?func=detail&atid=893831&aid=2933400&group_id=180599
The initial report is almost 8 weeks old!
Is data-corruption and data loss somehow less important than the
hundreds of patches that have been submitted since?? Or is there a fix
somewhere I've missed?
Cheers
Antoine
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
