diff options
| author | Eugenio Pérez <eperezma@redhat.com> | 2023-03-03 18:24:42 +0100 |
|---|---|---|
| committer | Michael S. Tsirkin <mst@redhat.com> | 2023-03-07 12:38:59 -0500 |
| commit | 5c1ebd4c432eda629aeb7a4ecab45220d0272616 (patch) | |
| tree | f4a71f73a03cdafdc11ef1ebee40395dbea01bb8 /net/tap_int.h | |
| parent | 9c363cf6d5982c568431531a8da26ccb0fcb3038 (diff) | |
| download | qemu-5c1ebd4c432eda629aeb7a4ecab45220d0272616.zip qemu-5c1ebd4c432eda629aeb7a4ecab45220d0272616.tar.gz qemu-5c1ebd4c432eda629aeb7a4ecab45220d0272616.tar.bz2 | |
vdpa: block migration if device has unsupported features
A vdpa net device must initialize with SVQ in order to be migratable at
this moment, and initialization code verifies some conditions. If the
device is not initialized with the x-svq parameter, it will not expose
_F_LOG so the vhost subsystem will block VM migration from its
initialization.
Next patches change this, so we need to verify migration conditions
differently.
QEMU only supports a subset of net features in SVQ, and it cannot
migrate state that cannot track or restore in the destination. Add a
migration blocker if the device offers an unsupported feature.
Signed-off-by: Eugenio Pérez <eperezma@redhat.com>
Message-Id: <20230303172445.1089785-12-eperezma@redhat.com>
Tested-by: Lei Yang <leiyang@redhat.com>
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
Diffstat (limited to 'net/tap_int.h')
0 files changed, 0 insertions, 0 deletions