Bug 987965
| Summary: | Cannot run vm with spice console protocol | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Alona Kaplan <alkaplan> | ||||||||
| Component: | vdsm | Assignee: | Saveliev Peter <peet> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Haim <hateya> | ||||||||
| Severity: | urgent | Docs Contact: | |||||||||
| Priority: | urgent | ||||||||||
| Version: | 3.2 | CC: | abaron, acathrow, alkaplan, bazulay, danken, iheim, mgoldboi, michal.skrivanek, ofrenkel, yeylon | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | 3.3 | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | virt | ||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2013-08-05 14:51:02 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: | |||||||||||
| Bug Blocks: | 918494 | ||||||||||
| Attachments: |
|
||||||||||
Created attachment 777792 [details]
engine log
Note the noisy line which seems related more to storage than to spice:
Thread-3287::WARNING::2013-07-24 16:24:34,414::clientIF::337::vds::(teardownVolumePath) Drive is not a vdsm image: VOLWM_CHUNK_MB:1024 VOLWM_CHUNK_REPLICATE_MULT:2 VOLWM_FREE_PCT:50 _blockDev:False _checkIoTuneCategories:<bound method Drive._checkIoTuneCategories of <vm.Drive object at 0x153d990>> _customize:<bound method ... {'path': ''} truesize:0 type:disk volExtensionChunk:1024 watermarkLimit:536870912
Traceback (most recent call last):
File "/usr/share/vdsm/clientIF.py", line 331, in teardownVolumePath
res = self.irs.teardownImage(drive['domainID'],
File "/usr/share/vdsm/vm.py", line 1342, in __getitem__
raise KeyError(key)
KeyError: 'domainID'
Alona, can you pls provide also libvirtd log for the case? Created attachment 781524 [details]
libvirt log
the real culprit when starting the VM is: 2013-08-01 09:53:04.435+0000: 25244: error : qemuBuildCommandLine:6192 : unsupported configuration: spice secure channels set in XML configuration, but TLS is disabled in qemu.conf However the supplied libvirt.log is not from the same time period as vdsm.log. Alona, can you please confirm some modification re SSL setings? this daoesn't seem to be related to storage (nor networking, despite the numerous nw related errors in libvirt.log) - changing to "virt" once Alona confirms this can be closed worksforme I don't remember modifying any ssl setting. My host is grey-vdsh.eng.lab.tlv.redhat.com you can check it. VM is created with
<graphics autoport="yes" keymap="en-us" listen="0" passwd="*****" passwdValidTo="1970-01-01T00
:00:01" port="-1" tlsPort="-1" type="spice">
<channel mode="secure" name="main"/>
<channel mode="secure" name="inputs"/>
<channel mode="secure" name="cursor"/>
<channel mode="secure" name="playback"/>
<channel mode="secure" name="record"/>
<channel mode="secure" name="display"/>
<channel mode="secure" name="usbredir"/>
<channel mode="secure" name="smartcard"/>
</graphics>
however TLS is disabled in config
> the real culprit when starting the VM is:
> 2013-08-01 09:53:04.435+0000: 25244: error : qemuBuildCommandLine:6192 :
> unsupported configuration: spice secure channels set in XML configuration,
> but TLS is disabled in qemu.conf
>
> However the supplied libvirt.log is not from the same time period as
> vdsm.log.
> Alona, can you please confirm some modification re SSL setings?
we verified that indeed in engine config spice was configured to secure ("SSLEnabled") and in the host it was configured to non-secure, hence the configuration mismatch.
after changing in engine config to SSLEnabled=false we could start vms.
closing with not a bug as this was configuration error.
|
Created attachment 777791 [details] vdsm log Description of problem: Cannot run vm with spice console protocol. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Add a vm 2. Change it console protocol to "spice" 3. Try to the the vm Actual results: Cannot run the vm. Exits with error- "internal error ifname "vnet6" not in key map." Expected results: The vm is up. Additional info: