[Users] Connecting with vnc to a VM defined as spice

Hello, I have a Windows XP VM in 3.2 beta defined as spice. If I want to connect from a client that only has vnc (a Mac for example) how can I do from User Portal? Even if the VM is powered off then I power it on, on the right I see only spice as an option... Does the user need any special right? And if I select run once form user portal and select vnc then it tries to fire up spice protocol and if I click on "..." icon, only spice is present and selected... Any pre-requisite on engine/node/vm/client? Thanks, Gianluca

On 3 Feb 2013, at 18:53, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
Hello, I have a Windows XP VM in 3.2 beta defined as spice.
If I want to connect from a client that only has vnc (a Mac for example) how can I do from User Portal? Even if the VM is powered off then I power it on, on the right I see only spice as an option... Did you change it in Edit VM dialog? It needs to be switched to vnc there, under Console tab. I wonder if it works anyway, I noticed yesterday on live image 3.2 that it doesn't work - please let us know
Rhanks, michal
Does the user need any special right? And if I select run once form user portal and select vnc then it tries to fire up spice protocol and if I click on "..." icon, only spice is present and selected...
Any pre-requisite on engine/node/vm/client?
Thanks, Gianluca _______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users

On Mon, Feb 4, 2013 at 9:55 AM, Michal Skrivanek wrote:
On 3 Feb 2013, at 18:53, Gianluca Cecchi wrote:
Hello, I have a Windows XP VM in 3.2 beta defined as spice.
If I want to connect from a client that only has vnc (a Mac for example) how can I do from User Portal? Even if the VM is powered off then I power it on, on the right I see only spice as an option... Did you change it in Edit VM dialog? It needs to be switched to vnc there, under Console tab. I wonder if it works anyway, I noticed yesterday on live image 3.2 that it doesn't work - please let us know
When you say edit, you say with vm powered off? Or is it a parameter I can change dynamically? In the first case, this means a running vm you can only connect to it one mode and power off if you want to change? In the mean time I powered off and changed the configuration and set to vnc but it seems it didn't work. I get the message regarding ip:port and password in web admin portal, but when I try to connect I don't even get the prompt for password, but an error. I tried with novnc and tigervnc from a fedora 17 laptop. Let me know how to test further in case. Gianluca

On 4 Feb 2013, at 10:52, Gianluca Cecchi <gianluca.cecchi@gmail.com> wrote:
On Mon, Feb 4, 2013 at 9:55 AM, Michal Skrivanek wrote:
On 3 Feb 2013, at 18:53, Gianluca Cecchi wrote:
Hello, I have a Windows XP VM in 3.2 beta defined as spice.
If I want to connect from a client that only has vnc (a Mac for example) how can I do from User Portal? Even if the VM is powered off then I power it on, on the right I see only spice as an option... Did you change it in Edit VM dialog? It needs to be switched to vnc there, under Console tab. I wonder if it works anyway, I noticed yesterday on live image 3.2 that it doesn't work - please let us know
When you say edit, you say with vm powered off? Or is it a parameter I can change dynamically? In the first case, this means a running vm you can only connect to it one mode and power off if you want to change?
In the mean time I powered off and changed the configuration and set to vnc but it seems it didn't work. I get the message regarding ip:port and password in web admin portal, That's correct for now. In 3.3 this will work better:)
but when I try to connect I don't even get the prompt for password, but an error. That's not correct. What error did you get? Did you use the password/ticket displayed in that popup during the period of 120s?
And in User Portal - was the type correct? Did it show the same popup as in webadmin? Thanks, michal
I tried with novnc and tigervnc from a fedora 17 laptop.
Let me know how to test further in case.
Gianluca

