A few notes after a few weeks of playing with this.
I've not reproduced the failure with migration per se.
However, when I did not add 'aio=native' to the backing store flags (i.e. file=/mnt/disk.img,if=virtio,cache=none,aio=native), after around 2 days qemu would exit saying
This appears to me to be a bug in the underlying gluster mount.
Until it is verified that this can be reproduced with another shared backing store and is not simply a result of bad behavior of the underlying glusterfs, priority of this bug will be lowered.
A few notes after a few weeks of playing with this.
I've not reproduced the failure with migration per se.
However, when I did not add 'aio=native' to the backing store flags (i.e. file=/mnt/ disk.img, if=virtio, cache=none, aio=native) , after around 2 days qemu would exit saying
(qemu) qemu: qemu_thread_create: Resource temporarily unavailable
This appears to me to be a bug in the underlying gluster mount.
Until it is verified that this can be reproduced with another shared backing store and is not simply a result of bad behavior of the underlying glusterfs, priority of this bug will be lowered.