a6df8adf3e
We don't migrate the followings fields for virtio-pci: uint32_t dfselect; uint32_t gfselect; uint32_t guest_features[2]; struct { uint16_t num; bool enabled; uint32_t desc[2]; uint32_t avail[2]; uint32_t used[2]; } vqs[VIRTIO_QUEUE_MAX]; This will confuse driver if migrating during initialization. Solves this issue by: - introduce transport specific callbacks to load and store extra virtqueue states. - add a new subsection for virtio to migrate transport specific modern device state. - implement pci specific callbacks. - add a new property for virtio-pci for whether or not to migrate extra state. - compat the migration for 2.4 and elder machine types Cc: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Jason Wang <jasowang@redhat.com> Reviewed-by: Michael S. Tsirkin <mst@redhat.com> Signed-off-by: Michael S. Tsirkin <mst@redhat.com> Reviewed-by: Cornelia Huck <cornelia.huck@de.ibm.com> |
||
---|---|---|
.. | ||
dataplane | ||
vhost-backend.h | ||
vhost-scsi.h | ||
vhost.h | ||
virtio-9p.h | ||
virtio-access.h | ||
virtio-balloon.h | ||
virtio-blk.h | ||
virtio-bus.h | ||
virtio-gpu.h | ||
virtio-input.h | ||
virtio-net.h | ||
virtio-rng.h | ||
virtio-scsi.h | ||
virtio-serial.h | ||
virtio.h |