aboutsummaryrefslogtreecommitdiff
path: root/tests/qemu-iotests/262.out
diff options
context:
space:
mode:
authorMax Reitz <mreitz@redhat.com>2019-10-01 19:48:27 +0200
committerStefan Hajnoczi <stefanha@redhat.com>2019-10-08 14:28:25 +0100
commit4d804b5305ffb4d5fa414c38d4f1bdfb987c8d0b (patch)
tree4e1aac5d59e208588ead438c35c30804b71bac34 /tests/qemu-iotests/262.out
parent8644476e51fa33d7ab637b36b1306d0d4c66177c (diff)
downloadqemu-4d804b5305ffb4d5fa414c38d4f1bdfb987c8d0b.zip
qemu-4d804b5305ffb4d5fa414c38d4f1bdfb987c8d0b.tar.gz
qemu-4d804b5305ffb4d5fa414c38d4f1bdfb987c8d0b.tar.bz2
iotests/262: Switch source/dest VM launch order
Launching the destination VM before the source VM gives us a regression test for HEAD^: The guest device causes a read from the disk image through guess_disk_lchs(). This will not work if the first sector (containing the partition table) is yet unallocated, we use COR, and the node is inactive. By launching the source VM before the destination, however, the COR filter on the source will allocate that area in the image shared between both VMs, thus the problem will not become apparent. Switching the launch order causes the sector to still be unallocated when guess_disk_lchs() runs on the inactive node in the destination VM, and thus we get our test case. Signed-off-by: Max Reitz <mreitz@redhat.com> Reviewed-by: Eric Blake <eblake@redhat.com> Message-id: 20191001174827.11081-3-mreitz@redhat.com Message-Id: <20191001174827.11081-3-mreitz@redhat.com> Signed-off-by: Stefan Hajnoczi <stefanha@redhat.com>
Diffstat (limited to 'tests/qemu-iotests/262.out')
-rw-r--r--tests/qemu-iotests/262.out6
1 files changed, 3 insertions, 3 deletions
diff --git a/tests/qemu-iotests/262.out b/tests/qemu-iotests/262.out
index 5a58e5e..8e04c49 100644
--- a/tests/qemu-iotests/262.out
+++ b/tests/qemu-iotests/262.out
@@ -1,9 +1,9 @@
-Launching source VM...
-Enabling migration QMP events on A...
-{"return": {}}
Launching destination VM...
Enabling migration QMP events on B...
{"return": {}}
+Launching source VM...
+Enabling migration QMP events on A...
+{"return": {}}
Starting migration to B...
{"return": {}}
{"data": {"status": "setup"}, "event": "MIGRATION", "timestamp": {"microseconds": "USECS", "seconds": "SECS"}}