On 21.02.2013, at 03:41, David Gibson wrote:
> At the moment, there is a significant amount of state which both qemu
> and KVM track, which is not synchronized between the two. In a KVM
> setup, qemu never updates that information, so we mostly get away with
> it, but we'll need this data in qem
At the moment, there is a significant amount of state which both qemu
and KVM track, which is not synchronized between the two. In a KVM
setup, qemu never updates that information, so we mostly get away with
it, but we'll need this data in qemu to implement savevm and
migration. This series impro
