diff options
| author | Avihai Horon <avihaih@nvidia.com> | 2023-09-06 18:08:52 +0300 |
|---|---|---|
| committer | Cédric Le Goater <clg@redhat.com> | 2023-09-11 08:34:06 +0200 |
| commit | bf7ef7a2da3e61dc104f26c679c9465e3fbe7dde (patch) | |
| tree | 8ae92216df15dcd7d8a1215c298758fcad122fad /hw/net/virtio-net.c | |
| parent | 08fc4cb51774f763dcc6fd74637aa9e00eb6a0ba (diff) | |
| download | qemu-bf7ef7a2da3e61dc104f26c679c9465e3fbe7dde.zip qemu-bf7ef7a2da3e61dc104f26c679c9465e3fbe7dde.tar.gz qemu-bf7ef7a2da3e61dc104f26c679c9465e3fbe7dde.tar.bz2 | |
vfio/migration: Block VFIO migration with postcopy migration
VFIO migration is not compatible with postcopy migration. A VFIO device
in the destination can't handle page faults for pages that have not been
sent yet.
Doing such migration will cause the VM to crash in the destination:
qemu-system-x86_64: VFIO_MAP_DMA failed: Bad address
qemu-system-x86_64: vfio_dma_map(0x55a28c7659d0, 0xc0000, 0xb000, 0x7f1b11a00000) = -14 (Bad address)
qemu: hardware error: vfio: DMA mapping failed, unable to continue
To prevent this, block VFIO migration with postcopy migration.
Reported-by: Yanghang Liu <yanghliu@redhat.com>
Signed-off-by: Avihai Horon <avihaih@nvidia.com>
Tested-by: Yanghang Liu <yanghliu@redhat.com>
Reviewed-by: Peter Xu <peterx@redhat.com>
Signed-off-by: Cédric Le Goater <clg@redhat.com>
Diffstat (limited to 'hw/net/virtio-net.c')
0 files changed, 0 insertions, 0 deletions