Marking as "Won't Fix" according to the last comment.
** Changed in: qemu
Status: New => Won't Fix
--
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
We can't just reopen files, we don't know what state they are in. Any
data that has been written to the image between the last flush and the
point where gluster made the fd invalid may be there or may be missing.
If any data is missing, we can't continue the guest or you'll get data
corruption.
Hi Kevin,
I understand. In this case (where the gluster process was killed or
crashed) I guess the best option would be to poweroff and restart the
VM, which can be done client-side (ovirt + libvirt)
Please mark as Won't fix.
Thanks.
--
You received this bug notification because you are a
