Bug 1707598

Summary: qemu-iotest 182 fails without device hotplugging support
Product: Red Hat Enterprise Linux 8 Reporter: Hanna Czenczek <hreitz>
Component: qemu-kvmAssignee: Hanna Czenczek <hreitz>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.1CC: drjones, jinzhao, juzhang, rbalakri, virt-maint
Target Milestone: rcKeywords: OtherQA
Target Release: 8.0   
Hardware: aarch64   
OS: Unspecified   
Whiteboard:
Fixed In Version: qemu-kvm-2.12.0-80.module+el8.1.0+3572+48154135 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 20:49:21 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Hanna Czenczek 2019-05-07 21:14:06 UTC
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​”.

Comment 2 Danilo de Paula 2019-07-02 23:25:41 UTC
Fix included in qemu-kvm-2.12.0-80.module+el8.1.0+3572+48154135

Comment 5 Hanna Czenczek 2019-09-23 11:02:52 UTC
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

Comment 7 Hanna Czenczek 2019-09-24 08:48:14 UTC
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

Comment 10 errata-xmlrpc 2019-11-05 20:49:21 UTC
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