| commit | 0049bfac6f538c89b75d23c42d094a883c55b881 | [log] [tgz] |
|---|---|---|
| author | Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com> | Wed Mar 06 15:39:58 2019 -0800 |
| committer | Edward A. James <eajames@us.ibm.com> | Thu Mar 21 19:19:12 2019 +0000 |
| tree | e36092df13d7bd263ead50c8c78c54ffa0e3c5c5 | |
| parent | 06ad085f07765e282aed8a97931c95075cb8e383 [diff] |
Fix video restarting sync issue There is a video start/stop sync issue inbetween ikvm server and ikvm manager because newClient and clientGone callbacks are called by a different thread from libvncserver. To fix this issue, this commit moves the video.start() call from server to manager to unify video control thread. Tested: Open KVM web page and reload the web page by pressing F5. KVM page should be reloaded correctly. Change-Id: Ic0d14ea712510318e9e8f45615a95e82aeaaddf1 Signed-off-by: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
The obmc-ikvm application is a VNC server that provides access to the host graphics output. The application interfaces with the video device on the BMC that captures the host graphics, and then serves that video data on the RFB (remote framebuffer, also known as VNC) protocol. The application also interfaces with the BMC USB gadget device to pass HID events from the BMC to the host, allowing the user to interact with the host system.
Once the host is running and an appropriate HID gadget device is instantiated on the BMC, the application can be started with the following command: obmc-ikvm -v <video device path> -i <HID gadget device path>
For example:
obmc-ikvm -v /dev/video0 -i /dev/hidg0