Closed dougm closed 11 years ago
ESXi 5.5 is required. Does not require vCenter or WebClient.
Not sure why, but needed a separate ReconfigVM with webSocket.port and it needed happen before the existing ReconfigVM. Otherwise, the webSocket.port property was applied to the vmx file, but MKS-RemoteMgr didn't start the websocket proxy unless the VM was power cycled.
For more info on noVNC: http://kanaka.github.io/noVNC/
This looks good. But should we reset the port on disable so folks can switch to normal mode?
The patch includes disabling vnc.webSocket.port with the 'off' command. When vnc is enabled with --ws, the normal vnc.port is also enabled, I believe the websocket proxy talks to this port. And you can still connect to vnc.port with a regular VNC client when vnc.webSocket.port is enabled.
'vnc --ws' will configure a RemoteDisplay.vnc.webSocket.port and rather than spawn a VNC client, prints a noVNC.com URL which can be opened in any HTML5 compliant browser.