Ubuntu
qemu package

unhelpful kvm error msg thrown when cache=none and no direct IO

Bug #1178884 reported by Jim Salter
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qemu (Ubuntu)
Expired
Wishlist
Unassigned

Bug Description

If you set cache=none to the definition of a guest's disk when the underlying storage subsystem does not support Direct I/O - for example, glusterFS or ZFSonLinux, or any FUSE filesystem - your guest will not start, and the error message thrown is a very generic "cannot connect to monitor".

Propose testing for Direct I/O, and trapping the error of Direct I/O not supported, and throwing an error (message for virsh, or dialog for virt-manager) that better explains the problem - "Direct I/O not supported for filesystem at [path to disk], cache=none not supported" would be nice.

Yolanda Robla (yolanda.robla)
Changed in kvm (Ubuntu):
status: New → Confirmed
importance: Undecided → Wishlist
Serge Hallyn (serge-hallyn)
affects: kvm (Ubuntu) → qemu (Ubuntu)
Revision history for this message
Michael Tokarev (mjt+launchpad-tls) wrote :

doesn't qemu itself print an error message in this case before exiting?

Revision history for this message
Serge Hallyn (serge-hallyn) wrote :

I just tested this with a fuse backend on wily but was unable to reproduce. Are you still having this error?

Changed in qemu (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for qemu (Ubuntu) because there has been no activity for 60 days.]

Changed in qemu (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.