Details
-
Task
-
Resolution: Fixed
-
P3: Somewhat important
-
None
-
None
-
None
Description
I'm sure I used to do this a few years ago, but can't seem to figure it out today.
The in-browser VNC viewer has many downsides (being stuck in a browser tab, clipboard not working, unable to type into the taskbar in Windows is probably unrelated but yep that's happening today, mouse cursor getting out of sync and therefore not being able to click some areas, unable to resize the virtual screen).
There's a link to download a virt-viewer file. This file gives a host and port, but I can't connect directly with a vnc viewer for some reason. Maybe because of the proxy, how is that supposed to work? Anyway I discovered the .vv file is meant for an application called virt-viewer, which conveniently is a package on Arch. So I got Arch connected to the VPN today. But this application also times out, doesn't connect. I would think it would know how to deal with the proxy, if that's why.
What about on macOS? virt-viewer is gtk-based: it would be better to use Qt. So I found https://github.com/F1ash/qt-virt-manager; didn't succeed in getting it built yet, but maybe there's some hope eventually.
Anyway being able to use a standard vnc viewer would be convenient. Being able to use the .vv file would be even more convenient (not having to open it up and find the address and port for the vnc viewer).
Do we have docs about this stuff anywhere?
Attachments
Issue Links
- relates to
-
QTQAINFRA-6626 macOS VMs in openNebula are undocumented => unusable
- Closed
-
QTQAINFRA-5815 VNC connection from OpenNebula for Parallels VMs doesn't work
- Closed
-
COIN-1131 VNC does not work for opennebula-vm:s
- Reported