Hi Arik,
seems there is a second issue in the xml with a required device not sent:
Here is the xml sent:
http://pastebin.test.redhat.com/501086
This is the error:
2017-07-07 06:06:36,386-0400 ERROR (vm/300ac8d4) [virt.vm] (vmId='300ac8d4-2157-46f6-bc24-291d3da9a83d') The vm start process failed (vm:789)
Traceback (most recent call last):
File "/usr/share/vdsm/virt/vm.py", line 723, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/virt/vm.py", line 2341, in _run
self._connection.createXML(domxml, flags),
File "/usr/lib/python2.7/site-packages/vdsm/ libvirtconnection.py", line 125, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 646, in wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3782, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: Unable to get device ID '(null)': Bad address
Here is some other useful info on the device teardown which can help suggest what was the device:
http://pastebin.test.redhat.com/501087
Here is a grep on the vm id from logs: http://pastebin.test.redhat.com/501085
here is a link to full logs:
http://jenkins.ovirt.org/job/test-repo_ovirt_experimental_ master/7501/artifact/
Can you please have a look?
Thanks,
Dafna
On 07/07/2017 10:03 AM, Dafna Ron wrote:
Thank you :)
I will keep an eye on the tests
On 07/07/2017 09:43 AM, Arik Hadas wrote:
בתאריך 6 ביולי 2017 11:13 PM, "Arik Hadas" <ahadas@redhat.com> כתב:
On Thu, Jul 6, 2017 at 8:40 PM, Dafna Ron <dron@redhat.com> wrote:
Hi,
vm failed to run with libvrt unsupported configuration (see error below) since the patch is related to 4.2 xml configuration and the vm failed to run on unsupported configuration I suspect its related - can you please have a closer look?
Right, good analysis.Will be easy to fix, just need to copy one of VDSM little hacks in:To:I'll do that tomorrow.Not sure why "ci please build" tests passed on that one though.
Fix is posted:
here is a grep from logs on vm id: http://pastebin.test.redhat.co
m/500889
Test failed: 004_basic_sanity.vm_run
Link to suspected patches: https://gerrit.ovirt.org/#/c/7
8955/ Link to Job: http://jenkins.ovirt.org/job/t
est-repo_ovirt_experimental_ma ster/7491/
Error snippet from the log:
<error>
engine log:
2017-07-06 11:26:34,473-04 INFO [org.ovirt.engine.core.bll.Run
VmOnceCommand] (default task-31) [a7b073ec-04ba-434a-95b4-39595 7cae6dc] Lock freed to object 'EngineLock:{exclusiveLocks='[ d3b1b67d-d2fd-4ed7-86d1-795ba2 f10bc0=VM]', sharedLocks=''}'
{"params": {"d3b1b67d-d2fd-4ed7-86d1-795ba2f10bc0": {"status": "Down", "timeOffset": "0", "exitReason": 1, "exitMessage": "unsupported configuration: unknown spice channel name smain", "exitCode": 1}, "notify_time": 4295594320}, "jsonrpc": "2.0", "method": "|virt|VM_status|d3b1b67d-d2fd -4ed7-86d1-795ba2f10bc0"}^@
vdsm log:
2017-07-06 11:26:36,866-0400 ERROR (vm/d3b1b67d) [virt.vm] (vmId='d3b1b67d-d2fd-4ed7-86d1
-795ba2f10bc0') The vm start process failed (vm:789)
Traceback (most recent call last):
File "/usr/share/vdsm/virt/vm.py", line 723, in _startUnderlyingVm
self._run()
File "/usr/share/vdsm/virt/vm.py", line 2328, in _run
self._connection.createXML(domxml, flags),
File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py" , line 125, in wrapper
ret = f(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 646, in wrapper
return func(inst, *args, **kwargs)
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 3782, in createXML
if ret is None:raise libvirtError('virDomainCreateXML() failed', conn=self)
libvirtError: unsupported configuration: unknown spice channel name smain
</error>
_______________________________________________ Infra mailing list Infra@ovirt.org http://lists.ovirt.org/ mailman/listinfo/infra