This indeed depends on the libvirt rebase.
(In reply to Pino Toscano from comment #1) > This indeed depends on the libvirt rebase. Fair enough. Just to be clear, that rebase has already happened, so there should be nothing stopping you from changing libguestfs now.
It seems to be working now.
(In reply to Pino Toscano from comment #3) > It seems to be working now. Care to provide pointers to the relevant downstream patch / commit, possibly along with a build log showing how the test suite passes after it's been merged? Just in case we need to dig up this in a couple of years :)
(In reply to Andrea Bolognani from comment #4) > Care to provide pointers to the relevant downstream patch / commit, > possibly along with a build log showing how the test suite passes > after it's been merged? I just tried with a scratch build. I'm not linking it as it will be gone in few days anyway, so it will be a stale/useless reference.
(In reply to Pino Toscano from comment #5) > (In reply to Andrea Bolognani from comment #4) > > Care to provide pointers to the relevant downstream patch / commit, > > possibly along with a build log showing how the test suite passes > > after it's been merged? > > I just tried with a scratch build. I'm not linking it as it will be gone in > few days anyway, so it will be a stale/useless reference. Fair enough. What about the patch / commit?
Checked the build.log and the basic sanity check has been enabled on aarch64. ... + make quickcheck 'QUICKCHECK_TEST_TOOL_ARGS=-t 1200' ./run test-tool/libguestfs-test-tool -t 1200 2019-06-05 10:51:50.569+0000: 5802: info : libvirt version: 5.4.0, package: 1.module+el8.1.0+3304+7eb41d5f (Red Hat, Inc. <http://bugzilla.redhat.com/bugzilla>, 2019-06-04-13:39:49, ) 2019-06-05 10:51:50.569+0000: 5802: info : hostname: arm64-033.build.eng.bos.redhat.com ... ===== TEST FINISHED OK ===== + exit 0 Processing files: libguestfs-1.40.2-10.module+el8.1.0+3311+ebd017c2.aarch64 ...
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/RHBA-2019:3723