On 12/4/25, 7:53 AM, "Vladimir Sementsov-Ogievskiy" <[email protected] <mailto:[email protected]>> wrote:
> [PATCH v9 0/8] virtio-net: live-TAP local migration > https://urldefense.com/v3/__https://patchew.org/QEMU/[email protected] > > <mailto:[email protected]>/__;!!GjvTz_vk!Wv8g8JpZGOl96S-RX_T81d0fwPei5C-fKhKAUqM5DJmec3xKhFaStiinE3IFLyUwrs1UQrdQgth3VU1HRlblRjjmVA$ > , which bring same thing: migrate TAP device, passing FDs > though migration channel. The benefit is that it doesn't > require additional migration channel. Hi Vladimir, Thanks for sending this. I tried testing your patch set and I got the following errors from qemu 2025-12-08T20:44:31.251153Z qemu-system-x86_64: 8 != 101 2025-12-08T20:44:31.251199Z qemu-system-x86_64: Failed to load element of type uint16 equal for max_queue_pairs: -22 2025-12-08T20:44:31.251492Z qemu-system-x86_64: warning: qemu_fclose: received fd 141 was never claimed 2025-12-08T20:44:31.251497Z qemu-system-x86_64: warning: qemu_fclose: received fd 142 was never claimed 2025-12-08T20:44:31.251501Z qemu-system-x86_64: warning: qemu_fclose: received fd 143 was never claimed 2025-12-08T20:44:31.251524Z qemu-system-x86_64: load of migration failed: Invalid argument: error while loading state for instance 0x0 of device '0000:00:03.0/virtio-net': Failed to load element of type virtio for virtio: -22
