From: "Blue Swirl" <blauwirbel@gmail.com>
To: qemu-devel@nongnu.org
Cc: Tim Leek <tleek@ll.mit.edu>
Subject: Re: [Qemu-devel] qemu replay?
Date: Tue, 22 Jul 2008 19:32:54 +0300 [thread overview]
Message-ID: <f43fc5580807220932g2554ab0cye915584925405155@mail.gmail.com> (raw)
In-Reply-To: <4BF509F8-DB9B-48F4-B548-801C3F1F6189@ll.mit.edu>
On 7/21/08, Tim Leek <tleek@ll.mit.edu> wrote:
>
> A quick question for the gurus. Please cc my email address with replies?
>
> Is there anything out there that implements record/replay for Qemu? I'm
> sure all of you are aware of this paper. Others have done similar things.
Interesting paper. There are patches to capture network traffic to a
file and some I/O can be captured by recompiling with debug code
enabled. Some of this can be replayed (just keyboard and mouse) using
the monitor interface, but not for other I/O.
Support of record/replay should not be too difficult to add. I haven't
looked, but the live migration stuff in Xen could be a good starting
point.
prev parent reply other threads:[~2008-07-22 16:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 18:02 [Qemu-devel] qemu replay? Tim Leek
2008-07-22 16:32 ` Blue Swirl [this message]
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=f43fc5580807220932g2554ab0cye915584925405155@mail.gmail.com \
--to=blauwirbel@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=tleek@ll.mit.edu \
/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).