All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Clemens Kolbitsch <ck@iseclab.org>
Cc: qemu-devel@nongnu.org, Juan Quintela <quintela@redhat.com>
Subject: Re: [Qemu-devel] Relative/Absolute timing snapshot problem
Date: Mon, 28 Mar 2011 18:32:17 +0200	[thread overview]
Message-ID: <4D90B811.2080800@redhat.com> (raw)
In-Reply-To: <201103280925.57531.ck@iseclab.org>

On 03/28/11 18:25, Clemens Kolbitsch wrote:
>> Hi Clemens,
>> > 
>> > Could you clarify what you are doing, when you say snapshot do you mean
>> > a savevm operation (ie. checkpoint) or a disk snapshot?
> I Jes,
> 
> sorry for not being clear: I use a savevm operation.
> 
> Following setup: I have a base file (qcow2 or qew format) and a snapshot file 
> (generated via 'qemu-img create -b <basefile> -f qcow2 <snapshotfile>') and 
> boot the snapshot file. Once the system (WinXP SP3 guest) has fully started, I 
> create a snapshot (savevm <foo>) and exit the emulator. Later, I resume the 
> snapshot by starting Qemu with the snapshotfile and say 'loadvm <foo>'.
> 
> Actually, I found that the times I gave in my last email were way 
> underestimated. The time difference is MUCH larger than 2-3 seconds per day. A 
> week-old snapshot can take minutes to load on a reasonably idle host machine.

Ok, then I am pretty much in the dark on this one - I don't know
anything about the checkpoint/restart feature and the impact on things
like the clock. I only worked on the live snapshot code (for disk
snapshots).

Hopefully someone else will have an idea.

Cheers,
Jes

  reply	other threads:[~2011-03-28 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-18 20:39 [Qemu-devel] Relative/Absolute timing snapshot problem Clemens Kolbitsch
2011-03-28 11:23 ` Jes Sorensen
2011-03-28 16:25   ` Clemens Kolbitsch
2011-03-28 16:32     ` Jes Sorensen [this message]
2011-03-28 17:49       ` Blue Swirl

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=4D90B811.2080800@redhat.com \
    --to=jes.sorensen@redhat.com \
    --cc=ck@iseclab.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.