mbox series

[v5,0/1] savevm/loadvm with postcopy flag qemu-iotest

Message ID 20171205133508.15061-1-danielhb@linux.vnet.ibm.com
Headers show
Series savevm/loadvm with postcopy flag qemu-iotest | expand

Message

Daniel Henrique Barboza Dec. 5, 2017, 1:35 p.m. UTC
Changes from v4:
- added a 'refcount_bits=1' constraint for internal snapshots

Changes from v3:
- rebased with master - file name changed from 198 to 201
- removed Creator/owner information (it can be retrieved with git)
- added a migration successful check before executing savevm
- removed a trailing double comma in the snapshot name

Daniel Henrique Barboza (1):
  tests/qemu-iotests: adding savevm/loadvm with postcopy flag test

 tests/qemu-iotests/201     | 120 +++++++++++++++++++++++++++++++++++++++++++++
 tests/qemu-iotests/201.out |  23 +++++++++
 tests/qemu-iotests/group   |   1 +
 3 files changed, 144 insertions(+)
 create mode 100755 tests/qemu-iotests/201
 create mode 100644 tests/qemu-iotests/201.out

Comments

Daniel Henrique Barboza Jan. 2, 2018, 1:04 p.m. UTC | #1
Hi there,

I saw that new iotests were added upstream and decided to re-sent this 
patch, but
then I noticed that the files being created by this patch (201 and 
201.out) weren't
created upstream - we have 200 and then 202 and 203.

Is this patch queued somewhere to be added or should I re-send it anyway?


Thanks,


Daniel


On 12/05/2017 11:35 AM, Daniel Henrique Barboza wrote:
> Changes from v4:
> - added a 'refcount_bits=1' constraint for internal snapshots
>
> Changes from v3:
> - rebased with master - file name changed from 198 to 201
> - removed Creator/owner information (it can be retrieved with git)
> - added a migration successful check before executing savevm
> - removed a trailing double comma in the snapshot name
>
> Daniel Henrique Barboza (1):
>    tests/qemu-iotests: adding savevm/loadvm with postcopy flag test
>
>   tests/qemu-iotests/201     | 120 +++++++++++++++++++++++++++++++++++++++++++++
>   tests/qemu-iotests/201.out |  23 +++++++++
>   tests/qemu-iotests/group   |   1 +
>   3 files changed, 144 insertions(+)
>   create mode 100755 tests/qemu-iotests/201
>   create mode 100644 tests/qemu-iotests/201.out
>
Daniel Henrique Barboza Jan. 15, 2018, 9:46 a.m. UTC | #2
Ping

On 01/02/2018 11:04 AM, Daniel Henrique Barboza wrote:
> Hi there,
>
> I saw that new iotests were added upstream and decided to re-sent this 
> patch, but
> then I noticed that the files being created by this patch (201 and 
> 201.out) weren't
> created upstream - we have 200 and then 202 and 203.
>
> Is this patch queued somewhere to be added or should I re-send it anyway?
>
>
> Thanks,
>
>
> Daniel
>
>
> On 12/05/2017 11:35 AM, Daniel Henrique Barboza wrote:
>> Changes from v4:
>> - added a 'refcount_bits=1' constraint for internal snapshots
>>
>> Changes from v3:
>> - rebased with master - file name changed from 198 to 201
>> - removed Creator/owner information (it can be retrieved with git)
>> - added a migration successful check before executing savevm
>> - removed a trailing double comma in the snapshot name
>>
>> Daniel Henrique Barboza (1):
>>    tests/qemu-iotests: adding savevm/loadvm with postcopy flag test
>>
>>   tests/qemu-iotests/201     | 120 
>> +++++++++++++++++++++++++++++++++++++++++++++
>>   tests/qemu-iotests/201.out |  23 +++++++++
>>   tests/qemu-iotests/group   |   1 +
>>   3 files changed, 144 insertions(+)
>>   create mode 100755 tests/qemu-iotests/201
>>   create mode 100644 tests/qemu-iotests/201.out
>>
>
>