Hi, >> IMO spice-server must not call interface_client_set_capabilities >> when the vm is not running. After all we notify spice-server about >> the vm stop/start events for a reason ... > > OK, I agree that should be fixed, we can queue this until the vm > starts running in spice-server. But having an assert on notify in > qemu is also wrong - and the only way to fix it like you pointed out > without dropping the event is to queue it as well. > > So which will it be, queue in spice or in qemu? qemu seems a simpler > place to catch everything.
When queuing in qemu you are facing the migration issue again in a different way: Just this time it isn't guest state, but a qxl register. Not guest visible, but still state which must be migrated over ... cheers, Gerd
