Bug 743557
Summary: | libvirtd fails to start - Failed to find group record for name 'qemu' | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | RHEL Program Management <pm-rhel> |
Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 6.1 | CC: | acathrow, ajia, dallan, eblake, jdenemar, jwest, llim, mprivozn, msvoboda, mzhan, pm-eus, rackeby, rwu, syeghiay, whuang |
Target Milestone: | rc | Keywords: | ZStream |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | libvirt-0.8.7-18.el6_1.2 | Doc Type: | Bug Fix |
Doc Text: |
Due to a programming error in the initialization code of the libvirtd daemon, the QEMU driver could have failed to find the user or group ID of the qemu application on the system. As a result, libvirtd failed to start. With this update, the error has been corrected and libvirtd now works as expected.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2011-11-07 13:49:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 742646, 771720 | ||
Bug Blocks: |
Description
RHEL Program Management
2011-10-05 11:13:03 UTC
Moving to POST: http://post-office.corp.redhat.com/archives/rhvirt-patches/2011-October/msg00167.html Verify this bug with : libvirt-0.8.7-18.el6_1.2.x86_64 [root@intel-w3520-12-2 z]# /etc/init.d/libvirtd status libvirtd (pid 5407) is running... [root@intel-w3520-12-2 z]# rpm -q libvirt qemu-kvm libvirt-0.8.7-18.el6_1.2.x86_64 qemu-kvm-0.12.1.2-2.160.el6_1.8.x86_64 [root@intel-w3520-12-2 z]# /etc/init.d/libvirtd restart Stopping libvirtd daemon: [ OK ] Starting libvirtd daemon: [ OK ] (In reply to comment #6) > Verify this bug with : > libvirt-0.8.7-18.el6_1.2.x86_64 > > > > [root@intel-w3520-12-2 z]# /etc/init.d/libvirtd status > libvirtd (pid 5407) is running... > [root@intel-w3520-12-2 z]# rpm -q libvirt qemu-kvm > libvirt-0.8.7-18.el6_1.2.x86_64 > qemu-kvm-0.12.1.2-2.160.el6_1.8.x86_64 > [root@intel-w3520-12-2 z]# /etc/init.d/libvirtd restart > Stopping libvirtd daemon: [ OK ] > Starting libvirtd daemon: [ OK ] libvirt-0.8.7-18.el6_1.2.rpm qemu-kvm-0.12.1.2-2.160.el6_1.8 kernel-2.6.32-131.17.1.el6 So are the packages now available via errata? I had a look on our satellite server but they are not there yet. Thanks, Pierre (In reply to comment #8) > So are the packages now available via errata? > > I had a look on our satellite server but they are not there yet. > > Thanks, > Pierre Hi, Pierre These packages should be in errata , but the libvirt's errata had not push yet . Wenlong Ah ok. Will that get pushed today? I'm hoping to upgrade this weekend. Thanks, Pierre (In reply to comment #10) > Ah ok. Will that get pushed today? I'm hoping to upgrade this weekend. Pierre, you should really be asking Red Hat support this kind of question. The people looking at the BZ are engineers and not able to give you definitive answers, but support can. Dave (In reply to comment #11) > Pierre, you should really be asking Red Hat support this kind of question. The > people looking at the BZ are engineers and not able to give you definitive > answers, but support can. Dave Ah ok. No major rush and btw I'm impressed with how quickly this was ported. Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Due to a programming error in the initialization code of the libvirtd daemon, the QEMU driver could have failed to find the user or group ID of the qemu application on the system. As a result, libvirtd failed to start. With this update, the error has been corrected and libvirtd now works as expected. 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. http://rhn.redhat.com/errata/RHBA-2011-1431.html |