ikvm on AST2500

[Jae Hyun Yoo]

Hello Konstantin,

The -p and -k options are required for mouse and keyboard supports in
ikvm. If you don't need to use these supports, it'd be okay to go with
your fixes. You may need to check kernel configs for USB virtual hub and
USB gadget supports in case if you are going to use the mouse and
keyboard support in ikvm.

Cheers,

Jae

On 1/24/2020 5:34 AM, Konstantin Klubnichkin wrote:
> Sorry for spamming, but may be my experience will help somebody.
> I've finally got an image both in vncviewer and web interface after 
> starting ikvm without -p and -k parameters.
> 24.01.2020, 15:29, "Konstantin Klubnichkin" <kitsok at yandex-team.ru>:
> 
>     Okay, I've got KVM in web interface after following patch:
>     =====================================================================
>      From c4fec3c77678318a54bb721633dd82d26ac80217 Mon Sep 17 00:00:00 2001
>     From: Konstantin Klubnichkin <kitsok at yandex-team.ru
>     <mailto:kitsok at yandex-team.ru>>
>     Date: Fri, 24 Jan 2020 12:15:39 +0300
>     Subject: [PATCH 1/1] Connect to 127.0.0.1 instead of ::1
>     ---
>     include/kvm_websocket.hpp | 2 +-
>     1 file changed, 1 insertion(+), 1 deletion(-)
>     diff --git a/include/kvm_websocket.hpp b/include/kvm_websocket.hpp
>     index 306c684..ed7c8cf 100644
>     --- a/include/kvm_websocket.hpp
>     +++ b/include/kvm_websocket.hpp
>     @@ -21,7 +21,7 @@ class KvmSession
>     conn(conn), hostSocket(conn.get_io_context()), doingWrite(false)
>     {
>     boost::asio::ip::tcp::endpoint endpoint(
>     - boost::asio::ip::make_address("::1"), 5900);
>     + boost::asio::ip::make_address("127.0.0.1"), 5900);
>     hostSocket.async_connect(
>     endpoint, [this, &conn](const boost::system::error_code& ec) {
>     if (ec)
>     --
>     1.9.1
>     =====================================================================
>     According to netstat -anp, obmc-ikvm really doesn't listen on IPv6
>     address:
>     tcp 7 0 127.0.0.1:5900 0.0.0.0:* LISTEN 272/obmc-ikvm
>     But still there is a black screen.
>     Will try to debug obmc-ikvm
>     Thank you!
>     24.01.2020, 10:28, "Konstantin Klubnichkin" <kitsok at yandex-team.ru
>     <mailto:kitsok at yandex-team.ru>>:
> 
>         Hello, Jae!
>         No luck with TightVNC.
>         I've started tcpdump -i lo port 5900 on my PC and found that
>         there are some packets during first VNC window draw, but then
>         there is no traffic even when the image is changing on the
>         hosts' screen.
>         bmcweb shows nothing at all on KVM page, will try to understand why.
>         Thank you!
>         23.01.2020, 20:22, "Jae Hyun Yoo" <jae.hyun.yoo at linux.intel.com
>         <mailto:jae.hyun.yoo at linux.intel.com>>:
> 
>             Hello Konstantin,
> 
>             Please give it a try again using TightVNC viewer. ikvm uses
>             the Tight
>             encoding so viewer should support the format. Or, you can
>             use bmcweb
>             instead.
> 
>             Cheers,
> 
>             Jae
> 
>                   Thank you!
>                   --
>                   Best regards,
>                   Konstantin Klubnichkin,
>                   lead firmware engineer,
>                   server hardware R&D group,
>                   Yandex Moscow office.
>                   tel: +7-903-510-33-33
> 
>         -- 
>         Best regards,
>         Konstantin Klubnichkin,
>         lead firmware engineer,
>         server hardware R&D group,
>         Yandex Moscow office.
>         tel: +7-903-510-33-33
> 
>     -- 
>     Best regards,
>     Konstantin Klubnichkin,
>     lead firmware engineer,
>     server hardware R&D group,
>     Yandex Moscow office.
>     tel: +7-903-510-33-33
> 
> -- 
> Best regards,
> Konstantin Klubnichkin,
> lead firmware engineer,
> server hardware R&D group,
> Yandex Moscow office.
> tel: +7-903-510-33-33