On 17.12.14 11:47, Mark Cave-Ayland wrote: > On 17/12/14 10:23, Alexander Graf wrote: > >>> After the restart the keyboard is frozen and unresponsive. Some >>> preliminary poking with gdb before and after seems to indicate that the >>> cuda_receive_packet() functions aren't being called after the restart >>> indicating that likely some state is missing from the savevm image and >>> not being restored correctly. Anyone have any ideas as to what might be >>> going wrong? >> >> I don't think anyone has test the migration code on non-papr ppc for >> quite a while. In fact, I'm surprised it's only the keyboard not working :). >> >> You're more than invited to send patches to fix it! :) > > How did I know that would be the response ;) I don't suppose anyone has > a vague memory of the timeframe/QEMU version when a savevm/loadvm was > last working for -M g3beige as a starting point?!
Phew - 0.7.0 maybe? If you say that only CUDA is broken, I don't think it'd be too hard to fix :). Check that there are VMSTATEs for everything and maybe retrigger interrupts after migration. Alex
