[Qemu-devel] [Bug 1450891] [NEW] VM will not resume on GlusterFS

[Christopher Pereira]

Public bug reported:

oVirt uses libvirt to run QEMU.
Images are passed to QEMU as files, not file descriptors.
When running images from a GlusterFS, the file descriptors may get invalidated 
because of network problems or the glusterfs process being restarted.
In this case, the VM goes into paused state.
When trying to resume the VM ('cont' command), QEMU uses the same invalidated 
file descriptors throwing a:
"block I/O error in device 'drive-virtio-disk0': Transport endpoint is not 
connected (107)".

Please check file-descriptors and reopen image file on 'cont' event in QEMU.
Thanks.

References:

[1] http://lists.nongnu.org/archive/html/qemu-devel/2015-03/msg01269.html
[2] https://bugzilla.redhat.com/show_bug.cgi?id=1058300

** Affects: qemu
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1450891

Title:
  VM will not resume on GlusterFS

Status in QEMU:
  New

Bug description:
  oVirt uses libvirt to run QEMU.
  Images are passed to QEMU as files, not file descriptors.
  When running images from a GlusterFS, the file descriptors may get 
invalidated because of network problems or the glusterfs process being 
restarted.
  In this case, the VM goes into paused state.
  When trying to resume the VM ('cont' command), QEMU uses the same invalidated 
file descriptors throwing a:
  "block I/O error in device 'drive-virtio-disk0': Transport endpoint is not 
connected (107)".

  Please check file-descriptors and reopen image file on 'cont' event in QEMU.
  Thanks.

  References:

  [1] http://lists.nongnu.org/archive/html/qemu-devel/2015-03/msg01269.html
  [2] https://bugzilla.redhat.com/show_bug.cgi?id=1058300

To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1450891/+subscriptions