Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1051364
Summary: | libvirt monitor socket didn't show up sometimes | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 6 | Reporter: | Martin Kletzander <mkletzan> |
Component: | libvirt | Assignee: | Martin Kletzander <mkletzan> |
Status: | CLOSED ERRATA | QA Contact: | Virtualization Bugs <virt-bugs> |
Severity: | urgent | Docs Contact: | |
Priority: | urgent | ||
Version: | 6.5 | CC: | dyuan, leiwang, moli, mzhan, qguan, rbalakri, rjones, rwu, whuang, wshi, ydu, zhwang |
Target Milestone: | rc | Keywords: | Reopened, Upstream |
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | libvirt-0.10.2-31.el6 | Doc Type: | Bug Fix |
Doc Text: | Story Points: | --- | |
Clone Of: | 892273 | Environment: | |
Last Closed: | 2014-10-14 04:19:40 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: | |||
Bug Depends On: | 892273, 895901 | ||
Bug Blocks: |
Comment 2
Martin Kletzander
2014-01-17 07:48:24 UTC
It's a tiny fix to update unix monitor timeout from 3 to 30(seconds). Update libvirt to libvirt-0.10.2-32.el6, and following the steps in https://bugzilla.redhat.com/show_bug.cgi?id=892273#c19, domain can start normally. If change the TIMEOUT in the qemu wrapper to more than 30 seconds, it will fail as expected: # virsh start rhel6 error: Failed to start domain rhel6 error: internal error Timed out while reading console log output: So move bug 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. http://rhn.redhat.com/errata/RHBA-2014-1374.html |