Hi,
We don't have a hard policy about not merging devices that don't
support migration.
Since migration must be supported forever, I'd rather see a device
get some solid testing before it starts doing live migration. That
said, we should probably do this consciously by explicitly marking
the device non-migrateable.
Can't we just implicitly fail migration whenever there's a device in
the tree that doesn't have VMSTATE?
There are cases where the device doesn't need to save state, so that
alone doesn't cut it.
cheers,
Gerd
