Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Description of problem:
qemu-iotest 182 in its current implementation requires device hotplogging. We do not have that e.g. on aarch64, so the test fails there.
Version-Release number of selected component (if applicable):
qemu-kvm-2.12.0-70
Steps to Reproduce:
1. Create a build directory and configure it for aarch64. For example:
1a. Start in the source directory
1b. $ mkdir build-aarch64
1c. $ cd build-aarch64
1d. $ ../configure --target-list=aarch64-softmmu
1e. $ make -j 4
2. Then run test 182:
2a. $ cd tests/qemu-iotests
2b. $ ./check -qcow2 182
Actual results:
182 [failed, exit status 1] - output mismatch (see 182.out.bad)
--- tests/qemu-iotests/182.out 2019-04-17 17:42:13.992120808 +0200
+++ build-aarch64/tests/qemu-iotests/182.out.bad 2019-05-07 23:12:37.132641750 +0200
@@ -13,5 +13,5 @@
Formatting 'TEST_DIR/t.qcow2.overlay', fmt=qcow2 size=197120 backing_file=TEST_DIR/t.qcow2 backing_fmt=file cluster_size=65536 lazy_refcounts=off refcount_bits=16
{"return": {}}
{"return": {}}
-{"return": {}}
-*** done
+{"error": {"class": "GenericError", "desc": "Bus 'pcie.0' does not support hotplugging"}}
+Wrong response matching error on handle 1
Failures: 182
Failed 1 of 1 tests
Expected results:
182 0s ...
Passed all 1 tests
Additional info:
Fixed upstream by “iotests: Make 182 do without device_add”.
Hi Jing,
There isn’t much to add to what I’ve written in comment 0 (the description). Running the test (“./check -qcow2 182” in tests/qemu-iotests of the qemu build directory) should work without the test failing (when qemu has been configured for aarch64).
Max
Hi Jing,
You don’t need an ARM environment. Just compile qemu with --target-list=aarch64-softmmu.
Here is what I see:
(Starting from qemu’s source tree)
$ git describe --tags
qemu-kvm-2.12.0-88.module+el8.1.0+4233+bc44be3f
$ mkdir build-aarch64
$ cd build-aarch64
$ ../configure --target-list=aarch64-softmmu --disable-werror
[configure output]
$ make -j 4
[make output]
$ cd tests/qemu-iotests
$ ./check -qcow2 182
QEMU -- "$PWD/../../aarch64-softmmu/qemu-system-aarch64" -nodefaults -machine accel=qtest
QEMU_IMG -- "$PWD/../../qemu-img"
QEMU_IO -- "$PWD/../../qemu-io" --cache writeback -f qcow2
QEMU_NBD -- "$PWD/../../qemu-nbd"
IMGFMT -- qcow2 (compat=1.1)
IMGPROTO -- file
PLATFORM -- Linux/x86_64 localhost 5.2.8-200.fc30.x86_64
TEST_DIR -- $PWD/scratch
SOCKET_SCM_HELPER -- $PWD/socket_scm_helper
182
Passed all 1 tests
So for me, the tast passes now (on qemu-kvm-2.12.0-88.module+el8.1.0+4233+bc44be3f).
Max
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2019:3345
Description of problem: qemu-iotest 182 in its current implementation requires device hotplogging. We do not have that e.g. on aarch64, so the test fails there. Version-Release number of selected component (if applicable): qemu-kvm-2.12.0-70 Steps to Reproduce: 1. Create a build directory and configure it for aarch64. For example: 1a. Start in the source directory 1b. $ mkdir build-aarch64 1c. $ cd build-aarch64 1d. $ ../configure --target-list=aarch64-softmmu 1e. $ make -j 4 2. Then run test 182: 2a. $ cd tests/qemu-iotests 2b. $ ./check -qcow2 182 Actual results: 182 [failed, exit status 1] - output mismatch (see 182.out.bad) --- tests/qemu-iotests/182.out 2019-04-17 17:42:13.992120808 +0200 +++ build-aarch64/tests/qemu-iotests/182.out.bad 2019-05-07 23:12:37.132641750 +0200 @@ -13,5 +13,5 @@ Formatting 'TEST_DIR/t.qcow2.overlay', fmt=qcow2 size=197120 backing_file=TEST_DIR/t.qcow2 backing_fmt=file cluster_size=65536 lazy_refcounts=off refcount_bits=16 {"return": {}} {"return": {}} -{"return": {}} -*** done +{"error": {"class": "GenericError", "desc": "Bus 'pcie.0' does not support hotplugging"}} +Wrong response matching error on handle 1 Failures: 182 Failed 1 of 1 tests Expected results: 182 0s ... Passed all 1 tests Additional info: Fixed upstream by “iotests: Make 182 do without device_add”.