[Users] test day help -- console

[Greg Sheremeta]

----- Original Message -----
> From: "Michal Skrivanek" <mskrivan at redhat.com>
> To: "Yedidyah Bar David" <didi at redhat.com>
> Cc: "Greg Sheremeta" <gshereme at redhat.com>, "users" <users at ovirt.org>
> Sent: Wednesday, February 12, 2014 12:16:42 PM
> Subject: Re: [Users] test day help -- console
> 
> 
> 
> On 12 Feb 2014, at 10:09, Yedidyah Bar David <didi at redhat.com> wrote:
> 
> > ----- Original Message -----
> >> From: "Michal Skrivanek" <mskrivan at redhat.com>
> >> To: "Greg Sheremeta" <gshereme at redhat.com>
> >> Cc: "users" <users at ovirt.org>
> >> Sent: Wednesday, February 12, 2014 10:43:18 AM
> >> Subject: Re: [Users] test day help -- console
> >> 
> >> 
> >> 
> >> On 11 Feb 2014, at 23:57, Greg Sheremeta <gshereme at redhat.com> wrote:
> >> 
> >>> I'm having a tough time getting a VM console working via VNC. I set a VM
> >>> to
> >>> use VNC, and I installed virt-viewer.
> >>> 
> >>> 1. When I try to open a .vv file with virt-viewer, I get an error "Cannot
> >>> find guest domain /var/tmp/console.vv"
> >> 
> >> Old virt-viewer. Where did you get it from?
> > 
> > It's built into current debian, I use it too. Does it support vv files?
> > Didn't know that. The same package also has 'remote-viewer', which works
> > for me with:
> > remote-viewer vnc://host:port
> 
> Yep. For some reason only remote-viewer works. No idea why
> 
> > 
> >> 
> >>> 2. Using a VNC client to connect to the host with the password in the .vv
> >>> file just immediately disconnects it -- no error message.
> > 
> > For vv files I use the following script:
> > 
> > =========================================================================
> > #!/bin/sh
> > 
> > LOG=$HOME/vv1.log
> > echo ===================== $(date) >> $LOG
> > echo params "$@" >> $LOG
> > 
> > vvfile="$1"
> > host=$(sed -n 's/^host=\([a-zA-Z0-9-]*\).*/\1/p' "$vvfile")
> > port=$(sed -n 's/^port=\([0-9]*\).*/\1/p' "$vvfile")
> > echo "$host" >> $LOG
> > echo "$port" >> $LOG
> > sed -n 's/^password=\(.*\)/\1/p' "$vvfile" | vncviewer -autopass
> > "${host}::${port}" &
> > 
> > sleep 2
> > /bin/rm -f "$vvfile"
> > =========================================================================
> > 
> > Verified now that it works (I seldom use it because the default is spice
> > which works for me).
> 
> Remote-viewer should work the same for VNC. For cclient of choice yes, your
> script is the one to use
> 
> > 
> >> 
> >> Did you make it in 120s?
> > 
> > That was the main reason for this script :-)
> > 
> >> Certificates?
> > 
> > Didn't bother with that.
> 
> Alon would be happy to hear that I'm sure:-D
> I agree, in reality noone bothers.
> 

It's a pretty invasive thing, IMHO. If I see that I need to install a browser certificate for something, first thing I'm going to do is look for the alternative. :/ It's worse than digging out my 2 factor auth token!!

> > 
> >> 
> >>> 3. noVNC just gives me an empty popup with a gray background.
> >> 
> >> You didn't import the engine's CA, did you?
> >> 
> >>> 
> >>> Any ideas?
> >> 
> >> The Console Downloads page has all the info to get it work, did you check
> >> it
> >> out? (linked from main landing page, display options, user portal...so you
> >> shouldn't moss it;)
> > 
> > You refer to 'Console Client Resources', which links to [1]?
> > I had to do some manual work to get spice-xpi working on Debian as it's not
> > packaged for it (and iirc neither are some of the dependencies).
> 
> Yes. If you have some handy tips for Debian please feel free to update the
> page
> 
> > 
> > [1] http://www.ovirt.org/Console_Client_Resources
> > --
> > Didi
>