Closed Makr91 closed 2 years ago
Hi @Makr91,
zadm
just acts as a proxy (unix socket to websocket for webvnc and unix socket to TCP/IP for vnc). If you face issues they are most likely either in the VNC server (bhyve in your case) or the client.
Do you see the same breakage when you use a different VNC client?
edit:
I tested with other VNC clients as well as with an older noVNC version. It looks like the latest noVNC version is incopatible with the bhyve VNC server. As a quick workaround you can download noVNC 1.2.0, unpack it and configure zadm
to use it instead of the bundled 1.3.0:
in /etc/opt/ooce/zadm/zadm.conf
:
"VNC" : {
"novnc_path" : "<path_to_noVNC_1.2.0>"
}
edit2: We've also downgraded the bundled noVNC version for now to have more time to investigate: https://github.com/omniosorg/omnios-extra/pull/1049
New zadm
releases will be published in a few minutes.
I can confirm that using a different VNC client works without issue. I will attempt to downgrade in a few hours and will report back
I updated OmniOS and that fix it, thank you!
Hello All,
I am not sure how zadm implements noVNC, but it would appears that when I use it on a up-date OmniOS r38 install, using a bhyve-release (ie UEFI) based image, but I am getting inverted colors on desktops. This occurs on windows, ubuntu, etc. I also get a few times that the screen becomes "blocky" when looking at just a shell console.
When the screen becomes blocky, refreshing the webpage briefly shows the correct screen. Desktops never become blocky, but they are always inverted.
This occurs on both Firefox and Chromium