--On 12 August 2013 11:59:03 +0200 Stefan Hajnoczi <stefanha@xxxxxxxxx> wrote:
The idea that was discussed on qemu-devel@xxxxxxxxxx uses fork(2) to capture the state of guest RAM and then send it back to the parent process. The guest is only paused for a brief instant during fork(2) and can continue to run afterwards.
How would you capture the state of emulated hardware which might not be in the guest RAM? -- Alex Bligh -- 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
