Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Created attachment 486270[details]
libvirt-log
Description of problem:
Sometimes (10-30%) when starting VM through vdsm then machine doesn't start. Vdsm shows:
'libvirtError: monitor socket did not show up.: No such file or directory'
but libvirt:
'14:26:14.952: 30228: info : qemuConnectMonitor:1286 : Failed to connect monitor for fa-host'
logs are attached (the relevant uuid=168ec522-825e-4b1e-aff5-1c9b6f09dff4)
Version-Release number of selected component (if applicable):
libvirt-0.8.7-13.el6.x86_64
vdsm-4.9-54.el6.x86_64
How reproducible:
10-30%
Steps to Reproduce:
1. run some VMs
2.
3.
Actual results:
Expected results:
Additional info:
vdsm-log:
Thread-5799::ERROR::2011-03-18 14:26:19,730::vm::643::vm.Vm::(_startUnderlyingVm) vmId=`168ec522-825e-4b1e-aff5-1c9b6f09dff4`::Traceback (most recent call last):
File "/usr/share/vdsm/vm.py", line 613, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/libvirtvm.py", line 782, in _run
self._connection.createXML(domxml, flags),
File "/usr/share/vdsm/libvirtconnection.py", line 72, in wrapper
raise e
libvirtError: monitor socket did not show up.: No such file or directory
Thread-5799::DEBUG::2011-03-18 14:26:19,732::vm::1776::vm.Vm::(setDownStatus) vmId=`168ec522-825e-4b1e-aff5-1c9b6f09dff4`::Changed state to Down: monitor socket did not show up.: No such file or directory
Comment 2RHEL Program Management
2011-04-04 02:06:26 UTC
Since RHEL 6.1 External Beta has begun, and this bug remains
unresolved, it has been rejected as it is not proposed as
exception or blocker.
Red Hat invites you to ask your support representative to
propose this request, if appropriate and relevant, in the
next release of Red Hat Enterprise Linux.
Created attachment 486270 [details] libvirt-log Description of problem: Sometimes (10-30%) when starting VM through vdsm then machine doesn't start. Vdsm shows: 'libvirtError: monitor socket did not show up.: No such file or directory' but libvirt: '14:26:14.952: 30228: info : qemuConnectMonitor:1286 : Failed to connect monitor for fa-host' logs are attached (the relevant uuid=168ec522-825e-4b1e-aff5-1c9b6f09dff4) Version-Release number of selected component (if applicable): libvirt-0.8.7-13.el6.x86_64 vdsm-4.9-54.el6.x86_64 How reproducible: 10-30% Steps to Reproduce: 1. run some VMs 2. 3. Actual results: Expected results: Additional info: vdsm-log: Thread-5799::ERROR::2011-03-18 14:26:19,730::vm::643::vm.Vm::(_startUnderlyingVm) vmId=`168ec522-825e-4b1e-aff5-1c9b6f09dff4`::Traceback (most recent call last): File "/usr/share/vdsm/vm.py", line 613, in _startUnderlyingVm self._run() File "/usr/share/vdsm/libvirtvm.py", line 782, in _run self._connection.createXML(domxml, flags), File "/usr/share/vdsm/libvirtconnection.py", line 72, in wrapper raise e libvirtError: monitor socket did not show up.: No such file or directory Thread-5799::DEBUG::2011-03-18 14:26:19,732::vm::1776::vm.Vm::(setDownStatus) vmId=`168ec522-825e-4b1e-aff5-1c9b6f09dff4`::Changed state to Down: monitor socket did not show up.: No such file or directory