On 28.08.2025 03:57, Akihiko Odaki wrote:
The posted call trace indicates a lockup happens in the control path,
but commit cefd67f25430 ("virtio-net: Fix num_buffers for version 1")
changes the data path.
On the other hand, I can come up with a possible failure scenario with
commit ce1431615292 ("virtio: Call set_features during reset"). Perhaps
it changed the machine state before loading the migrated state, and
caused a mismatch between them.
Yes, the problem commit is 0caed25cd171c6 "virtio: Call set_features
during reset", - the OP corrected himself in the next message (subject
line updated).
I need more information to understand the issue. A command line to
reproduce the issue is especially helpful because options like
mrg_rxbuf=, which you mentioned, tell enabled features, which is
valuable information.
See https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1112044#69 for
the command line. The guest is started by libvirtd.
Please note: this is stable-7.2 series, it is *not* master (I picked
up this commit to 7.2.x). It'd be interesting to check if master is
affected too. Unfortunately I never tried migration, and now I only
have my notebook, so can only migrate between two qemu instances on
the same box - which is probably okay too.
Thanks,
/mjt
