[Bug 1178884] [NEW] unhelpful kvm error msg thrown when cache=none and no direct IO

[Jim Salter]

Public bug reported:

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.

** Affects: kvm (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to kvm in Ubuntu.
https://bugs.launchpad.net/bugs/1178884

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kvm/+bug/1178884/+subscriptions