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 1147494 - libvirtd crashes when starting a domain with 0 cpu shares
Summary: libvirtd crashes when starting a domain with 0 cpu shares
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libvirt
Version: 7.1
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Ján Tomko
QA Contact: Virtualization Bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-09-29 11:53 UTC by Ján Tomko
Modified: 2015-03-05 07:45 UTC (History)
7 users (show)

Fixed In Version: libvirt-1.2.8-5.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 07:45:54 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0323 0 normal SHIPPED_LIVE Low: libvirt security, bug fix, and enhancement update 2015-03-05 12:10:54 UTC

Description Ján Tomko 2014-09-29 11:53:52 UTC
Description of problem:
libvirtd crashes when starting a domain with 0 cpu shares

Version-Release number of selected component (if applicable):
libvirt-1.2.8-4.el7

How reproducible:
100 %

Steps to Reproduce:
1. Start a domain with <cputune><shares>0</shares></cputune>

Actual results:
Crash.

Expected results:
No crash.

Comment 1 Ján Tomko 2014-09-29 11:55:46 UTC
Upstream patch:
https://www.redhat.com/archives/libvir-list/2014-September/msg01676.html

Comment 2 Ján Tomko 2014-09-29 12:02:17 UTC
Fixed upstream:
commit e26bbf49cc051b5d5c2a86c572f55953e617e872
Author:     Ján Tomko <jtomko>
CommitDate: 2014-09-29 13:58:43 +0200

    Fix crash cpu_shares change event crash on domain startup
    
    Introduced by commit 0dce260.
    
    qemuDomainEventQueue was called with qemuDomainObjPrivatePtr instead
    of virQEMUDriverPtr.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1147494

git describe: v1.2.9-rc1-21-ge26bbf4

Comment 5 Jincheng Miao 2014-10-15 10:12:17 UTC
This bug could be reproduced in libvirt-1.2.8-4.el7:
# rpm -q libvirt
libvirt-1.2.8-4.el7.x86_64

# virsh edit r6
...
  <cputune>
    <shares>0</shares>
  </cputune>
...

# virsh start r6
error: Failed to start domain r6
error: End of file while reading data: Input/output error
error: Failed to reconnect to the hypervisor


But in latest libvirt-1.2.8-5.el7, it works:
# rpm -q libvirt
libvirt-1.2.8-5.el7.x86_64

# virsh edit r6
...
  <cputune>
    <shares>0</shares>
  </cputune>
...

# virsh start r6
Domain r6 started

So change the status to VERIFIED.

Comment 7 errata-xmlrpc 2015-03-05 07:45:54 UTC
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/RHSA-2015-0323.html


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