11:40 a.m.
Hello,
wrking on 3.3.2 beta on F19 ovirt repo
For simplicity I set
- no Websocket Procy on engine
# engine-config -g WebSocketProxy
WebSocketProxy: version: general
- Stop my WebSocketProxy previosuly configured
# systemctl status ovirt-websocket-proxy.service
ovirt-websocket-proxy.service - oVirt Engine websockets proxy
Loaded: loaded
(/usr/lib/systemd/system/ovirt-websocket-proxy.service; enabled)
Active: inactive (dead) since Sun 2013-12-15 17:58:45 CET; 18min ago
Main PID: 23556 (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/ovirt-websocket-proxy.service
- set SpiceProxyDefault
# engine-config -g SpiceProxyDefault
SpiceProxyDefault: http://10.4.4.63:3128 version: general
10.4.4.63 is a CentOS 5.10 server with squid enabled
[root@c510 squid]# diff squid.conf squid.conf.orig
578,581d577
<
< acl localnet src 10.4.3.0/24 # RFC1918 possible internal network
< acl localnet src 10.4.4.0/24 # RFC1918 possible internal network
<
624c620
< #http_access deny CONNECT !SSL_ports
---
http_access deny CONNECT !SSL_ports
638d633
< http_access allow localnet
restart ovirt-engine service
My engine is 10.4.4.60
My host is fedora 19 with ip 10.4.4.59 and a running VM
My client is a Fedora 19 with firefox 26 and ip 10.4.3.24
If I open user portal in my client I see that "enable SpiceProxy" is
checked against this VM
(as I set it gobally via engine-config command)
But when I click console button I see this on my client:
$ netstat -an | egrep "10.4.4"
tcp 0 0 10.4.3.24:38061 10.4.4.60:443 TIME_WAIT
tcp 0 0 10.4.3.24:46284 10.4.4.60:22 ESTABLISHED
tcp 0 1 10.4.3.24:43066 10.4.4.59:5900 SYN_SENT
and an error in browser about
unable to connect to graphic server
so it attempts to go to host.
In client /var/log/messages:
Dec 15 18:21:21 tekkaman gnome-session[2864]: (plugin-container:8024):
SpiceXPI-CRITICAL **: controller connect: No such file or directory
Dec 15 18:21:21 tekkaman gnome-session[2864]: (plugin-container:8024):
SpiceXPI-CRITICAL **: controller connect: No such file or directory
Dec 15 18:21:21 tekkaman spice: starting remote-viewer --spice-controller ...
Dec 15 18:21:21 tekkaman spice: XDG_VTNR=1
Dec 15 18:21:21 tekkaman spice: ORBIT_SOCKETDIR=/var/tmp/orbit-g.cecchi
Dec 15 18:21:21 tekkaman spice: XSUNTRANSPORT=shmem
Dec 15 18:21:21 tekkaman spice: XDG_SESSION_ID=1
Dec 15 18:21:21 tekkaman spice: HOSTNAME=tekkaman.localdomain.local
Dec 15 18:21:21 tekkaman spice: GIO_LAUNCHED_DESKTOP_FILE_PID=6719
Dec 15 18:21:21 tekkaman spice: IMSETTINGS_INTEGRATE_DESKTOP=yes
Dec 15 18:21:21 tekkaman spice:
GPG_AGENT_INFO=/run/user/1000/keyring-uNXVI0/gpg:0:1
Dec 15 18:21:21 tekkaman spice: XDG_MENU_PREFIX=gnome-
Dec 15 18:21:21 tekkaman spice: TERM=dumb
Dec 15 18:21:21 tekkaman spice: SHELL=/bin/bash
Dec 15 18:21:21 tekkaman spice: HISTSIZE=1000
Dec 15 18:21:21 tekkaman spice: TMPDIR=/var/tmp
Dec 15 18:21:21 tekkaman spice: XRE_PROFILE_NAME=
Dec 15 18:21:21 tekkaman spice: GJS_DEBUG_OUTPUT=stderr
Dec 15 18:21:21 tekkaman spice:
GNOME_KEYRING_CONTROL=/run/user/1000/keyring-uNXVI0
Dec 15 18:21:21 tekkaman spice: QTDIR=/usr/lib64/qt-3.3
Dec 15 18:21:21 tekkaman spice: GJS_DEBUG_TOPICS=JS ERROR;JS LOG
Dec 15 18:21:21 tekkaman spice: QTINC=/usr/lib64/qt-3.3/include
Dec 15 18:21:21 tekkaman spice: MOZILLA_FIVE_HOME=/usr/lib64/firefox
Dec 15 18:21:21 tekkaman spice: NSS_SSL_CBC_RANDOM_IV=1
Dec 15 18:21:21 tekkaman spice: IMSETTINGS_MODULE=none
Dec 15 18:21:21 tekkaman spice: QT_GRAPHICSSYSTEM_CHECKED=1
Dec 15 18:21:21 tekkaman spice: XRE_PROFILE_LOCAL_PATH=
Dec 15 18:21:21 tekkaman spice: USER=g.cecchi
Dec 15 18:21:21 tekkaman spice: XRE_START_OFFLINE=
Dec 15 18:21:21 tekkaman spice:
LD_LIBRARY_PATH=/usr/lib64/firefox/xulrunner:/usr/lib64/firefox:/usr/lib64/firefox/plugins:/usr/lib64/firefox
Dec 15 18:21:21 tekkaman spice: SSH_AUTH_SOCK=/run/user/1000/keyring-uNXVI0/ssh
Dec 15 18:21:21 tekkaman spice: GNOME_DISABLE_CRASH_DIALOG=1
Dec 15 18:21:21 tekkaman spice:
SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/2864,unix/unix:/tmp/.ICE-unix/2864
Dec 15 18:21:21 tekkaman spice: USERNAME=g.cecchi
Dec 15 18:21:21 tekkaman spice: LIBPATH=/usr/lib64/firefox:/usr/lib64/firefox
Dec 15 18:21:21 tekkaman spice: MOZ_APP_LAUNCHER=/usr/bin/firefox
Dec 15 18:21:21 tekkaman spice:
MOZ_PLUGIN_PATH=/usr/lib64/mozilla/plugins:/usr/lib64/firefox/plugins
Dec 15 18:21:21 tekkaman spice:
GIO_LAUNCHED_DESKTOP_FILE=/usr/share/applications/firefox.desktop
Dec 15 18:21:21 tekkaman spice:
FONTCONFIG_PATH=/etc/fonts:/usr/lib64/firefox/res/Xft
Dec 15 18:21:21 tekkaman spice: DESKTOP_SESSION=gnome
Dec 15 18:21:21 tekkaman spice:
PATH=/usr/lib64/qt-3.3/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/g.cecchi/.local/bin:/home/g.cecchi/bin
Dec 15 18:21:21 tekkaman spice: MAIL=/var/spool/mail/g.cecchi
Dec 15 18:21:21 tekkaman spice: QT_IM_MODULE=ibus
Dec 15 18:21:21 tekkaman spice: PWD=/home/g.cecchi
Dec 15 18:21:21 tekkaman spice: XMODIFIERS=@im=ibus
Dec 15 18:21:21 tekkaman spice: LANG=en_US.UTF-8
Dec 15 18:21:21 tekkaman spice: GNOME_KEYRING_PID=2860
Dec 15 18:21:21 tekkaman spice: KDE_IS_PRELINKED=1
Dec 15 18:21:21 tekkaman spice: XRE_PROFILE_PATH=
Dec 15 18:21:21 tekkaman spice: GDM_LANG=en_US.UTF-8
Dec 15 18:21:21 tekkaman spice: KDEDIRS=/usr
Dec 15 18:21:21 tekkaman spice: XSUNSMESIZE=512
Dec 15 18:21:21 tekkaman spice: GDMSESSION=gnome
Dec 15 18:21:21 tekkaman spice: HISTCONTROL=ignoredups
Dec 15 18:21:21 tekkaman spice: SHLVL=2
Dec 15 18:21:21 tekkaman spice: HOME=/home/g.cecchi
Dec 15 18:21:21 tekkaman spice: XDG_SEAT=seat0
Dec 15 18:21:21 tekkaman spice: GNOME_DESKTOP_SESSION_ID=this-is-deprecated
Dec 15 18:21:21 tekkaman spice:
DYLD_LIBRARY_PATH=/usr/lib64/firefox:/usr/lib64/firefox
Dec 15 18:21:21 tekkaman spice: MOZ_LAUNCHED_CHILD=
Dec 15 18:21:21 tekkaman spice: MOZ_GRE_CONF=/etc/gre.d/gre64.conf
Dec 15 18:21:21 tekkaman spice: QTLIB=/usr/lib64/qt-3.3/lib
Dec 15 18:21:21 tekkaman spice:
DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-G3RfQQysBc,guid=49804c78c033de622c5380b152addb59
Dec 15 18:21:21 tekkaman spice: SPICE_XPI_SOCKET=/tmp/spicec-tYz3e4/spice-xpi
Dec 15 18:21:21 tekkaman spice: NO_EM_RESTART=
Dec 15 18:21:21 tekkaman spice: LESSOPEN=||/usr/bin/lesspipe.sh %s
Dec 15 18:21:21 tekkaman spice: MOZ_CRASHREPORTER_RESTART_ARG_1=
Dec 15 18:21:21 tekkaman spice: SHLIB_PATH=/usr/lib64/firefox:/usr/lib64/firefox
Dec 15 18:21:21 tekkaman spice: XRE_BINARY_PATH=
Dec 15 18:21:21 tekkaman spice: MOZ_CRASHREPORTER_RESTART_ARG_0=/usr/bin/firefox
Dec 15 18:21:21 tekkaman spice: WINDOWPATH=1
Dec 15 18:21:21 tekkaman spice: DISPLAY=:0
Dec 15 18:21:21 tekkaman spice: XDG_RUNTIME_DIR=/run/user/1000
Dec 15 18:21:21 tekkaman spice:
QT_PLUGIN_PATH=/usr/lib64/kde4/plugins:/usr/lib/kde4/plugins
Dec 15 18:21:21 tekkaman spice: XUL_APP_FILE=
Dec 15 18:21:21 tekkaman spice:
MOZ_CRASHREPORTER_DATA_DIRECTORY=/home/g.cecchi/.mozilla/firefox/Crash
Reports
Dec 15 18:21:21 tekkaman spice:
MOZ_CRASHREPORTER_STRINGS_OVERRIDE=/usr/lib64/firefox/browser/crashreporter-override.ini
Dec 15 18:21:21 tekkaman spice: NO_AT_BRIDGE=1
Dec 15 18:21:21 tekkaman spice:
XAUTHORITY=/run/gdm/auth-for-g.cecchi-0Ht3a6/database
Dec 15 18:21:21 tekkaman spice: _=/usr/bin/env
Dec 15 18:21:34 tekkaman spice:
Dec 15 18:21:34 tekkaman spice: (remote-viewer:8709): GSpice-WARNING
**: Could not connect to 10.4.4.59: Socket I/O timed out
Dec 15 18:22:19 tekkaman spice: remote-viewer execution failed
Dec 15 18:22:19 tekkaman gnome-session[2864]: (plugin-container:8024):
SpiceXPI-CRITICAL **: could not get browser window, when trying to
call OnDisconnected
No logs in access.log of squid on 10.4.4.63 host
How to debug further?
What files to check on engine for Spice Proxy?
Tried also with a client that is on the same network as all servers
(10.4.4.0 where engine, proxy, hosts has their ips) and the spice
client opens but I see that it indeed connects to 10.4.4.9, so it is
not using proxy...
tcp 0 0 10.4.4.67:39613 10.4.4.59:5901 ESTABLISHED
Thanks,
Gianluca
4:59 a.m.
New subject: [Users] Spice Proxy seems to try connect to host and not defined proxy
Hi,
AFAIK this feature is present in windows clients only.
@SPICE devel:
Is there a plan to add this support also to Linux clients? To what version?
thanx,
Tomas
PS: I will update the wiki according to the results from this discussion.
----- Original Message -----
7:37 a.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
On Mon, Dec 16, 2013 at 12:39 PM, Marc-André Lureau wrote:
It would be nice to mark that as a note for RHEVM documentation too...
I can post a documentation bug eventually....
But for sure I tested with an updated Fedora 19 client and if I'm not
wrong also with a Fedora 20 beta
And none of them worked...
So how far from "upstream spice-gtk" are Fedora 19-20?
On my Fedora 19 client I have spice-gtk3-0.20-6.fc19.x86_64 btw
When I run console with Spice Proxy enabled from this Fedora 19
client I see that it runs remote-viewer indeed that is included in
installed virt-viewer-0.5.6-1.fc19.x86_64 and
rpm -qR virt-viewer gives also
libspice-client-gtk-3.0.so.4 (the one included in spice-gtk3 version
mentioned above)..
So what I'm missing to be "compliant" on fedora 19 client?
Thanks in advance,
Gianluca
7:56 a.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
----- Original Message -----
I am not a RHEVM user, I don't know where is the documentation you are talking about.
But I know that we track spice-gtk/virt-viewer RFE in bug and erratas for RHEL/RHEVM.
That's surprising, SPICE_PROXY=http://... and virt-viewer "proxy"
configuration should work. Can you describe what you are testing?
So how far from "upstream spice-gtk" are Fedora 19-20?
Not very far.
You said you are using ovirt? With XPI or mime? Could you get the SPICE_DEBUG=1 log and
check that proxy is being used?
Could you check from command line that your HTTP proxy is correctly configured (allow
CONNECT etc)
ex: SPICE_PROXY=http://proxy:3128 remote-viewer spice://host:port
8:09 a.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
On Mon, Dec 16, 2013 at 2:56 PM, Marc-André Lureau wrote:
Note that my original post was to ovirt-users mailing list. See here for it:
http://lists.ovirt.org/pipermail/users/2013-December/018735.html
(see what I got in /var/log/messages output there)
Tomas then forwarded to spice-devel too at a certain point.
So the doc links I referred were:
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Vir...
https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Vir...
But I know that we track spice-gtk/virt-viewer RFE in bug and erratas
for RHEL/RHEVM.
I'm going to search for them to get more info on this, thanks
I'm going to test what you suggested and report
The test was made from fedora 19 in firefox browser and with spice-xpi
installed, against oVirt 3.3.2 beta (based on f19 too and ovirt-beta
repo).
In VM I had set "auto" for spice, so I think it should use virt-viewer
as it did, correct?
And I also have pre-marked the Spice-Proxy checkbox (inherited by
global config set)
Does Spice Proxy work with both the plugin and the native
remote-viewer or only with the latter?
Gianluca
9:36 a.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
----- Original Message -----
If 'auto' is set than it first tries to use the XPI plugin. If it does not find it
than the native impl (using .vv file)
Should with both. For XPI we set the ".Proxy" property (with capital
"P") and for the native we put
"proxy=..." to the .vv file (with small "p") which is AFAIK correct.
If you are using the native impl could you please verify that the "proxy=..." is
indeed present in the .vv file?
Gianluca
5:04 p.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
On Mon, Dec 16, 2013 at 4:36 PM, Tomas Jelinek wrote:
OK... my expression "for sure" was not the reality ;-)
The problem was that I didn't report correctly the clients used (f19
and f20 were actually used for another test).
I had used CentOS 5.10 and CentOS 6.4 in my first tests, so as
Marc-Andre' clarified, they are not able to connect.
I have just tried now with a Fedora 20 with firefox and it was able to
use proxy both with native client and plugin.
Tried also with Fedora 19 and Chrome and was able to use proxy too
In its generated .vv fie I correctly see these lines:
host=10.4.4.58 (one of the two hypervisors)
proxy=http://10.4.4.63:3128 (my setup proxy)
Sorry for my confusion, but at least I learnt that there are indeed
client dependencies...
Gianluca
2:38 a.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
----- Original Message -----
Awesome!
BTW the root cause of this issue was that it was not mentioned on
http://www.ovirt.org/Features/Spice_Proxy ;)
I would love to put the missing info there but I'm still not sure what are the
specific versions where the support has been added.
@Marc-Andre: do you happen to know what where the win/linux versions where this support
has been added to spice? I did not find it anywhere...
4:03 a.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
----- Original Message -----
@Marc-Andre: do you happen to know what where the win/linux versions
where
this support has been added to spice? I did not find it anywhere...
checking the NEWS files:
spice-gtk v0.15
virt-viewer v0.5.5
spice-xpi v2.8.90
9:39 a.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
On Tue, Dec 17, 2013 at 11:26 AM, Tomas Jelinek wrote:
Please note that on F19 I have:
spice-xpi-2.8-3.fc19.x86_64
and on F20 I see there is
spice-xpi-2.8.90-1.fc20.x86_64
SO does this mean that only in upcoming Fedora 20 (right today... ;-)
one would have spice-xpi functionality?
This test seems to confirm:
I'm doing further testing on f19 client with
spice-gtk3-0.20-6.fc19.x86_64
(spice-gtk not installed, is it correct?)
spice-xpi-2.8-3.fc19.x86_64
virt-viewer-0.5.6-1.fc19.x86_64
firefox-26.0-2.fc19.x86_64
I changed proxy (10.4.4.63) port to 80 as at the moment is the only
opened on that lan.
I changed accordingly the engine config and restart
hypervisor ip is 10.4.4.59
From same firefox:
1) if I select native client option I correctly get the console window
for a VM and in netstat
tcp 0 0 10.4.23.21:44980 10.4.4.63:80 ESTABLISHED
2) If I select browser plugin for the same VM I get error and I see
with netstat that it is trying host ip and not proxy one
tcp 0 1 10.4.23.21:51365 10.4.4.59:5901 SYN_SENT
In terminal session before launching firefox I have set:
export SPICE_DEBUG=1
What I get when I try console via spice-xpi is:
(plugin-container:15279): SpiceXPI-CRITICAL **: controller connect: No
such file or directory
(plugin-container:15279): SpiceXPI-CRITICAL **: controller connect: No
such file or directory
while in f20 I get, also with spice plugin:
tcp 0 0 10.4.4.67:32850 10.4.4.63:80 ESTABLISHED
and in ps output:
gcecchi 2145 1 1 09:33 ? 00:00:01 remote-viewer --spice-controller
Hope that can get it also on Fedora 19, if the bug referred for 6.x
and resolved in 6.5 is this one I found:
https://bugzilla.redhat.com/show_bug.cgi?id=994613
should be "only" a matter to port upstram patch to fedora 19, correct?
Thanks,
Gianluca
10:37 a.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
--7fVM7fn5T1d7Fqim
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
hey,
On Tue, Dec 17, 2013 at 04:39:38PM +0100, Gianluca Cecchi wrote:
If I read your email correctly, native client, which is the preferred way
of starting a SPICE console is working with proxy, while starting the
client through the spice-xpi browser plugin is not working. Is there any
specific reason why you want this to work also with the spice-xpi plugin
while native support is fine ?
Christophe
--7fVM7fn5T1d7Fqim
Content-Type: application/pgp-signature
--7fVM7fn5T1d7Fqim--
10:53 a.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
On Tue, Dec 17, 2013 at 5:37 PM, Christophe Fergeau wrote:
No, the fact is that if I leave the default "auto" option, actually it
tries the spice-xpi plugin that then fails and not the remote-viewer.
So I have to manually specify for every VM to use "native".
Is this expected behavior if both spice-xpi and remote-viewer are
found on the client to give precedence to plugin?
Gianluca
11:03 a.m.
New subject: [Users] [Spice-devel] Spice Proxy seems to try connect to host and not defined proxy
--cN+O50sc7gZAK+8F
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
On Tue, Dec 17, 2013 at 05:53:06PM +0100, Gianluca Cecchi wrote:
Tomas already explained this behaviour in this thread:
http://lists.freedesktop.org/archives/spice-devel/2013-December/015784.html
Christophe
--cN+O50sc7gZAK+8F
Content-Type: application/pgp-signature
--cN+O50sc7gZAK+8F--
4224
days inactive
4226
days old
15 comments
4 participants
participants (4)
-
Christophe Fergeau -
Gianluca Cecchi -
Marc-André Lureau -
Tomas Jelinek