On Wed, Jan 31, 2024 at 11:07 AM Si-Wei Liu wrote:
>
> Hi Eugenio,
>
> Maybe there's some patch missing, but I saw this core dump when x-svq=on
> is specified while waiting for the incoming migration on destination host:
>
> (gdb) bt
> #0 0x5643b24cc13c in vhost_iova_tree_map_alloc
Hi Eugenio,
Maybe there's some patch missing, but I saw this core dump when x-svq=on
is specified while waiting for the incoming migration on destination host:
(gdb) bt
#0 0x5643b24cc13c in vhost_iova_tree_map_alloc (tree=0x0,
map=map@entry=0x7ffd58c54830) at
To map the guest memory while it is migrating we need to create the
iova_tree, as long as the destination uses x-svq=on. Checking to not
override it.
The function vhost_vdpa_net_client_stop clear it if the device is
stopped. If the guest starts the device again, the iova tree is
recreated by
