1244649 – iothreadadd will create a new iothread in xml which will disappear after restart libvirtd

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.

Bug 1244649 - iothreadadd will create a new iothread in xml which will disappear after restart libvirtd

Summary: iothreadadd will create a new iothread in xml which will disappear after rest...

Keywords:
Status:	CLOSED DUPLICATE of bug 1244664
Alias:	None
Product:	Red Hat Enterprise Linux 7
Classification:	Red Hat
Component:	libvirt
Sub Component:
Version:	7.2
Hardware:	x86_64
OS:	Linux
Priority:	medium
Severity:	medium
Target Milestone:	rc
Target Release:	---
Assignee:	John Ferlan
QA Contact:	Virtualization Bugs
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2015-07-20 08:29 UTC by Luyao Huang
Modified:	2015-08-12 12:21 UTC (History)
CC List:	4 users (show)
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:	2015-08-12 12:21:14 UTC
Target Upstream Version:
Embargoed:

Attachments	(Terms of Use)

Description Luyao Huang 2015-07-20 08:29:15 UTC

Description of problem:
iothreadadd will leave a new iothread even create it failed

Version-Release number of selected component (if applicable):
libvirt-1.2.17-2.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1. find a way to make iothreadadd get failed after do it success in qemu side
i chose use iothreadadd when cpuset (although this is a another issue):

# vim /etc/libvirt/qemu.conf
cgroup_controllers = [ "devices", "blkio", "cpu", "cpuacct", "memory"]

# virsh start test4
Domain test4 started

# virsh iothreadinfo test4
 IOThread ID     CPU Affinity   
---------------------------------------------------
 1               0
 2               1


2. add an iothread

# virsh iothreadadd test4 3
error: Requested operation is not valid: failed to set cpuset.cpus in cgroup for id 3

# echo $?
1


3. although iothread return error, but we still show it in iothreadinfo

# virsh iothreadinfo test4
 IOThread ID     CPU Affinity   
---------------------------------------------------
 1               0
 2               1
 3               1


Actual results:
iothreadadd will leave a new iothread even create it failed

Expected results:
return success and print this error in the log, or remove the new create iothread if we get failed in cgroup or set task part (this will be more safe then just print the error in the log)

Additional info:

Comment 1 Luyao Huang 2015-07-20 08:57:38 UTC

Also i notice this won't save the change to status file, which will make it disappear after restart libvirt:

# virsh iothreadadd test4 5
error: Requested operation is not valid: failed to set cpuset.cpus in cgroup for id 5

# virsh iothreadinfo test4
 IOThread ID     CPU Affinity   
---------------------------------------------------
 1               0
 2               1
 4               1
 5               1


# virsh dumpxml test4 |grep "iothreads"
  <iothreads>4</iothreads>
[root@lhuang ~]# virsh dumpxml test4 |grep "iothread"
  <iothreads>4</iothreads>
  <iothreadids>
    <iothread id='4'/>
    <iothread id='5'/>
  </iothreadids>
    <iothreadpin iothread='1' cpuset='0'/>
    <iothreadpin iothread='2' cpuset='1'/>


# service libvirtd restart
Redirecting to /bin/systemctl restart  libvirtd.service


# virsh dumpxml test4 |grep "iothread"
  <iothreads>3</iothreads>
  <iothreadids>
    <iothread id='4'/>
  </iothreadids>
    <iothreadpin iothread='1' cpuset='0'/>
    <iothreadpin iothread='2' cpuset='1'/>

# virsh iothreadadd test4 6
error: internal error: got wrong number of IOThread ids from QEMU monitor. got 5, wanted 4

# virsh iothreadpin test4 6 1
error: invalid argument: iothread 6 not found

# virsh iothreadadd test4 6
error: internal error: unable to execute QEMU command 'object-add': attempt to add duplicate property 'iothread6' to object (type 'container')

Comment 2 Luyao Huang 2015-07-20 09:35:20 UTC

Sorry for forget past the xml in commant 0, getinfo can see it is not a bug here, but comment 1 is the main issue here.

Comment 3 John Ferlan 2015-08-12 12:21:14 UTC


*** This bug has been marked as a duplicate of bug 1244664 ***

Note You need to log in before you can comment on or make changes to this bug.