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:
iothreadinfo cannot be used
Version-Release number of selected component (if applicable):
libvirt-1.2.17-1.el7.x86_64
How reproducible:
100%
Steps to Reproduce:
1.prepare a running guest with iothread
# virsh dumpxml test4
<domain type='kvm' id='8'>
<name>test4</name>
<uuid>b1e7936b-104b-430e-9211-d6c61b8df313</uuid>
<memory unit='KiB'>1024000</memory>
<currentMemory unit='KiB'>1024000</currentMemory>
<vcpu placement='static' current='2'>4</vcpu>
<iothreads>2</iothreads>
<cputune>
<emulatorpin cpuset='2'/>
<iothreadpin iothread='1' cpuset='3'/>
</cputune>
2. use iothreadinfo
# virsh iothreadinfo test4
error: Unable to get domain IOThreads information
error: Unable to encode message payload
3.
Actual results:
iothreadinfo cannot be used in new version
Expected results:
can get output
Additional info:
V1 of this issue's patch:
https://www.redhat.com/archives/libvir-list/2015-June/msg01523.html
Fixed upstream:
commit e8c5f61e91025f244bb022b1774a3fc6484625f8
Author: Peter Krempa <pkrempa>
Date: Thu Jul 2 16:46:46 2015 +0200
util: bitmap: Don't alloc overly large binary bitmaps
Optimize the virBitmap to array-of-char bitmap conversion by skipping
trailing zero bytes.
This also fixes a regression when requesting iothread information from a
live VM since after commit 825df8c3158cfaf5f398418471f10f4ff3c3515a the
bitmap returned from virProcessGetAffinity is too big to be formatted
properly via RPC. A user would get the following error:
error: Unable to get domain IOThreads information
error: Unable to encode message payload
Hi Peter, I can reproduce it on libvirt-1.2.17-1.el7.x86_64
Verify it on libvirt-1.2.17-8.el7.x86_64
Step1:
Define a domain fllowing in xml:
...
<vcpu placement='static' current='2'>4</vcpu>
<iothreads>2</iothreads>
<cputune>
<emulatorpin cpuset='2'/>
<iothreadpin iothread='1' cpuset='3'/>
</cputune>
...
Step2:
When domain shutoff, run iothreadinfo:
# virsh iothreadinfo t38
IOThread ID CPU Affinity
---------------------------------------------------
1 3
2 0-7
Step3:
Start domain and run iothreadinfo with --live:
# virsh start t38
Domain t38 started
# virsh iothreadinfo t38 --live
IOThread ID CPU Affinity
---------------------------------------------------
1 3
2 0-7
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://rhn.redhat.com/errata/RHBA-2015-2202.html
Description of problem: iothreadinfo cannot be used Version-Release number of selected component (if applicable): libvirt-1.2.17-1.el7.x86_64 How reproducible: 100% Steps to Reproduce: 1.prepare a running guest with iothread # virsh dumpxml test4 <domain type='kvm' id='8'> <name>test4</name> <uuid>b1e7936b-104b-430e-9211-d6c61b8df313</uuid> <memory unit='KiB'>1024000</memory> <currentMemory unit='KiB'>1024000</currentMemory> <vcpu placement='static' current='2'>4</vcpu> <iothreads>2</iothreads> <cputune> <emulatorpin cpuset='2'/> <iothreadpin iothread='1' cpuset='3'/> </cputune> 2. use iothreadinfo # virsh iothreadinfo test4 error: Unable to get domain IOThreads information error: Unable to encode message payload 3. Actual results: iothreadinfo cannot be used in new version Expected results: can get output Additional info: V1 of this issue's patch: https://www.redhat.com/archives/libvir-list/2015-June/msg01523.html