I revoke my previous comments. Meanwhile it turned out that the server I
was testing with had HW problems (namely it couldn't handle 6x2GB RAM
despite of the motherboard docs claiming it would). So my error reports
are unreliable ... they might have been caused by HW issues.
--
kvm-84: virtio on
I'm also hit by bug#448694 which was the reason for using qcow2 images
in the first place. Now I'm pretty much left in the cold ... cannot use
RAW or LVM ... and neither qcow2. What am I supposed to store my guest
filesystems in then? :-(
--
kvm-84: virtio on qcow2 broken (regression)
https://bug
Btw: I do not use virtio in any of my guests, only emulated IDE
controllers ... which is most probably a big difference compared to the
original bug report.
--
kvm-84: virtio on qcow2 broken (regression)
https://bugs.launchpad.net/bugs/404394
You received this bug notification because you are a m
I hope I'm not getting lynched :-), but I'd like to reopen this bug as not
fixed. Previously you wrote that Karmic is not affected, however I've
experienced filesystem corruption inside qcow2 images. It's a bit hard to
reproduce since I had it in Windows 2003 guests, but I'll try to create a tes
