On Tue, Aug 19, 2025 at 4:41 PM Vladimir Sementsov-Ogievskiy <vsement...@yandex-team.ru> wrote: > > On 19.08.25 05:45, Jason Wang wrote: > > On Mon, Aug 18, 2025 at 10:06 PM Vladimir Sementsov-Ogievskiy > > <vsement...@yandex-team.ru> wrote: > >> > >> Hi all! > >> > >> As preparation for further development of TAP live local migration > >> (passing open fds through unix socket), > > > > I'm not sure I understand this, but I think it has been supported now, > > or anything I miss? > > > > Hmm, may be I missing something, but where? > > I see no code which put TAP fd into migration channel. Nothing about > migration in tap.c at all. > > So, normally, to make local migration with TAP device, you have to create a > new TAP for new QEMU > process. > > I want to add a migration state, which will include needed part of TAPState, > including fd, > to continue using same TAP device in target process, avoiding also any > initialization steps > on that fd.
Ok, I see. But the question is that TAP is not something that is visible to guests. Doing that may be a suboptimal as we need to deal with the migration compatibility. Can we simply teach the management layer to use the same TAP fd instead assuming it's a local migration. Thanks > > -- > Best regards, > Vladimir >
