Description of problem: I created a VM with a disk I tried to run a VM. Version-Release number of selected component (if applicable): engine: rhevm: 3.5.0-0.12.beta.el6ev OS: RHEL - 6Server - 6.6.0.1.el6 host: host OS: RHEL - 6Server - 6.6.0.1.el6 kernel: 2.6.32 - 502.el6.x86_64 KVM: 0.12.1.2 - 2.415.el6_5.14 libvirt: libvirt-0.10.2-46.el6 vdsm: vdsm-4.16.3-3.el6ev.beta How reproducible: 100% Steps to Reproduce: 1. Create any VM with a disk 2. start VM Actual results: Cannot start any VM Expected results: ---
Created attachment 938402 [details] host: /var/log/vdsm - logs
Created attachment 938403 [details] engine: /var/log/ovirt-engine/ - logs
Created attachment 938404 [details] host: /var/log/libvirt
Created attachment 938405 [details] screenshot - host monitor
Created attachment 938406 [details] screenshot - engine - webadmin
i see this in vdsm.log Thread-758::ERROR::2014-09-17 11:53:02,838::vm::2336::vm.Vm::(_startUnderlyingVm) vmId=`adc309bf-4b07-4143-a039-35811f91d2b4`::The vm start process failed Traceback (most recent call last): File "/usr/share/vdsm/virt/vm.py", line 2276, in _startUnderlyingVm self._run() File "/usr/share/vdsm/virt/vm.py", line 3378, in _run self._connection.createXML(domxml, flags), File "/usr/lib64/python2.6/site-packages/vdsm/libvirtconnection.py", line 111, in wrapper ret = f(*args, **kwargs) File "/usr/lib64/python2.6/site-packages/libvirt.py", line 2709, in createXML if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self) libvirtError: Child quit during startup handshake: Input/output error libvirt log is missing from the zip.. please attach libvirt log
Created attachment 939901 [details] libvirtd.log I must update /etc/libvirt/libvirtd.conf log_outputs="1:file:/var/log/libvirt/libvirtd.log" to get this log
I tried install libvirt-0.10.2-45.el6 instead libvirt-0.10.2-46.el6, but no change in behavior. Log was created with libvirt-0.10.2-45.el6
looks like a bad configuration of vdsm/libvirt sebooleans see bug 1139873 for more info *** This bug has been marked as a duplicate of bug 1139873 ***