Bug 688946

Summary: libvirt/vdsm 'monitor socket did not show up.: No such file or directory'
Product: Red Hat Enterprise Linux 6 Reporter: Pavel Stehlik <pstehlik>
Component: libvirtAssignee: Daniel Veillard <veillard>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.1CC: dallan, danken, dyuan, eblake, gren, mzhan, nzhang, yoyzhang
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-10 02:56:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
libvirt-log none

Description Pavel Stehlik 2011-03-18 15:43:43 UTC
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 2 RHEL 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.

Comment 3 Dan Kenigsberg 2011-04-28 17:07:30 UTC
It smell like another bug 623712 dup. Can you reproduce this with cgconfig off?