I'm not sure this is completely fixed. I saw the following which states 0.11 still has the issue.
http://<email address hidden>/msg22891.html
The changelog for qemu-kvm doesn't make any mention of this bug either.
I was doing ISO testing for http://iso.qa.ubuntu.com/qatracker/result/3238/41 and had 3 other ISO tests running at the same time. I specified ubuntuKarmic to libvirt, which uses virtio. While the other 3 ISO tests worked fine, the one I did without LVM had problems in mountall:
mountall: Cancelled
General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and re-try.
This happened *after* I logged in as a regular user and the console kept alternating back and forth between the maintenance shell and the regular user shell. It was very confusing.
I checked dmesg and the only interesting thing I saw was:
[ 15.868803] JBD: barrier-based sync failed on vda1:8 - disabling barriers
I'm not sure this is completely fixed. I saw the following which states 0.11 still has the issue. /msg22891. html
http://<email address hidden>
The changelog for qemu-kvm doesn't make any mention of this bug either.
I was doing ISO testing for http:// iso.qa. ubuntu. com/qatracker/ result/ 3238/41 and had 3 other ISO tests running at the same time. I specified ubuntuKarmic to libvirt, which uses virtio. While the other 3 ISO tests worked fine, the one I did without LVM had problems in mountall:
mountall: Cancelled
General error mounting filesystems.
A maintenance shell will now be started.
CONTROL-D will terminate this shell and re-try.
This happened *after* I logged in as a regular user and the console kept alternating back and forth between the maintenance shell and the regular user shell. It was very confusing.
I checked dmesg and the only interesting thing I saw was:
[ 15.868803] JBD: barrier-based sync failed on vda1:8 - disabling barriers