Bug 680730
Summary: | [libvirt] libvirt fails to start when qemu driver init fails | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Haim <hateya> |
Component: | libvirt | Assignee: | Michal Privoznik <mprivozn> |
Status: | CLOSED WORKSFORME | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.1 | CC: | abaron, berrange, dallan, danken, dnaori, eblake, hateya, mgoldboi, xen-maint, yeylon, ykaul, yoyzhang |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2011-04-27 09:47:52 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: | |||
Bug Blocks: | 682015 |
Description
Haim
2011-02-27 12:05:23 UTC
vdsm-hook-vhostmd-4.9-51.el6.x86_64 vdsm-reg-4.9-51.el6.x86_64 vdsm-debuginfo-4.9-51.el6.x86_64 vdsm-cli-4.9-51.el6.x86_64 vdsm-4.9-51.el6.x86_64 vdsm-hook-faqemu-4.9-51.el6.x86_64 libvirt-devel-0.8.7-8.el6.x86_64 libvirt-client-0.8.7-8.el6.x86_64 libvirt-0.8.7-8.el6.x86_64 libvirt-debuginfo-0.8.7-8.el6.x86_64 libvirt-python-0.8.7-8.el6.x86_64 libselinux-2.0.94-2.el6.x86_64 libselinux-python-2.0.94-2.el6.x86_64 libselinux-debuginfo-2.0.94-2.el6.x86_64 selinux-policy-targeted-3.7.19-54.el6.noarch libselinux-utils-2.0.94-2.el6.x86_64 selinux-policy-3.7.19-54.el6.noarch This isn't a crash, libvirtd shuts down in an orderly fashion if a fatal error occurs during initialization. Please set log_debug=1 in libvirtd.conf and restart libvirtd & attach the full debug log it produces. Oh one question - do you have the 'blkio' cgroup mounted (see /proc/mounts) ? If so what kernel version do you have ? This may also be related to bug 688774 |