From: Amit Shah <amit.shah@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: pbonzini@redhat.com, quintela@redhat.com, qemu-devel@nongnu.org,
afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH v3 0/5] Migration Deciphering aid
Date: Tue, 20 Jan 2015 16:01:12 +0530 [thread overview]
Message-ID: <20150120103112.GI31174@grmbl.mre> (raw)
In-Reply-To: <1419604968-87437-1-git-send-email-agraf@suse.de>
On (Fri) 26 Dec 2014 [15:42:43], Alexander Graf wrote:
> Migration is a black hole to most people. One of the biggest reasons for
> this is that its protocol is a secret, undocumented sauce of code rolling
> around random parts of the QEMU code base.
>
> But what if we simply exposed the description of how the format looks like
> alongside the actual migration stream? This is what this patch set does.
>
> It adds a new section that comes after the end of stream marker (so that it
> doesn't slow down migration) that contains a JSON description of the device
> state description.
>
> Along with this patch set also comes a python script that can read said JSON
> from a migration dump and decipher the device state and ram contents of the
> migration dump using it.
>
> With this, you can now fully examine all glorious details that go over the
> wire when virtual machine state gets dumped, such as during live migration.
>
> We discussed the approach taken here during KVM Forum 2013. Originally, my idea
> was to include a special device that contains the JSON data which can be enabled
> on demand. Anthony suggested however to just always include the description data
> after the end marker which I think is a great idea.
>
> Example decoded migration: http://csgraf.de/mig/mig.txt
> Example migration description: http://csgraf.de/mig/mig.desc.txt
> Presentation: https://www.youtube.com/watch?v=iq1x40Qsrew
> Slides: https://www.dropbox.com/s/otp2pk2n3g087zp/Live%20Migration.pdf
Nice to finally see this!
I guess you have a v4 coming soon?
Amit
next prev parent reply other threads:[~2015-01-20 10:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-26 14:42 [Qemu-devel] [PATCH v3 0/5] Migration Deciphering aid Alexander Graf
2014-12-26 14:42 ` [Qemu-devel] [PATCH v3 1/5] QJSON: Add JSON writer Alexander Graf
2015-01-06 15:41 ` Eric Blake
2015-01-06 21:39 ` Alexander Graf
2014-12-26 14:42 ` [Qemu-devel] [PATCH v3 2/5] " Alexander Graf
2015-01-06 15:44 ` Eric Blake
2015-01-06 21:16 ` Alexander Graf
2014-12-26 14:42 ` [Qemu-devel] [PATCH v3 3/5] qemu-file: Add fast ftell code path Alexander Graf
2015-01-06 15:46 ` Eric Blake
2014-12-26 14:42 ` [Qemu-devel] [PATCH v3 4/5] migration: Append JSON description of migration stream Alexander Graf
2015-01-06 15:56 ` Eric Blake
2015-01-06 21:25 ` Alexander Graf
2015-01-20 10:30 ` Amit Shah
2014-12-26 14:42 ` [Qemu-devel] [PATCH v3 5/5] Add migration stream analyzation script Alexander Graf
2015-01-06 16:05 ` Eric Blake
2015-01-06 21:29 ` Alexander Graf
2015-01-20 10:31 ` Amit Shah [this message]
2015-01-20 10:54 ` [Qemu-devel] [PATCH v3 0/5] Migration Deciphering aid Alexander Graf
2015-01-21 6:05 ` Amit Shah
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=20150120103112.GI31174@grmbl.mre \
--to=amit.shah@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=pbonzini@redhat.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 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.