> On 2 Jul 2019, at 10:01, kim.karga...@noroff.no wrote:
>
> Hi,
>
> Thanks all. Seems I hadn´t realized that the VNC and SPICE native requires a
> proxy like squid. Going to set that up and see if I can get it working.
yeah, native viewers do not use websockets. A squid proxy would work.
Hi,
Thanks all. Seems I hadn´t realized that the VNC and SPICE native requires a
proxy like squid. Going to set that up and see if I can get it working.
Appreciate the help.
Kind regards
Kim
___
Users mailing list -- users@ovirt.org
To unsubscribe
As i'm accessing the VNC from another network , I do use noVNC.For native VNC
or SPICE - I use it only at home (my lab is there), so i don't have to worry
about that.
I think there were a lot of threads in the mailing list.
Best Regards,Strahil Nikolov
В понеделник, 1 юли 2019 г., 9:37:34
The VM hosts themselves are the graphics servers, when you connect to spice or vnc native it gives you the IP of whatever server the VM is running on. If you can't get to the network of the VM hosts then you have to have a spice proxy in place.As far as I know you cannot use the native vnc client
> On 1 Jul 2019, at 12:31, kim.karga...@noroff.no wrote:
>
> Hi,
>
> We are running ovirt 4.3. The engine is on a bare metal machine and the hosts
> are running on Centos 7. When installing the engine, I set it to be the
> webproxy. When I create a new vm, I select both SPICE+VNC. When
The graphics server is the actual host.
Can you directly access SPICE/VNC port from your workstation?
Best Regards,
Strahil NikolovOn Jul 1, 2019 13:31, kim.karga...@noroff.no wrote:
>
> Hi,
>
> We are running ovirt 4.3. The engine is on a bare metal machine and the hosts
> are running on
6 matches
Mail list logo
