Il 03/03/2014 13:32, Stefan Hajnoczi ha scritto:
If there is not enough memory to fork, then a synchronous approach to catching guest memory writes is needed. I'm not sure if a good mechanism for that exists but the simplest would be mprotect(2) and a signal handler (which will make the guest run very slowly).
I think we'll be adding such a mechanism, but for guest memory reads, for postcopy migration. Perhaps it could be reused for live snapshotting?
Paolo -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
