There are some patches in flight for using a nvlist for snapshot/restore. Wouldn't it be better to use it for migration too?
So, the sender could send a nvlist which contains information about all sections like memory, kern_structs etc. After that, both (sender and reciever) can send/recv all sections mentioned in the nvlist.

In D34720#924367, @corvink wrote:

There are some patches in flight for using a nvlist for snapshot/restore. Wouldn't it be better to use it for migration too?
So, the sender could send a nvlist which contains information about all sections like memory, kern_structs etc. After that, both (sender and reciever) can send/recv all sections mentioned in the nvlist.

Sounds good. Could you point me to those patches, please?

In D34720#926533, @mihaiburcea15_gmail.com wrote:

In D34720#924367, @corvink wrote:

There are some patches in flight for using a nvlist for snapshot/restore. Wouldn't it be better to use it for migration too?
So, the sender could send a nvlist which contains information about all sections like memory, kern_structs etc. After that, both (sender and reciever) can send/recv all sections mentioned in the nvlist.

Sounds good. Could you point me to those patches, please?

Unfortunately, there are currently no patches online. Just a proposal: https://lists.freebsd.org/archives/freebsd-virtualization/2023-May/001295.html. Nevertheless, I like the idea of sending a nvlist list as it's more flexible than your current approach.