From: Clemens Kolbitsch <ck@iseclab.org>
To: Jes Sorensen <Jes.Sorensen@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Relative/Absolute timing snapshot problem
Date: Mon, 28 Mar 2011 09:25:57 -0700 [thread overview]
Message-ID: <201103280925.57531.ck@iseclab.org> (raw)
In-Reply-To: <4D906F99.9080808@redhat.com>
> On 03/18/11 21:39, Clemens Kolbitsch wrote:
> > Hi list,
> >
> > strange situation: When I create a snapshot using Qemu 0.14.0 stable,
> > everything works smoothly and resuming the CPU takes about 1-2 seconds.
> > If I don't use the snapshot file for some time, the time it takes to
> > resume grows by 2-3 seconds per day. At the moment, I'm looking at a
> > snapshot file from last week and it takes nearly 30 seconds to load.
> >
> > Funny thing about it: if I turn my system time back to the date when the
> > snapshot was created (or before that), resuming CPU works within the
> > expected 1-2 seconds. I have _very briefly_ looked into it and it seems
> > like Qemu spends an aweful long amount of time catching up with timer
> > execution -- is it possible that these are stored using absolute time
> > instead of relative timing?
> >
> > I am using qcow2 file format, because I absolutely rely on CPU-snapshots
> > and support for base-files. I have read here and there that it is more
> > or less broken (or at least very slow), but with the correct
> > cache-options it works for me (except for this bug, of course).
> >
> > Has anyone encountered this or should I start looking into it (although I
> > have some experience with the core source, I'm not very experienced with
> > the snapshotting code).
>
> 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?
>
> Cheers,
> Jes
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.
--Clemens
next prev parent reply other threads:[~2011-03-28 16:27 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 [this message]
2011-03-28 16:32 ` Jes Sorensen
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=201103280925.57531.ck@iseclab.org \
--to=ck@iseclab.org \
--cc=Jes.Sorensen@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.