Bug 1147494
Summary: | libvirtd crashes when starting a domain with 0 cpu shares | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 7 | Reporter: | Ján Tomko <jtomko> |
Component: | libvirt | Assignee: | Ján Tomko <jtomko> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 7.1 | CC: | dyuan, honzhang, jdenemar, jmiao, lmiksik, mzhan, rbalakri |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-1.2.8-5.el7 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2015-03-05 07:45:54 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Ján Tomko
2014-09-29 11:53:52 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 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. 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 |