kanaka/noVNC — Issue #118: Intel AMT KVMoIP support
Author: maxnet
Created: 2012-01-07 19:43:01+00:00
State: open

I'm trying to get NoVNC to work with desktop mainboards that support Intel AMT (VNC based KVMoIP functionality)

NoVNC can connect when I change rfb.js slightly:

--- include/rfb.orig.js 2012-01-07 20:01:22.630113578 +0100
+++ include/rfb.js 2012-01-07 20:11:24.958119036 +0100
@@ -652,6 +652,7 @@
case "003.006": rfb_version = 3.3; break; // UltraVNC
case "003.007": rfb_version = 3.7; break;
case "003.008": rfb_version = 3.8; break;
+ case "004.000": rfb_version = 3.8; break; // Intel AMT
default:
return fail("Invalid server version " + sversion);
}

However when I have "true color" enabled, it disconnects instantly.

When I disable "true color", it stays connected, however then I have a black screen with no visual.
Pressing keys on the keyboard does work, and screen resolutions changes do are detected by NoVNC (black screen gets bigger and smaller, but stays black)

I did some packet sniffing, and it seems AMT prefers to use 16 bits per pixel.

Transmission Control Protocol, Src Port: amt-redir-tcp (16994), Dst Port: 49384 (49384), Seq: 8, Ack: 15, Len: 40
Virtual Network Computing
Framebuffer width: 720
Framebuffer height: 400
Bits per pixel: 16
Depth: 16
Big endian flag: False
True color flag: True
Red maximum: 31
Green maximum: 63
Blue maximum: 31
Red shift: 11
Green shift: 5
Blue shift: 0
Padding
Desktop name length: 16
Desktop name: Intel(r) AMT KVM

Am I correct that NoVNC only supports 8 bit and 24 bit?