On Fri, 12 Aug 2016 16:32:55 +0100
Stefan Hajnoczi wrote:
> The vq->inuse field is not migrated. Many devices don't hold
> VirtQueueElements across migration so it doesn't matter that vq->inuse
> starts at 0 on the destination QEMU.
>
> At least virtio-serial, virtio-blk, and virtio-balloon mig
On Fri, 08/12 16:32, Stefan Hajnoczi wrote:
> The vq->inuse field is not migrated. Many devices don't hold
> VirtQueueElements across migration so it doesn't matter that vq->inuse
> starts at 0 on the destination QEMU.
>
> At least virtio-serial, virtio-blk, and virtio-balloon migrate while
> hol
On Fri, Aug 12, 2016 at 04:32:55PM +0100, Stefan Hajnoczi wrote:
> The vq->inuse field is not migrated. Many devices don't hold
> VirtQueueElements across migration so it doesn't matter that vq->inuse
> starts at 0 on the destination QEMU.
>
> At least virtio-serial, virtio-blk, and virtio-balloo
The vq->inuse field is not migrated. Many devices don't hold
VirtQueueElements across migration so it doesn't matter that vq->inuse
starts at 0 on the destination QEMU.
At least virtio-serial, virtio-blk, and virtio-balloon migrate while
holding VirtQueueElements. For these devices we need to re
