[Users] Notes on setting spice-proxy console option
Hi, I have struggled quite a bit to get it up and running. Over the time, I have accumulated some notes on various things I did so to share with everyone who is interested in doing this. This complements the online doc in a way that might give me a complete picture in one place. However I need some clarifications as I might have forgotten to document certain steps or certain steps I did turn out to be not necessary in the end. It will be great if experts here can help me get the things straight. My setup is like: Browser (firefox 24.2 on RHEL6) ------------ ovirt-engine (3.3.2) ------------ ovirt-node (3.0.3) No direct network connectivity from the browser machine to the node machine. These are the major things I installed for spice-proxy to work: * On ovirt-engine: yum install spice-gtk, virt-viewer, spice-xpi yum-install squid /etc/squid/squid.conf updates: acl localhost src <browser IP addr> #http_access deny CONNECT !SSL_ports http_access deny !Safe_ports http_port 3128 service squid restart make sure iptables allow 3128 engine-config -s SpiceProxyDefault= http://<ovirt-engine-IP>:3128 service ovirt-engine restart * On browser machine running firefox 24.2.0 on RHEL6 for running browser console plugin client yum install spice-xpi. make sure VM's console option is set to SPICE Are the above steps reasonable? any missing or redundant? Additional questions: 1. Will spice-proxy work with the Spice HTML5 client in the browser? 2. Is the spice-proxy architecture diagram like: browser --------- squid proxy - spice-proxy ---------------------- VM 3. I didn't explicitly install any certs for the squid proxy. Is it automatically taken care of? References: http://www.ovirt.org/Console_Client_Resources http://www.ovirt.org/Features/Spice_Proxy https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Virtua... Thanks. David
----- Original Message -----
It should work, You mentioned you used RHEL/CentOS 6.5 as the client (what you call Browser) machine, In that case Can you edit /etc/spice/logger.ini file and change in the line "log4j.rootCategory=INFO, R" INFO to DEBUG? Restart Firefox, make connection to the VM and check ~/.spicec/spice-xpi.log file for line "DEBUG nsPluginInstance::SetHotKeys: release-cursor=shift+f12,toggle-fullscreen=shift+f11" (looking for value of "release-cursor"). If the value is not shift+f12, can you check value of "SpiceReleaseCursorKeys" on the engine with using ovirt-config tool? If the value is shift-f12, can you run on the VM, xev tool and check what keys It can see pressed when pressing shift-f12 combo?
Hi Marian, Here is what I found and with more questions on this SHIFT+F12 issue: ----- Original Message -----
1. I changed the logger.init as you suggested, restrated firefox and launch the spice console. 2. I looked at the spice-xpi.log file but didn't find any trace of "release-cursor" 3. ON the engine machine, I have: SpiceReleaseCursorKeys: shift+f12 version: general 4. What's the xev tool on the VM you want me to run? I can't find such a command. Thanks.
----- Original Message -----
One more way to check this is to change the "console invocation" in "console options dialog" to "Native client" and than try to connect. It will attempt to download a .vv file. If you will have it, you could open it and look for a line like like: release-cursor=shift+f12 If it contains it, you can try to connect from command line using this file like: remote-viewer path_to_console.vv If it does not, it is either misconfigured "SpiceReleaseCursorKeys" or an engine bug. Anyway, you can try to manually edit the console.vv file and add the "release-cursor=shift+f12" line and try to connect using the remote-viewer again if it works this way. This way we will at least find out if the problem is in engine or SPICE or configuration. Thanx, Tomas
----- Original Message -----
I am interested in trying this. I tried before but didn't succeed. Is it enough to configure websocket proxy on the engine like this? WebSocketProxy: <engine-IP-addr>:6100 version: general WebSocketProxyTicketValiditySeconds: 120 version: general Any pointer to a good setup guide? David
Well, this is the default deployment on engine. The engine host is the proxy. If that's what you need there is no additional configuration needed. Just say yes to websocket proxy during installation and import ca.crt to your browser Only if you want to run the proxy elsewhere you need to update the below parameters accordingly Thanks, michal
participants (4)
-
David Li -
Marian Krcmarik -
Michal Skrivanek -
Tomas Jelinek