From: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
To: Max Reitz <mreitz@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>, Cleber Rosa <crosa@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v4 1/1] tests/qemu-iotests: adding savevm/loadvm with postcopy flag test
Date: Tue, 5 Dec 2017 09:47:09 -0200 [thread overview]
Message-ID: <0a28bdcd-907f-fc9f-8b35-65a15d8bfae9@linux.vnet.ibm.com> (raw)
In-Reply-To: <8435b741-1bfc-fbe8-baa8-00bc98e60e0f@redhat.com>
On 12/04/2017 08:23 PM, Max Reitz wrote:
> On 2017-12-04 16:17, Daniel Henrique Barboza wrote:
>> This patch implements a test case for the scenario that was failing
>> prior to the patch "migration/ram.c: do not set 'postcopy_running' in
>> POSTCOPY_INCOMING_END", commit acab30b85d.
>>
>> This new test file 201 was derived from the test file 181 authored
>> by Kevin Wolf.
>>
>> CC: Kevin Wolf <kwolf@redhat.com>
>> CC: Max Reitz <mreitz@redhat.com>
>> CC: Cleber Rosa <crosa@redhat.com>
>> Signed-off-by: Daniel Henrique Barboza <danielhb@linux.vnet.ibm.com>
>> ---
>> tests/qemu-iotests/201 | 116 +++++++++++++++++++++++++++++++++++++++++++++
>> tests/qemu-iotests/201.out | 23 +++++++++
>> tests/qemu-iotests/group | 1 +
>> 3 files changed, 140 insertions(+)
>> create mode 100755 tests/qemu-iotests/201
>> create mode 100644 tests/qemu-iotests/201.out
>>
>> diff --git a/tests/qemu-iotests/201 b/tests/qemu-iotests/201
>> new file mode 100755
>> index 0000000000..9b6e23bbfc
>> --- /dev/null
>> +++ b/tests/qemu-iotests/201
>> @@ -0,0 +1,116 @@
>> +#!/bin/bash
>> +#
>> +# Test savevm and loadvm after live migration with postcopy flag
>> +#
>> +# Copyright (C) 2017, IBM Corporation.
>> +#
>> +# This file is derived from tests/qemu-iotests/181 by Kevin Wolf
>> +#
>> +# This program is free software; you can redistribute it and/or modify
>> +# it under the terms of the GNU General Public License as published by
>> +# the Free Software Foundation; either version 2 of the License, or
>> +# (at your option) any later version.
>> +#
>> +# This program is distributed in the hope that it will be useful,
>> +# but WITHOUT ANY WARRANTY; without even the implied warranty of
>> +# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
>> +# GNU General Public License for more details.
>> +#
>> +# You should have received a copy of the GNU General Public License
>> +# along with this program. If not, see <http://www.gnu.org/licenses/>.
>> +
>> +seq=`basename $0`
>> +echo "QA output created by $seq"
>> +
>> +status=1 # failure is the default!
>> +
>> +MIG_SOCKET="${TEST_DIR}/migrate"
>> +
>> +# get standard environment, filters and checks
>> +. ./common.rc
>> +. ./common.filter
>> +. ./common.qemu
>> +
>> +_cleanup()
>> +{
>> + rm -f "${MIG_SOCKET}"
>> + _cleanup_test_img
>> + _cleanup_qemu
>> +}
>> +trap "_cleanup; exit \$status" 0 1 2 3 15
>> +
>> +_supported_fmt qcow2
>> +_supported_proto generic
>> +_supported_os Linux
> Sorry, I had to unqueue the patch again, because I only just saw there's
> something like
>
>> # Internal snapshots are (currently) impossible with refcount_bits=1
>> _unsupported_imgopts 'refcount_bits=1[^0-9]'
> missing here (taken from 080).
>
> (Without that, the test fails with
> $ ./check -T -qcow2 -o refcount_bits=1 201
> )
>
> I could have added it myself, but that seemed a bit too much of a change
> to me...
No problem, I'll resend with that extra instruction.
I have a question though: is there a way to run a qemu-iotest with all the
parameters combinations (image type, image protocol ...) that the test must
support?
Thanks,
Daniel
>
> Max
>
>> +
>> +size=64M
>> +_make_test_img $size
next prev parent reply other threads:[~2017-12-05 11:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 15:17 [Qemu-devel] [PATCH v4 0/1] savevm/loadvm with postcopy flag qemu-iotest Daniel Henrique Barboza
2017-12-04 15:17 ` [Qemu-devel] [PATCH v4 1/1] tests/qemu-iotests: adding savevm/loadvm with postcopy flag test Daniel Henrique Barboza
2017-12-04 18:18 ` Max Reitz
2017-12-04 22:23 ` Max Reitz
2017-12-05 11:47 ` Daniel Henrique Barboza [this message]
2017-12-05 18:06 ` Dr. David Alan Gilbert
2017-12-05 19:31 ` Daniel Henrique Barboza
2017-12-05 19:43 ` Dr. David Alan Gilbert
2017-12-06 8:27 ` Kevin Wolf
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=0a28bdcd-907f-fc9f-8b35-65a15d8bfae9@linux.vnet.ibm.com \
--to=danielhb@linux.vnet.ibm.com \
--cc=crosa@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@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).