Bug 788092 - VDSM: Disable vdsm's ssl'ability influence spice ssl'ability and prevent VM from starting.
Summary: VDSM: Disable vdsm's ssl'ability influence spice ssl'ability and prevent VM f...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: unspecified
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: ---
Assignee: Dan Kenigsberg
QA Contact:
URL:
Whiteboard: virt
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-07 13:19 UTC by Avi Tal
Modified: 2016-04-22 04:59 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-19 10:16:11 UTC
oVirt Team: ---
Embargoed:


Attachments (Terms of Use)
vdsm log (326.09 KB, application/x-compressed-tar)
2012-02-07 13:19 UTC, Avi Tal
no flags Details

Description Avi Tal 2012-02-07 13:19:29 UTC
Created attachment 559940 [details]
vdsm log

vdsm-4.9.3.3-0.fc16.x86_64
qemu-kvm-0.15.1-3.fc16.x86_64
libvirt-0.9.6-4.fc16.x86_64

Description of problem:
Start VM failed when using fake hosts:
vdsm log:
hread-286::ERROR::2012-02-07 14:27:38,849::vm::552::vm.Vm::(_startUnderlyingVm) vmId=`d222d726-3a2d-4a3f-bf7e-e3ffeceb284b`::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)
libvirtError: internal error Child process (LC_ALL=C PATH=/sbin:/usr/sbin:/bin:/usr/bin /usr/libexec/vdsm/vdsm-faqemu -help) status unexpected: exit status 1


As a workaround,i had to create link of qemu-kvm to libexec
# ln -s /usr/bin/qemu-kvm /usr/libexec/

but after creating that link the start VM still failed:

Thread-1945::ERROR::2012-02-07 15:02:25,688::vm::552::vm.Vm::(_startUnderlyingVm) vmId=`d222d726-3a2d-4a3f-bf7e-e3ffeceb284b`::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)
libvirtError: internal error process exited while connecting to monitor: do_spice_init: starting 0.10.1


There for this bug is a test blocker for us.

Comment 1 Avi Tal 2012-02-08 08:06:10 UTC
Correction to the bug summery:
The bug is all around spice ssl'ability that for some reason related to vdsm ssl'ability.

scenario:
1. Installing host/vdsm with ssl.
2. Reconfigure vdsm ssl=false.
3. Try to start VM with spice and ssl true. (backend DB: EnableSpiceRootCertificateValidation=true)

unable to start VM:
vdsm exception:
Thread-1945::ERROR::2012-02-07
15:02:25,688::vm::552::vm.Vm::(_startUnderlyingVm)
vmId=`d222d726-3a2d-4a3f-bf7e-e3ffeceb284b`::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)
libvirtError: internal error process exited while connecting to monitor:
do_spice_init: starting 0.10.1

Comment 3 Michal Skrivanek 2013-08-19 10:16:11 UTC
plain connections are for debug only, there's no need to have additional granularity


Note You need to log in before you can comment on or make changes to this bug.