VNC console behind NAT
Hello, I am able to connect to SPICE that is behind a NAT (via Squid), but am wondering if there is a way to do it with VNC as the console option? I thought I had this working at one point, several installs ago, but it doesn't seem to be the case currently. When I do try to connect to a VM configured to use VNC as the console option, the remote-viewer screen opens, says "Connecting to graphic server", then after about 30 seconds or so says it is unable to connect to the graphic server. Thanks! :-) Regards, Alan
----- Original Message -----
From: "Alan Murrell" <lists@murrell.ca> To: "users" <users@ovirt.org> Sent: Sunday, 20 September, 2015 10:09:51 AM Subject: [ovirt-users] VNC console behind NAT
Hello,
I am able to connect to SPICE that is behind a NAT (via Squid), but am wondering if there is a way to do it with VNC as the console option?
I thought I had this working at one point, several installs ago, but it doesn't seem to be the case currently. When I do try to connect to a VM configured to use VNC as the console option, the remote-viewer screen opens, says "Connecting to graphic server", then after about 30 seconds or so says it is unable to connect to the graphic server.
Display address override would not help? http://wiki.ovirt.org/Features/Display_Address_Override
Thanks! :-)
Regards,
Alan
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
Quoting "Tomas Jelinek" <tjelinek@redhat.com>:
Display address override would not help? http://wiki.ovirt.org/Features/Display_Address_Override
I wasn't aware of that feature, or at least I don't think I was :-) I must have had that enabled previously when I was able to connect via VNC console through NAT via VNC console. Is the VNC port that is used different for each host also? I currently only have one host, and it gives a connection on port 5902. If I added a second host, would it also use 5902 or would the engine assign a different VNC port to it? The reason I ask is that for a multi-host setup, that could become a bit of an issue if they all use the same port (using different host names is not an issue). If the same port is used for all hosts, can this be overridden too? If it can't be, then I suppose one solution would be to setup a a TCP proxy and forward port 5902 to it, then let it handle the connection to the correct host based on the host name used. I hope that makes sense? Regards, Alan
----- Original Message -----
From: "Alan Murrell" <lists@murrell.ca> To: "users" <users@ovirt.org> Cc: "Tomas Jelinek" <tjelinek@redhat.com> Sent: Monday, September 21, 2015 8:00:26 PM Subject: Re: [ovirt-users] VNC console behind NAT
Quoting "Tomas Jelinek" <tjelinek@redhat.com>:
Display address override would not help? http://wiki.ovirt.org/Features/Display_Address_Override
I wasn't aware of that feature, or at least I don't think I was :-) I must have had that enabled previously when I was able to connect via VNC console through NAT via VNC console.
Is the VNC port that is used different for each host also? I currently only have one host, and it gives a connection on port 5902. If I added a second host, would it also use 5902 or would the engine assign a different VNC port to it?
the port is not really deterministic - depends on how many VMs are running and to which you are connected to etc. Imagine you have 2 vms on the same host and connect to both of them - they need to listen on different ports.
The reason I ask is that for a multi-host setup, that could become a bit of an issue if they all use the same port (using different host names is not an issue). If the same port is used for all hosts, can this be overridden too?
no, I don't think so. Maybe using some vdsm hook but it is not a nice solution.
If it can't be, then I suppose one solution would be to setup a a TCP proxy and forward port 5902 to it, then let it handle the connection to the correct host based on the host name used.
I hope that makes sense?
Regards,
Alan
On Sep 22, 2015, at 10:01 , Tomas Jelinek <tjelinek@redhat.com> wrote:
----- Original Message -----
From: "Alan Murrell" <lists@murrell.ca> To: "users" <users@ovirt.org> Cc: "Tomas Jelinek" <tjelinek@redhat.com> Sent: Monday, September 21, 2015 8:00:26 PM Subject: Re: [ovirt-users] VNC console behind NAT
Quoting "Tomas Jelinek" <tjelinek@redhat.com>:
Display address override would not help? http://wiki.ovirt.org/Features/Display_Address_Override
I wasn't aware of that feature, or at least I don't think I was :-) I must have had that enabled previously when I was able to connect via VNC console through NAT via VNC console.
Is the VNC port that is used different for each host also? I currently only have one host, and it gives a connection on port 5902. If I added a second host, would it also use 5902 or would the engine assign a different VNC port to it?
the port is not really deterministic - depends on how many VMs are running and to which you are connected to etc. Imagine you have 2 vms on the same host and connect to both of them - they need to listen on different ports.
normally it's sequential on each host, so in small setup like yours you will get the same port on both host you would need a full proxy. Is websocket proxy & noVNC in browser an option?
The reason I ask is that for a multi-host setup, that could become a bit of an issue if they all use the same port (using different host names is not an issue). If the same port is used for all hosts, can this be overridden too?
no, I don't think so. Maybe using some vdsm hook but it is not a nice solution.
If it can't be, then I suppose one solution would be to setup a a TCP proxy and forward port 5902 to it, then let it handle the connection to the correct host based on the host name used.
I hope that makes sense?
Regards,
Alan
_______________________________________________ Users mailing list Users@ovirt.org http://lists.ovirt.org/mailman/listinfo/users
On Sep 24, 2015, at 09:43 , Alan Murrell <lists@murrell.ca> wrote:
On 23/09/15 07:44 AM, Michal Skrivanek wrote:
you would need a full proxy. Is websocket proxy & noVNC in browser an option?
I have tried both of those and have never been able to get them to work for me.
It is a bit more difficult, it is also not fully equivalent (especially spice_html5 is really an alpha quality) But with the right deployment of websocket-proxy it should work just fine (engine-setup should ask you if you rerun - if you want to run it on engine host; or it can be deployed on a separate host). Then make sure you did indeed import engine's CA into the browser btw, what's the reason for VNC? lack of SPICE client on a particular platform? Thanks, michal
On 24/09/15 12:47 AM, Michal Skrivanek wrote:
btw, what's the reason for VNC? lack of SPICE client on a particular platform?
One of my guests is running Zentyal. For some reason the console does not display very well when using SPICE but with VNC it is fine. Zentyal is built on top of Ubuntu. Oddly, if I install a guest VM with just the same version of Ubuntu that Zentyal is built on, SPICE works fine with that. Not sure what to make of that. Regards, Alan
On 25 Sep 2015, at 06:31, Alan Murrell wrote:
On 24/09/15 12:47 AM, Michal Skrivanek wrote:
btw, what's the reason for VNC? lack of SPICE client on a particular platform?
One of my guests is running Zentyal. For some reason the console does not display very well when using SPICE but with VNC it is fine.
Zentyal is built on top of Ubuntu. Oddly, if I install a guest VM with just the same version of Ubuntu that Zentyal is built on, SPICE works fine with that.
Not sure what to make of that.
Strange Supposing it is a problem with the driver, you can perhaps try the unaccelerated version of display (so it would effectively become similar to VNC performance-wise) In 3.6 you can configure video card and protocol separately…by default QXL - the accelerated "video card" allows SPICE and VNC, and "cirrus" - the legacy card allows VNC you can try SPICE over cirrus…just need to allow that in osinfo config. There should be something like "os.other.devices.display.protocols.value = spice/qxl,vnc/cirrus,vnc/qxl", you can override that for all OSes or just your own. See [1] Thanks, michal
Regards,
Alan
participants (3)
-
Alan Murrell -
Michal Skrivanek -
Tomas Jelinek