On Mon, Feb 4, 2013 at 11:58 AM, Michal Skrivanek wrote:
In the mean time I powered off and changed the configuration and set to vnc but it seems it didn't work. I get the message regarding ip:port and password in web admin portal, That's correct for now. In 3.3 this will work better:)
Fine. As it is now it very uncomfortable...
but when I try to connect I don't even get the prompt for password, but an error. That's not correct. What error did you get? Did you use the password/ticket displayed in that popup during the period of 120s?
- from vncviewer: vncviewer 192.168.1.102 ::5902 TigerVNC Viewer for X version 1.1.0 - built Jul 23 2012 20:03:56 Copyright (C) 1999-2011 TigerVNC Team and many others (see README.txt) See http://www.tigervnc.org for information on TigerVNC. don;t get the passwotrd but a window with unable connect to socket: Connection refused (111) and on the console from where I ran the command the same: " Mon Feb 4 23:32:29 2013 main: unable connect to socket: Connection refused (111) " - From a web browser window where I point to file:///usr/share/novnc/index.html and then put ip, port and password and press the "connect" button I get: Server disconnected (code: 1006)
And in User Portal - was the type correct? Did it show the same popup as in webadmin?
See the screenshot regarding user portal after clicking on "..." button aside the "console" one: https://docs.google.com/file/d/0BwoPbcrMv8mvSGJZRzlOaUNObEE/edit?usp=sharing But I think I found something that could be the reason. In vdsm.log on host I find this at the moment when probably vnc console started: ?xml version="1.0" encoding="utf-8"?> <domain type="kvm"> <name>F18</name> <uuid>1d3fd942-1aad-4b09-adf0-94a0c4b23b02</uuid> <memory>1572864</memory> <currentMemory>1572864</currentMemory> <vcpu>1</vcpu> <devices> <channel type="unix"> <target name="com.redhat.rhevm.vdsm" type="virtio"/> <source mode="bind" path="/var/lib/libvirt/qemu/channels/F18.com.redhat.rhevm.vdsm"/> </channel> <channel type="unix"> <target name="org.qemu.guest_agent.0" type="virtio"/> <source mode="bind" path="/var/lib/libvirt/qemu/channels/F18.org.qemu.guest_agent.0"/> </channel> <input bus="usb" type="tablet"/> <graphics autoport="yes" keymap="en-us" listen="0" passwd="*****" passwdValidTo="1970-01-01T00:00:01" port="-1" type="vnc"/> Perhaps there is something wrong with passwdValidTo="1970-01-01T00:00:01" or not...? date on host is correct: [root@f18ovn03 vdsm]# date Mon Feb 4 23:48:11 CET 2013 the same on engine a few seconds later [root@f18engine ~]# date Mon Feb 4 23:49:38 CET 201 and on my client [g.cecchi@ope46 ~]$ date Mon Feb 4 23:50:10 CET 2013 Full vdsm.log here: https://docs.google.com/file/d/0BwoPbcrMv8mvM0RlN18wLVhYX3M/edit?usp=sharing HIH, Gianluca

----- Mensaje original -----
De: "Gianluca Cecchi" <gianluca.cecchi@gmail.com> Para: "Michal Skrivanek" <mskrivan@redhat.com> CC: "users" <users@ovirt.org> Enviados: Lunes, 4 de Febrero 2013 10:52:02 Asunto: Re: [Users] Connecting with vnc to a VM defined as spice
In the mean time I powered off and changed the configuration and set to vnc but it seems it didn't work. I get the message regarding ip:port and password in web admin portal, but when I try to connect I don't even get the prompt for password, but an error.
I tried with novnc and tigervnc from a fedora 17 laptop.
Let me know how to test further in case.
Did you make sure that the mentioned port was open in the host firewall? -- -- Adrián Gibanel I.T. Manager +34 675 683 301 www.btactic.com Ens podeu seguir a/Nos podeis seguir en: i Abans d´imprimir aquest missatge, pensa en el medi ambient. El medi ambient és cosa de tothom. / Antes de imprimir el mensaje piensa en el medio ambiente. El medio ambiente es cosa de todos. AVIS: El contingut d'aquest missatge i els seus annexos és confidencial. Si no en sou el destinatari, us fem saber que està prohibit utilitzar-lo, divulgar-lo i/o copiar-lo sense tenir l'autorització corresponent. Si heu rebut aquest missatge per error, us agrairem que ho feu saber immediatament al remitent i que procediu a destruir el missatge . AVISO: El contenido de este mensaje y de sus anexos es confidencial. Si no es el destinatario, les hacemos saber que está prohibido utilizarlo, divulgarlo y/o copiarlo sin tener la autorización correspondiente. Si han recibido este mensaje por error, les agradeceríamos que lo hagan saber inmediatamente al remitente y que procedan a destruir el mensaje .
participants (3)
-
Adrian Gibanel
-
Gianluca Cecchi
-
Michal Skrivanek