Bug 795836

Summary: vdsm : Can 't run VM's on fake Fedora16 hosts
Product: [Retired] oVirt Reporter: Oded Ramraz <oramraz>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED DUPLICATE QA Contact: yeylon <yeylon>
Severity: high Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: abaron, acathrow, bazulay, iheim, oramraz, srevivo, ykaul
Target Milestone: ---Keywords: Regression
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-11 21:01:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
vdsm log file none

Description Oded Ramraz 2012-02-21 15:59:25 UTC 
Description of problem:

Whenever I'm trying to run VM's on Fedora16 hosts I'm getting this error:
Thread-937::DEBUG::2012-02-21 17:46:58,761::vm::528::vm.Vm::(_startUnderlyingVm) vmId=`4d89445e-f563-441b-8a62-1599fed3b258`::_ongoingCreations released
Thread-937::ERROR::2012-02-21 17:46:58,764::vm::552::vm.Vm::(_startUnderlyingVm) vmId=`4d89445e-f563-441b-8a62-1599fed3b258`::The vm start process failed
Traceback (most recent call last):
  File "/usr/share/vdsm/vm.py", line 518, in _startUnderlyingVm
    self._run()
  File "/usr/share/vdsm/libvirtvm.py", line 1169, in _run
    self._connection.createXML(domxml, flags),
  File "/usr/share/vdsm/libvirtconnection.py", line 79, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 2100, in createXML
    if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)



Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Oded Ramraz 2012-02-21 16:02:38 UTC 
Created attachment 564737 [details]
vdsm log file
Comment 2 Dan Kenigsberg 2012-03-11 21:01:24 UTC 
You did not supply libvirtd.log (which you should whenever there's a libvirtError in Vdsm.log) but I believe this is a dup of bug 770285. Please reopen if this is not the case.

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