Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1430214 - unable to execute QEMU command 'query-iothreads'
Summary: unable to execute QEMU command 'query-iothreads'
Keywords:
Status: CLOSED DUPLICATE of bug 1430258
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.4
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Libvirt Maintainers
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-03-08 03:13 UTC by yisun
Modified: 2017-03-08 10:52 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-08 10:52:36 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description yisun 2017-03-08 03:13:05 UTC 
Description of problem:
When start a domain with latest qemu-kvm and libvirt, get an error: unable to execute QEMU command 'query-iothreads'

Version-Release number of selected component (if applicable):
libvirt-3.1.0-1.el7.x86_64
qemu-kvm-1.5.3-132.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. Define a vm
# virsh define test.xml
Domain test defined from test.xml
2. Start it via virsh cmd
# virsh start test
error: Failed to start domain test
error: internal error: unable to execute QEMU command 'query-iothreads': The command query-iothreads has not been found


Actual results:
cannot start vm, error happened as above

Expected results:
vm can start

Additional info:
This is not reproducible with latest qemu-kvm-rhev-2.8.0-5.el7
Comment 3 Pino Toscano 2017-03-08 10:52:36 UTC 
That's a libvirt regression in 3.1.0, see bug 1430258.

*** This bug has been marked as a duplicate of bug 1430258 ***
Note You need to log in before you can comment on or make changes to this bug.