On 02/03/2012 04:04 PM, Spyro Polymiadis wrote:
Thanks Itamar - thats very useful information
Ill try and find information on how to "set a password"
Its basically a bog standard installation - is there no password normally? Is the
password required only for connecting to the console via the command line spicec client?
How does the IE/Firefox spice plugin work in this case - as it doesnt prompt for any
passowrd..
the webadmin and user portal will do this for you, and pass the options
to the spice client.
I would have assumed that the console session (weather using spice or vnc) would load
with no password - similar to how console sessions work in vSphere, KVM and proxmox (which
also uses vnc)
that would not be secure...
The jittery mouse - yes i was rdp-ing to my windows VM to load IE.. ill ty it from a
physical windows machine
so you can see this works when using the integrated solution (btw, which
spice activex did you use for IE?)
but spice from vnc has issues with the mouse.
With my other question - how would you determine which VM you are "consoling"
if there are more than 1 on a hypervisor.
the port you connect to. each vm has a different port. the engine gives
you these details in the api.
Cheers
Spyro
----- Original Message -----
From: "Itamar Heim"<iheim(a)redhat.com>
To: "Spyro Polymiadis"<spyro(a)rsp.com.au>
Cc: "Arnon Gilboa"<agilboa(a)redhat.com>, "Alon
Levy"<alevy(a)redhat.com>, users(a)ovirt.org
Sent: Friday, 3 February, 2012 8:59:08 PM
Subject: Re: [Users] Spice plugin for firefox
On 02/03/2012 09:08 AM, Spyro Polymiadis wrote:
> hrmm after some digging i came across this on the hypervisor when i try
> and launch spicec...
>
> /var/log/libvirt/qemu/vm1.log
>
> reds_handle_read_link_done: Peer doesn't support AUTH selection
>
> maybe ill blow that VM away and create a new one...see if that helps
to cover your first question, yes, spice-xpi works well for me from a
fedora 15 machine using default spice packages of fedora.
you need to set the password to connect to spice (just like for VNC).
since it by default expires after a while, it is called a ticket.
you can use the rest API/SDK/CLI to set the ticket.
as for mouse being jittery in IE - do you happen to use it via an RDP
session (if so, try not to nest clients).