Hide Forgot
Description of problem: RHEVM-Config allows to change SpiceSecureChannels to: #SpiceSecureChannels.validValues=smain,sinputs,scursor,splayback,srecord,sdisplay Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. [root@kiril-rhevm ~]# rhevm-config -g SpiceSecureChannels SpiceSecureChannels: smain,sinputs version: general 2. [root@kiril-rhevm ~]# vim /etc/rhevm/rhevm-config/rhevm-config.properties 3. [root@kiril-rhevm ~]# rhevm-config -s SpiceSecureChannels="smain, sdisplay" -- cver=general 4. service jbossas restart Stopping jbossas: [ OK ] Starting jbossas: [ OK ] 5. Attempt to open RHEVM AP, and to open VM using Spice. Actual results: VM is down. Exit message internal error unknown spice channel name sdisplay. Getting an Error on RHEVM.log : 2012-03-15 10:35:52,401 INFO [org.ovirt.engine.core.vdsbroker.IsVmDuringInitiatingVDSCommand] (pool-10-thread-49) FINISH, IsVmDuringInitiatingVDSCommand, return: false, log id: 2ad8880c 2012-03-15 10:35:52,406 WARN [org.ovirt.engine.core.bll.RunVmCommand] (pool-10-thread-49) CanDoAction of action RunVm failed. Reasons:ACTION_TYPE_FAILED_VDS_VM_CLUSTER,VAR__ACTION__RUN,VAR__TYPE__VM 2012-03-15 10:48:46,235 INFO [org.ovirt.engine.core.bll.Backend] (main) Start time: 3/15/12 10:48 AM Expected results: Should support ALL new SpiceSecureChannel names. (To workaround it - use display and not sdisplay) Additional info: ** Please see attached screen-shot ** Please see attached rhevm.log
Created attachment 570224 [details] rhevm.log
Created attachment 570225 [details] rhevm-APl_screen-shot
Can't reproduce on my setup. What are the versions of spicec, spice-xpi and client system? Isn't it possibly a dupe of bug 786554 or bug 800306?
Ortal, after some investigation, I understand the bug fully: 1) the immediate cause of the bug is that you added space into SpiceSecureChannels string. If you remove the space, VMs will start OK 2) root cause is remnant of RHEV spice support being written for spice 0.3.x in RHEL 5.x hosts - the "schannel" notation for secure channels. Since RHEL 6.1, this is gone and "s" prefixes have to be removed before the channel names are added to libvirt domain xml Based on above, I'm reassigning the bug to VDSM and they have essentially two options what to do with it: * fix it in the code * convert it to documentation bug for RHEV-M explaining that SpiceSecureChannels must not contain spaces
(removing myself and David Blechter from CC list)
Created attachment 570259 [details] relevant part of vdsm.log when SpiceSecureChannels contains spaces
Created attachment 570260 [details] relevant part of libvirtd.log when SpiceSecureChannels contains spaces
Created attachment 570262 [details] relevant part of vdsm.log when SpiceSecureChannels does not contain spaces
Created attachment 570264 [details] relevant part of libvirtd.log when SpiceSecureChannels does not contain spaces
I created bug #803666 to track root cause of this bug.
SpiceSecureChannels is a piece of the vdsm/Engine API. It is not expected to be human-writable, and in Vdsm side, there should be no auto-corrections such as stripping leading whitespace from channel names. This, if at all, should be done on data entry, in the configuration tool.