JetKVM support was built from the device's published source and tried on real hardware (firmware 0.5.9). The picture, the status, sharing the picture with the device's own page and restarting the JetKVM work there. Key presses, keep-awake and Wake-on-LAN are accepted by the device. Typed text and the ATX power extension have so far only been tried against a stand-in.
Servers were built from what the controllers of an ASRock Rack and a Gigabyte board (both AMI MegaRAC) report about themselves, and tried on real boards of both makers. Signing in and out, the status with its temperatures and fans, and reading which power actions the controller offers work on both; a look at the server takes half a second to a second. On one of them the rest was tried as well: the locator light (a light told to blink went out by itself within twenty seconds, so a steady one is asked for, and stays), a restart of the controller (the server untouched), a request to shut down and switching on. A reset was accepted; whether the server restarted could not be seen from here. A power cut pressed seconds after that reset was accepted and not carried out, which is why QKVM now looks whether one was; why the controller dropped it is not yet known. The console opened signed in has so far only been tried on a stand-in. Other makes of controller (iDRAC, iLO, OpenBMC) have not been tried. There is no picture of a server's screen: Redfish has none, and each maker's remote console speaks a protocol of its own.
KVMs with two-factor login enabled are not supported.
QKVM is view-only apart from the actions above. Typing and mouse control happen in the KVM's own console.
