If something went wrong... well, on my AMD machine this usually means
the fw is really unhappy and recovery is hardly possible and the machine
needs reboot. Probably stopping the VM would make more sense for now (or
stop the device so the user could save work from the VM, dunno).
My current plan (in next version) is to squash the mixture handling in
previous patch to always run the code for "unexpected mix", and return
error without rollback if it fails in kvm_convert_memory(), which will
cause QEMU to quit. I think it can meet what you want.
As for the rollback handling, maybe keep it as an attached patch for
future reference or just remove it.
probably best to remove it for now. The patch is in the mailing list
archives for future reference :)
--
Cheers,
David / dhildenb
