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:
When trying to use libguestfs with libvirt 3.1.0, the appliance cannot be started using the libvirt backend:
libguestfs: error: could not create appliance through libvirt.
Try running qemu directly without libvirt using this environment variable:
export LIBGUESTFS_BACKEND=direct
Original error from libvirt: internal error: unable to execute QEMU command 'query-iothreads': The command query-iothreads has not been found [code=1 int1=-1]
Most probably libvirt assumes a too new QEMU is available, while only 1.5 is around.
Version-Release number of selected component (if applicable):
libvirt-client-3.1.0-1.el7.x86_64
libvirt-daemon-3.1.0-1.el7.x86_64
libvirt-daemon-config-network-3.1.0-1.el7.x86_64
libvirt-daemon-config-nwfilter-3.1.0-1.el7.x86_64
libvirt-daemon-driver-interface-3.1.0-1.el7.x86_64
libvirt-daemon-driver-network-3.1.0-1.el7.x86_64
libvirt-daemon-driver-nodedev-3.1.0-1.el7.x86_64
libvirt-daemon-driver-nwfilter-3.1.0-1.el7.x86_64
libvirt-daemon-driver-qemu-3.1.0-1.el7.x86_64
libvirt-daemon-driver-secret-3.1.0-1.el7.x86_64
libvirt-daemon-driver-storage-3.1.0-1.el7.x86_64
libvirt-daemon-driver-storage-core-3.1.0-1.el7.x86_64
libvirt-daemon-driver-storage-disk-3.1.0-1.el7.x86_64
libvirt-daemon-driver-storage-gluster-3.1.0-1.el7.x86_64
libvirt-daemon-driver-storage-iscsi-3.1.0-1.el7.x86_64
libvirt-daemon-driver-storage-logical-3.1.0-1.el7.x86_64
libvirt-daemon-driver-storage-mpath-3.1.0-1.el7.x86_64
libvirt-daemon-driver-storage-rbd-3.1.0-1.el7.x86_64
libvirt-daemon-driver-storage-scsi-3.1.0-1.el7.x86_64
libvirt-daemon-kvm-3.1.0-1.el7.x86_64
libvirt-devel-3.1.0-1.el7.x86_64
libvirt-docs-3.1.0-1.el7.x86_64
libvirt-libs-3.1.0-1.el7.x86_64
qemu-img-1.5.3-132.el7.x86_64
qemu-kvm-1.5.3-132.el7.x86_64
qemu-kvm-common-1.5.3-132.el7.x86_64
How reproducible:
100% with libvirt 3.1.0.
Steps to Reproduce:
1. Make sure libvirt >= 3.1.0 is available
2. Try to run libguestfs, for example libguestfs-test-tool
Additional info:
This is a regression, since it used to work until libvirt 3.0.0.
Upstream commit:
commit bb0bffb16c2afe976802aae2059c27fdd0845b2f
Author: Pavel Hrdina <phrdina>
Date: Wed Mar 8 10:45:10 2017 +0100
qemu_process: don't probe iothreads if it's not supported by QEMU
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/RHEA-2017:1846
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/RHEA-2017:1846