On 2011-07-19 19:20, Marcelo Tosatti wrote: > On Mon, Jul 18, 2011 at 03:46:56PM -0700, Frank Berreth wrote: >> Hello, >> >> I am working on save/restore code (independent of Qemu or KVM tools) >> and am having trouble doing 'the right thing' with KVM it seems. I do >> have trouble finding good documentation on specifically save or >> restore (besides the description of IOCTLs) and there is a high chance >> I am doing something goofy here. >> >> The way I am save/restoring is simply saving the state I get through >> the different KVM IOCTLs and dumping it back on restore. The exception >> is restoring of the MSRs, where I first get the list, then get the >> MSRS and save/restore only those that were filled in by KVM. >> >> The restore order is the following: >> >> first restore memory, then >> KVM_SET_REGS >> KVM_SET_FPU >> KVM_SET_SREGS >> KVM_SET_MSRS >> KVM_SET_MPSTATE >> KVM_SET_LAPIC >> some user mode devices and then >> KVM_SET_PIT >> KVM_SET_IRQCHIP (3 times, for MASTER, SLAVE and IOAPIC) > > KVM_SET_VCPU_EVENTS is missing from this list. ...and some more. As Marcelo said, follow QEMU closely. It's the reference implementation and known to work pretty well. Just curious: What is the reason for another probably painful rewrite of QEMU? Jan
Attachment:
signature.asc
Description: OpenPGP digital signature
