From: Jan Kiszka <jan.kiszka@web.de>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: Frank Berreth <frankber@google.com>, kvm@vger.kernel.org
Subject: Re: Save/Restore not working
Date: Tue, 19 Jul 2011 22:09:04 +0200 [thread overview]
Message-ID: <4E25E460.3010601@web.de> (raw)
In-Reply-To: <20110719172001.GB31673@amt.cnet>
[-- Attachment #1: Type: text/plain, Size: 1309 bytes --]
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 #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2011-07-19 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-18 22:46 Save/Restore not working Frank Berreth
2011-07-19 17:20 ` Marcelo Tosatti
2011-07-19 20:09 ` Jan Kiszka [this message]
2011-07-20 17:49 ` Frank Berreth
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4E25E460.3010601@web.de \
--to=jan.kiszka@web.de \
--cc=frankber@google.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox