Red Hat Bugzilla – Bug 1147494
libvirtd crashes when starting a domain with 0 cpu shares
Last modified: 2015-03-05 02:45:54 EST
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.
Upstream patch: https://www.redhat.com/archives/libvir-list/2014-September/msg01676.html
Fixed upstream: commit e26bbf49cc051b5d5c2a86c572f55953e617e872 Author: Ján Tomko <jtomko@redhat.com> 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