From: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
To: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>,
qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Max Reitz <mreitz@redhat.com>,
dgilbert@redhat.com, qemu-block@nongnu.org, quintela@redhat.com
Subject: Re: [PATCH v2 14/22] qemu-iotests/199: better catch postcopy time
Date: Wed, 19 Feb 2020 16:16:28 +0300 [thread overview]
Message-ID: <ef51a28c-c9d8-7dc3-e203-883f9f48fbad@virtuozzo.com> (raw)
In-Reply-To: <20200217150246.29180-15-vsementsov@virtuozzo.com>
On 17/02/2020 18:02, Vladimir Sementsov-Ogievskiy wrote:
> The test aims to test _postcopy_ migration, and wants to do some write
> operations during postcopy time.
>
> Test considers migrate status=complete event on source as start of
> postcopy. This is completely wrong, completion is completion of the
> whole migration process. Let's instead consider destination start as
> start of postcopy, and use RESUME event for it.
>
> Next, as migration finish, let's use migration status=complete event on
> target, as such method is closer to what libvirt or another user will
> do, than tracking number of dirty-bitmaps.
>
> Finally, add a possibility to dump events for debug. And if
> set debug to True, we see, that actual postcopy period is very small
> relatively to the whole test duration time (~0.2 seconds to >40 seconds
> for me). This means, that test is very inefficient in what it supposed
> to do. Let's improve it in following commits.
>
> Signed-off-by: Vladimir Sementsov-Ogievskiy <vsementsov@virtuozzo.com>
> ---
> tests/qemu-iotests/199 | 72 +++++++++++++++++++++++++++++++++---------
> 1 file changed, 57 insertions(+), 15 deletions(-)
>
> diff --git a/tests/qemu-iotests/199 b/tests/qemu-iotests/199
> index dda918450a..6599fc6fb4 100755
> --- a/tests/qemu-iotests/199
> +++ b/tests/qemu-iotests/199
> @@ -20,17 +20,43 @@
>
> import os
> import iotests
> -import time
> from iotests import qemu_img
>
> +debug = False
> +
> disk_a = os.path.join(iotests.test_dir, 'disk_a')
> disk_b = os.path.join(iotests.test_dir, 'disk_b')
> size = '256G'
> fifo = os.path.join(iotests.test_dir, 'mig_fifo')
>
>
> +def event_seconds(event):
> + return event['timestamp']['seconds'] + \
> + event['timestamp']['microseconds'] / 1000000.0
> +
> +
> +def event_dist(e1, e2):
> + return event_seconds(e2) - event_seconds(e1)
> +
> +
> class TestDirtyBitmapPostcopyMigration(iotests.QMPTestCase):
> def tearDown(self):
It's common to put the definition of setUp() ahead
> + if debug:
> + self.vm_a_events += self.vm_a.get_qmp_events()
> + self.vm_b_events += self.vm_b.get_qmp_events()
> + for e in self.vm_a_events:
> + e['vm'] = 'SRC'
> + for e in self.vm_b_events:
> + e['vm'] = 'DST'
> + events = (self.vm_a_events + self.vm_b_events)
> + events = [(e['timestamp']['seconds'],
> + e['timestamp']['microseconds'],
> + e['vm'],
> + e['event'],
> + e.get('data', '')) for e in events]
> + for e in sorted(events):
> + print('{}.{:06} {} {} {}'.format(*e))
> +
> self.vm_a.shutdown()
> self.vm_b.shutdown()
> os.remove(disk_a)
> @@ -47,6 +73,10 @@ class TestDirtyBitmapPostcopyMigration(iotests.QMPTestCase):
> self.vm_a.launch()
> self.vm_b.launch()
>
> + # collect received events for debug
> + self.vm_a_events = []
> + self.vm_b_events = []
> +
> def test_postcopy(self):
> write_size = 0x40000000
> granularity = 512
> @@ -77,15 +107,13 @@ class TestDirtyBitmapPostcopyMigration(iotests.QMPTestCase):
> self.vm_a.hmp_qemu_io('drive0', 'write %d %d' % (s, chunk))
> s += 0x10000
>
> - bitmaps_cap = {'capability': 'dirty-bitmaps', 'state': True}
> - events_cap = {'capability': 'events', 'state': True}
> + caps = [{'capability': 'dirty-bitmaps', 'state': True},
The name "capabilities" would be an appropriate identifier.
> + {'capability': 'events', 'state': True}]
>
> - result = self.vm_a.qmp('migrate-set-capabilities',
> - capabilities=[bitmaps_cap, events_cap])
> + result = self.vm_a.qmp('migrate-set-capabilities', capabilities=caps)
> self.assert_qmp(result, 'return', {})
>
> - result = self.vm_b.qmp('migrate-set-capabilities',
> - capabilities=[bitmaps_cap])
> + result = self.vm_b.qmp('migrate-set-capabilities', capabilities=caps)
> self.assert_qmp(result, 'return', {})
>
> result = self.vm_a.qmp('migrate', uri='exec:cat>' + fifo)
> @@ -94,24 +122,38 @@ class TestDirtyBitmapPostcopyMigration(iotests.QMPTestCase):
> result = self.vm_a.qmp('migrate-start-postcopy')
> self.assert_qmp(result, 'return', {})
>
> - while True:
> - event = self.vm_a.event_wait('MIGRATION')
> - if event['data']['status'] == 'completed':
> - break
> + e_resume = self.vm_b.event_wait('RESUME')
"event_resume" gives a faster understanding
> + self.vm_b_events.append(e_resume)
>
> s = 0x8000
> while s < write_size:
> self.vm_b.hmp_qemu_io('drive0', 'write %d %d' % (s, chunk))
> s += 0x10000
>
> + match = {'data': {'status': 'completed'}}
> + e_complete = self.vm_b.event_wait('MIGRATION', match=match)
"event_complete" also
> + self.vm_b_events.append(e_complete)
> +
> + # take queued event, should already been happened
> + e_stop = self.vm_a.event_wait('STOP')
"event_stop"
> + self.vm_a_events.append(e_stop)
> +
> + downtime = event_dist(e_stop, e_resume)
> + postcopy_time = event_dist(e_resume, e_complete)
> +
> + # TODO: assert downtime * 10 < postcopy_time
I got the results below in debug mode:
downtime: 6.194924831390381
postcopy_time: 0.1592559814453125
1582102669.764919 SRC MIGRATION {'status': 'setup'}
1582102669.766179 SRC MIGRATION_PASS {'pass': 1}
1582102669.766234 SRC MIGRATION {'status': 'active'}
1582102669.768058 DST MIGRATION {'status': 'active'}
1582102669.801422 SRC MIGRATION {'status': 'postcopy-active'}
1582102669.801510 SRC STOP
1582102675.990041 DST MIGRATION {'status': 'postcopy-active'}
1582102675.996435 DST RESUME
1582102676.111313 SRC MIGRATION {'status': 'completed'}
1582102676.155691 DST MIGRATION {'status': 'completed'}
> + if debug:
with no usage in the following patches, you can put the whole block of
relative code above under the "if debug: section
> + print('downtime:', downtime)
> + print('postcopy_time:', postcopy_time)
> +
> + # Assert that bitmap migration is finished (check that successor bitmap
> + # is removed)
> result = self.vm_b.qmp('query-block')
> - while len(result['return'][0]['dirty-bitmaps']) > 1:
> - time.sleep(2)
> - result = self.vm_b.qmp('query-block')
> + assert len(result['return'][0]['dirty-bitmaps']) == 1
>
> + # Check content of migrated (and updated by new writes) bitmap
> result = self.vm_b.qmp('x-debug-block-dirty-bitmap-sha256',
> node='drive0', name='bitmap')
> -
> self.assert_qmp(result, 'return/sha256', sha256)
>
>
>
Reviewed-by: Andrey Shinkevich <andrey.shinkevich@virtuozzo.com>
--
With the best regards,
Andrey Shinkevich
next prev parent reply other threads:[~2020-02-19 13:19 UTC|newest]
Thread overview: 80+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 15:02 [PATCH v2 00/22] Fix error handling during bitmap postcopy Vladimir Sementsov-Ogievskiy
2020-02-17 15:02 ` [PATCH v2 01/22] migration/block-dirty-bitmap: fix dirty_bitmap_mig_before_vm_start Vladimir Sementsov-Ogievskiy
2020-02-18 9:44 ` Andrey Shinkevich
2020-02-17 15:02 ` [PATCH v2 02/22] migration/block-dirty-bitmap: rename state structure types Vladimir Sementsov-Ogievskiy
2020-07-23 20:50 ` Eric Blake
2020-02-17 15:02 ` [PATCH v2 03/22] migration/block-dirty-bitmap: rename dirty_bitmap_mig_cleanup Vladimir Sementsov-Ogievskiy
2020-02-18 11:00 ` Andrey Shinkevich
2020-02-19 14:20 ` Vladimir Sementsov-Ogievskiy
2020-07-23 20:54 ` Eric Blake
2020-02-17 15:02 ` [PATCH v2 04/22] migration/block-dirty-bitmap: move mutex init to dirty_bitmap_mig_init Vladimir Sementsov-Ogievskiy
2020-02-18 11:28 ` Andrey Shinkevich
2020-02-17 15:02 ` [PATCH v2 05/22] migration/block-dirty-bitmap: refactor state global variables Vladimir Sementsov-Ogievskiy
2020-02-18 13:05 ` Andrey Shinkevich
2020-02-19 15:29 ` Vladimir Sementsov-Ogievskiy
2020-02-17 15:02 ` [PATCH v2 06/22] migration/block-dirty-bitmap: rename finish_lock to just lock Vladimir Sementsov-Ogievskiy
2020-02-18 13:20 ` Andrey Shinkevich
2020-02-17 15:02 ` [PATCH v2 07/22] migration/block-dirty-bitmap: simplify dirty_bitmap_load_complete Vladimir Sementsov-Ogievskiy
2020-02-18 14:26 ` Andrey Shinkevich
2020-02-19 15:30 ` Vladimir Sementsov-Ogievskiy
2020-02-19 16:14 ` Vladimir Sementsov-Ogievskiy
2020-02-17 15:02 ` [PATCH v2 08/22] migration/block-dirty-bitmap: keep bitmap state for all bitmaps Vladimir Sementsov-Ogievskiy
2020-02-18 17:07 ` Andrey Shinkevich
2020-07-23 21:30 ` Eric Blake
2020-07-24 5:18 ` Vladimir Sementsov-Ogievskiy
2020-02-17 15:02 ` [PATCH v2 09/22] migration/block-dirty-bitmap: relax error handling in incoming part Vladimir Sementsov-Ogievskiy
2020-02-18 18:54 ` Andrey Shinkevich
2020-02-19 15:34 ` Vladimir Sementsov-Ogievskiy
2020-07-24 7:23 ` Vladimir Sementsov-Ogievskiy
2020-02-17 15:02 ` [PATCH v2 10/22] migration/block-dirty-bitmap: cancel migration on shutdown Vladimir Sementsov-Ogievskiy
2020-02-18 19:11 ` Andrey Shinkevich
2020-07-23 21:04 ` Eric Blake
2020-02-17 15:02 ` [PATCH v2 11/22] migration/savevm: don't worry if bitmap migration postcopy failed Vladimir Sementsov-Ogievskiy
2020-02-17 16:57 ` Dr. David Alan Gilbert
2020-02-18 19:44 ` Andrey Shinkevich
2020-02-17 15:02 ` [PATCH v2 12/22] qemu-iotests/199: fix style Vladimir Sementsov-Ogievskiy
2020-02-19 7:04 ` Andrey Shinkevich
2020-07-23 22:03 ` Eric Blake
2020-07-24 6:32 ` Vladimir Sementsov-Ogievskiy
2020-02-17 15:02 ` [PATCH v2 13/22] qemu-iotests/199: drop extra constraints Vladimir Sementsov-Ogievskiy
2020-02-19 8:02 ` Andrey Shinkevich
2020-02-17 15:02 ` [PATCH v2 14/22] qemu-iotests/199: better catch postcopy time Vladimir Sementsov-Ogievskiy
2020-02-19 13:16 ` Andrey Shinkevich [this message]
2020-02-19 15:44 ` Vladimir Sementsov-Ogievskiy
2020-07-24 6:50 ` Vladimir Sementsov-Ogievskiy
2020-02-17 15:02 ` [PATCH v2 15/22] qemu-iotests/199: improve performance: set bitmap by discard Vladimir Sementsov-Ogievskiy
2020-02-19 14:17 ` Andrey Shinkevich
2020-02-17 15:02 ` [PATCH v2 16/22] qemu-iotests/199: change discard patterns Vladimir Sementsov-Ogievskiy
2020-02-19 14:33 ` Andrey Shinkevich
2020-02-19 14:44 ` Andrey Shinkevich
2020-02-19 15:46 ` Vladimir Sementsov-Ogievskiy
2020-07-24 0:23 ` Eric Blake
2020-02-17 15:02 ` [PATCH v2 17/22] qemu-iotests/199: increase postcopy period Vladimir Sementsov-Ogievskiy
2020-02-19 14:56 ` Andrey Shinkevich
2020-07-24 0:14 ` Eric Blake
2020-02-17 15:02 ` [PATCH v2 18/22] python/qemu/machine: add kill() method Vladimir Sementsov-Ogievskiy
2020-02-19 17:00 ` Andrey Shinkevich
2020-05-29 10:09 ` Philippe Mathieu-Daudé
2020-02-17 15:02 ` [PATCH v2 19/22] qemu-iotests/199: prepare for new test-cases addition Vladimir Sementsov-Ogievskiy
2020-02-19 16:10 ` Andrey Shinkevich
2020-02-17 15:02 ` [PATCH v2 20/22] qemu-iotests/199: check persistent bitmaps Vladimir Sementsov-Ogievskiy
2020-02-19 16:28 ` Andrey Shinkevich
2020-02-17 15:02 ` [PATCH v2 21/22] qemu-iotests/199: add early shutdown case to bitmaps postcopy Vladimir Sementsov-Ogievskiy
2020-02-19 16:48 ` Andrey Shinkevich
2020-02-19 16:50 ` Andrey Shinkevich
2020-02-17 15:02 ` [PATCH v2 22/22] qemu-iotests/199: add source-killed " Vladimir Sementsov-Ogievskiy
2020-02-19 17:15 ` Andrey Shinkevich
2020-07-24 7:50 ` Vladimir Sementsov-Ogievskiy
2020-02-17 19:31 ` [PATCH v2 00/22] Fix error handling during bitmap postcopy no-reply
2020-02-18 20:02 ` Andrey Shinkevich
2020-02-18 20:57 ` Eric Blake
2020-02-19 13:25 ` Andrey Shinkevich
2020-02-19 13:36 ` Eric Blake
2020-02-19 13:52 ` Andrey Shinkevich
2020-02-19 14:58 ` Eric Blake
2020-02-19 17:22 ` Andrey Shinkevich
2020-02-19 14:00 ` Eric Blake
2020-04-02 7:42 ` Vladimir Sementsov-Ogievskiy
2020-05-29 11:58 ` Eric Blake
2020-05-29 12:16 ` Vladimir Sementsov-Ogievskiy
2020-07-23 20:39 ` Eric Blake
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=ef51a28c-c9d8-7dc3-e203-883f9f48fbad@virtuozzo.com \
--to=andrey.shinkevich@virtuozzo.com \
--cc=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=vsementsov@virtuozzo.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 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).