From: John Snow <jsnow@redhat.com>
To: "Denis V. Lunev" <den-lists@parallels.com>,
qemu-devel <qemu-devel@nongnu.org>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
Subject: Re: [Qemu-devel] Debugging Migration
Date: Tue, 6 Oct 2015 19:02:51 -0400 [thread overview]
Message-ID: <5614531B.5080107@redhat.com> (raw)
In-Reply-To: <56144DDD.9040304@parallels.com>
On 10/06/2015 06:40 PM, Denis V. Lunev wrote:
> On 10/06/2015 09:46 PM, John Snow wrote:
>> Is there a convenient way of "pausing" or stalling a live migration to
>> allow methodical testing of race conditions?
>>
>> I'd like to instrument something along the lines of:
>>
>> (1) Live migration begins.
>> (2) migration is artificially halted or paused, but QEMU is allowed to
>> run.
>> (3) Some additional qtest/QMP commands are received and processed.
>> (4) migration is allowed to resume.
>>
>> Does anyone have perhaps even test patches to instrument this sort of
>> thing, or is it up to detective john to add it if he wants it?
>>
>> Thanks,
>> --js
>>
> we have performed some experiments with migration "test mode".
> The idea was to estimate the time to migrate and estimate
> expected downtime for distributed resource management.
> In this mode the migration was not performed but all stuff around
> like dirty bitmap was touched.
>
> There are several patches for this in my queue but they are very
> hackish.
>
> Will it help you?
>
> Den
It certainly won't hurt me to look at them if you'll share :)
--js
next prev parent reply other threads:[~2015-10-06 23:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 18:46 [Qemu-devel] Debugging Migration John Snow
2015-10-06 19:00 ` Dr. David Alan Gilbert
2015-10-06 22:40 ` Denis V. Lunev
2015-10-06 23:02 ` John Snow [this message]
2015-10-07 6:20 ` [Qemu-devel] [RFC 0/8] QEMUFile-way to gather VM's memory statistics Denis V. Lunev
2015-10-07 6:20 ` [Qemu-devel] [PATCH 1/8] migration: fix expected_downtime Denis V. Lunev
2015-10-07 6:20 ` [Qemu-devel] [PATCH 2/8] qemu-file: new hook in qemu-file Denis V. Lunev
2015-10-07 6:20 ` [Qemu-devel] [PATCH 3/8] migration: add new capability test-only Denis V. Lunev
2015-10-07 15:05 ` Eric Blake
2015-10-08 14:54 ` Denis V. Lunev
2015-10-09 15:19 ` Dr. David Alan Gilbert
2015-10-07 6:20 ` [Qemu-devel] [PATCH 4/8] migration: add function for reseting migration bitmap Denis V. Lunev
2015-10-07 6:20 ` [Qemu-devel] [PATCH 5/8] migration: add draft of new transport Denis V. Lunev
2015-10-07 6:20 ` [Qemu-devel] [PATCH 6/8] migration: implementation of hook_ram_sync Denis V. Lunev
2015-10-07 9:44 ` Paolo Bonzini
2015-10-08 16:51 ` Denis V. Lunev
2015-10-07 9:44 ` Paolo Bonzini
2015-10-08 16:39 ` Denis V. Lunev
2015-10-07 14:03 ` Dr. David Alan Gilbert
2015-10-07 6:20 ` [Qemu-devel] [PATCH 7/8] migration: new migration test mode Denis V. Lunev
2015-10-07 13:56 ` Dr. David Alan Gilbert
2015-10-07 15:08 ` Eric Blake
2015-10-08 17:01 ` Denis V. Lunev
2015-10-08 17:05 ` Dr. David Alan Gilbert
2015-10-08 17:05 ` Denis V. Lunev
2015-10-08 18:57 ` Dr. David Alan Gilbert
2015-10-07 6:20 ` [Qemu-devel] [PATCH 8/8] migration: add output of gathered statistics Denis V. Lunev
2015-10-07 14:19 ` [Qemu-devel] [RFC 0/8] QEMUFile-way to gather VM's memory statistics Dr. David Alan Gilbert
2015-10-07 6:38 ` [Qemu-devel] Debugging Migration Denis V. Lunev
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=5614531B.5080107@redhat.com \
--to=jsnow@redhat.com \
--cc=den-lists@parallels.com \
--cc=dgilbert@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 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).