Re: [Users] Notes on setting up spice-proxy console option
----- Original Message -----
From: "David Li" <david_li(a)sbcglobal.net>
To: "Marian Krcmarik" <mkrcmari(a)redhat.com>
Cc: users(a)ovirt.org
Sent: Thursday, January 30, 2014 11:44:40 PM
Subject: Re: [Users] Notes on setting up spice-proxy console option
Hi Marian,
Here is what I found and with more questions on this SHIFT+F12 issue:
----- Original Message -----
> From: Marian Krcmarik <mkrcmari(a)redhat.com>
> To: David Li <david_li(a)sbcglobal.net>
> Cc: users(a)ovirt.org
> Sent: Wednesday, January 29, 2014 5:51 AM
> Subject: Re: [Users] Notes on setting up spice-proxy console option
>
>
>
> 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?
>
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"
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
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.
_______________________________________________
Users mailing list
Users(a)ovirt.org
http://lists.ovirt.org/mailman/listinfo/users