Bug 1156038

Summary: [PPC] Libvirt fails to start VM process
Product: Red Hat Enterprise Virtualization Manager Reporter: Ori Gofen <ogofen>
Component: ovirt-engineAssignee: Nobody <nobody>
Status: CLOSED DUPLICATE QA Contact:
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 3.4.3CC: acanan, danken, ecohen, fdeutsch, gklein, iheim, lpeer, lsurette, michal.skrivanek, ogofen, rbalakri, Rhev-m-bugs, sherold, ybronhei, yeylon
Target Milestone: ---Keywords: Regression, Reopened
Target Release: 3.4.4   
Hardware: ppc64   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-26 11:40:20 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: 1150243    
Bug Blocks: 1122979    
Attachments:
Description Flags
logs none

Description Ori Gofen 2014-10-23 12:52:44 UTC
Created attachment 949867 [details]
logs

Description of problem:

Can't run a VM on the new power kvm build.

Thread-190::ERROR::2014-10-23 12:38:40,966::vm::2341::vm.Vm::(_startUnderlyingVm) vmId=`c9890aff-6cbf-4817-82dc-1f33adadf782`::The vm start process failed
Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py", line 2301, in _startUnderlyingVm
    self._run()
  File "/usr/share/vdsm/vm.py", line 3252, in _run
    self._connection.createXML(domxml, flags),
  File "/usr/lib64/python2.7/site-packages/vdsm/libvirtconnection.py", line 92, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2920, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)


Version-Release number of selected component (if applicable):
vdsm-4.14.17-1.pkvm2_1.ppc64


How reproducible:
100%

Steps to Reproduce:
1.run VM

Actual results:
libvirt fails to start qemu process 

Expected results:
VM's should run

Additional info:

Comment 1 Michal Skrivanek 2014-10-23 13:08:28 UTC
looks like the same issue as in bug 1150243 due to the fact that vdsm is preinstalled on the box, much like in the rhev-h case.

Comment 2 Michal Skrivanek 2014-10-23 13:12:35 UTC
workaround is to run "vdsm-tool sebool-config" right after PowerKVM installation

Comment 5 Fabian Deutsch 2014-10-23 14:56:08 UTC

*** This bug has been marked as a duplicate of bug 1150243 ***

Comment 8 Michal Skrivanek 2014-10-24 05:28:20 UTC
Dan, the solution for node is not going to fix this one. Any other option?

Comment 9 Dan Kenigsberg 2014-10-24 10:26:17 UTC
Yaniv Bronheim promised to make a "configurator" out of the set-sebool code. This would make it run when ovirt-host-deploy issues `vdsm-tool configure`.

Comment 10 Yaniv Bronhaim 2014-10-26 11:40:20 UTC

*** This bug has been marked as a duplicate of bug 1157185 ***