From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Cc: "He, Junyan" <junyan.he@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Juan Quintela <quintela@redhat.com>, John Snow <jsnow@redhat.com>
Subject: Re: [Qemu-devel] Some question about savem/qcow2 incremental snapshot
Date: Wed, 10 Jan 2018 20:17:11 +0000 [thread overview]
Message-ID: <CAJSP0QU8YGzLo0mVL-VCWzebk1iE-ZV1XQPkOJ7pq69Ch6GtnA@mail.gmail.com> (raw)
In-Reply-To: <20180110201519.GF2451@work-vm>
On Wed, Jan 10, 2018 at 8:15 PM, Dr. David Alan Gilbert
<dgilbert@redhat.com> wrote:
> * Stefan Hajnoczi (stefanha@gmail.com) wrote:
>> On Tue, Jan 9, 2018 at 7:55 PM, Dr. David Alan Gilbert
>> <dgilbert@redhat.com> wrote:
>> >> Certain guest operations like rebooting or zeroing memory will defeat
>> >> the incremental guest RAM snapshot feature. It's worth thinking about
>> >> these cases to make sure this feature would be worth it in real use
>> >> cases.
>> >
>> > But those probably wouldn't upset an NVDimm?
>>
>> If the guest dirties all RAM then the incremental snapshot feature
>> degrades to a full snapshot. I'm asking if there are common
>> operations where that happens.
>>
>> I seem to remember Windows guests zero all pages on cold boot. Maybe
>> that's not the case anymore.
>>
>> Worth checking before embarking on this feature because it could be a
>> waste of effort if it turns out real-world guests dirty all memory in
>> common cases.
>
> Right, but I'm hoping that there's some magic somewhere where an NVDimm doesn't
> get zero'd because of a cold boot since that would seem to make it
> volatile.
This feature isn't specific to NVDIMM though. It would be equally
useful for regular RAM.
Stefan
next prev parent reply other threads:[~2018-01-10 20:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-25 7:54 [Qemu-devel] Some question about savem/qcow2 incremental snapshot He, Junyan
2018-01-09 15:35 ` Stefan Hajnoczi
2018-01-09 19:55 ` Dr. David Alan Gilbert
2018-01-10 19:16 ` Stefan Hajnoczi
2018-01-10 20:15 ` Dr. David Alan Gilbert
2018-01-10 20:17 ` Stefan Hajnoczi [this message]
2018-01-16 7:14 ` He Junyan
-- strict thread matches above, loose matches on Subject: below --
2017-12-25 7:33 He Junyan
2018-05-08 14:41 ` Eric Blake
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=CAJSP0QU8YGzLo0mVL-VCWzebk1iE-ZV1XQPkOJ7pq69Ch6GtnA@mail.gmail.com \
--to=stefanha@gmail.com \
--cc=dgilbert@redhat.com \
--cc=jsnow@redhat.com \
--cc=junyan.he@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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;
as well as URLs for NNTP newsgroup(s).