All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: Thaju <tajudheenk@gmail.com>, Lei YU <mine260309@gmail.com>
Cc: xiuzhi <1450335857@qq.com>, ed <ed@tanous.net>,
	openbmc <openbmc@lists.ozlabs.org>,
	Eddie James <eajames@linux.vnet.ibm.com>
Subject: Re: Does obmc-ikvm work with bmcweb?
Date: Wed, 20 Mar 2019 10:43:17 -0700	[thread overview]
Message-ID: <77cb1f2b-96c5-bd14-eab7-0da527343ce1@linux.intel.com> (raw)
In-Reply-To: <CAH2KKeajTT96Y6rOdKGct+EBLdbFxGo97SEfWzMrcu0hqRh_Hw@mail.gmail.com>

Hi Thaju/Lei,

Check journal (journalctl -f) while you're testing KVM if there is any
suspicious error. In normal opration, you should see logs like below:

Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Got connection 
from client 127.0.0.1
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12   other clients:
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Normal socket 
connection
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Client Protocol 
Version 3.8
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Protocol version 
sent 3.8, using 3.8
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 
rfbProcessClientSecurityType: executing handler for type 1
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 
rfbProcessClientSecurityType: returning securityResult for client rfb 
version >= 3.8
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Pixel format for 
client 127.0.0.1:
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12   32 bpp, depth 
24, little endian
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12   true colour: 
max r 255 g 255 b 255, shift r 16 g 8 b 0
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Using image 
quality level 6 for client 127.0.0.1
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Using JPEG 
subsampling 0, Q79 for client 127.0.0.1
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Using 
compression level 2 for client 127.0.0.1
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Enabling 
NewFBSize protocol extension for client 127.0.0.1
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Enabling 
LastRect protocol extension for client 127.0.0.1
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 
rfbProcessClientNormalMessage: ignoring unsupported encoding type 
Enc(0xFFFFFEFE)
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 
rfbProcessClientNormalMessage: ignoring unsupported encoding type 
Enc(0xFFFFFECC)
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 
rfbProcessClientNormalMessage: ignoring unsupported encoding type 
Enc(0xFFFFFEC8)
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 
rfbProcessClientNormalMessage: ignoring unsupported encoding type 
Enc(0xFFFFFEC7)
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Enabling 
full-color cursor updates for client 127.0.0.1
Mar 19 16:17:12 wolfpass env[1331]: 19/03/2019 16:17:12 Using tight 
encoding for client 127.0.0.1
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19 Client 127.0.0.1 
gone
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19 Statistics 
       events    Transmit/ RawEquiv ( saved)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19 
FramebufferUpdate   :      1 |         0/        0 (  0.0%)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19  LastRect 
     :     58 |       696/      696 (  0.0%)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19  tight 
     :     58 |   1831655/182452920 ( 99.0%)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19  RichCursor 
     :      1 |      1684/     1684 (  0.0%)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19  TOTALS 
     :    118 |   1834035/182455300 ( 99.0%)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19 Statistics 
       events    Received/ RawEquiv ( saved)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19  PointerEvent 
     :      3 |        18/       18 (  0.0%)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19 
FramebufferUpdate   :     59 |       590/      590 (  0.0%)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19  SetEncodings 
     :      1 |        68/       68 (  0.0%)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19  SetPixelFormat 
     :      1 |        20/       20 (  0.0%)
Mar 19 16:17:19 wolfpass env[1331]: 19/03/2019 16:17:19  TOTALS 
     :     64 |       696/      696 (  0.0%)

Also, try these two patches. I added one more patch.
https://gerrit.openbmc-project.xyz/c/openbmc/obmc-ikvm/+/19392
https://gerrit.openbmc-project.xyz/c/openbmc/obmc-ikvm/+/19433

If it doesn't make help, try external connection using Tight VNC viewer.
Currently, external connection is disabled by libvncserver's listening
ip setting so apply below patch if you are going to enable external
connection.

In obmc-ikvm package:
-----------------------
diff --git a/ikvm_server.cpp b/ikvm_server.cpp
index 35310da292be..b7bd5344ed0d 100644
--- a/ikvm_server.cpp
+++ b/ikvm_server.cpp
@@ -44,7 +44,7 @@ Server::Server(const Args& args, Input& i, Video& v) :
      server->cursor->xhot = 1;
      server->cursor->yhot = 1;

-    rfbStringToAddr(&ip[0], &server->listenInterface);
+    //rfbStringToAddr(&ip[0], &server->listenInterface);

      rfbInitServer(server);
-------------------------

Make sure that it's just for test purpose. We intentionally disabled
external connection because of security issue. Also, you might need to
use Tight VNC viewer only. I checked that other VNC viewers don't
support tight encoding properly.

Regards,
Jae


On 3/20/2019 4:12 AM, Thaju wrote:
> Hi Jae/Xiuzhi,
> 
> I have tried enabling KVM as mentioned in the mail thread. But unable to 
> get the video in the web. Also tried using vnc viewer, but connection 
> refused.
> 
> I see the following:
> 
> # obmc-ikvm -v /dev/video0 -f 10 -k /dev/hidg0 -p /dev/hidg1
> 26/02/2019 09:41:04 Unable to establish connection with systemd socket
> 26/02/2019 09:41:04 Listening for VNC connections on TCP port 5900
> 26/02/2019 09:41:04 Listening for VNC connections on TCP6 port 5900
> 26/02/2019 09:42:17 Got connection from client 127.0.0.1
> 26/02/2019 09:42:17   other clients:
> 26/02/2019 09:42:17 Normal socket connection
> 
> # dmesg | grep video
> [   18.921547] aspeed-video 1e700000.video: assigned reserved memory 
> node framebuffer
> [   59.799015] aspeed-video 1e700000.video: Timed out; first mode detect
> 
> obmc-ikvm recipe:
> 
> SUMMARY = "obmc kvm application"
> DESCRIPTION = "Interfaces video device and USB HID device on BMC"
> 
> FILESEXTRAPATHS_append := ":${THISDIR}/${PN}"
> 
> inherit systemd
> inherit obmc-phosphor-systemd
> inherit autotools pkgconfig
> 
> LICENSE = "Apache-2.0"
> LIC_FILES_CHKSUM = "file://LICENSE;md5=e3fc50a88d0a364313df4b21ef20c29e"
> 
> PV = "1.0+git${SRCPV}"
> 
> SRC_URI = "git://github.com/openbmc/obmc-ikvm 
> <http://github.com/openbmc/obmc-ikvm> \
>          file://Fix_video_restarting_sync_issue.patch \
>          "
> SRCREV = "2bc661d34abd1fda92a9d2b256ed88ca0e90d09a"
> 
> DEPENDS += "autoconf-archive"
> DEPENDS += "libvncserver"
> DEPENDS += "sdbusplus"
> DEPENDS += "sdeventplus"
> DEPENDS += "phosphor-logging"
> DEPENDS += "phosphor-dbus-interfaces"
> DEPENDS += "systemd"
> 
> S = "${WORKDIR}/git"
> 
> SERVICE_FILE = "start-ipkvm.service"
> SYSTEMD_PACKAGES = "${PN}"
> SYSTEMD_SERVICE_${PN} += "${SERVICE_FILE}"
> SYSTEMD_DEFAULT_TARGET ?= "${SYSTEMD_DEFAULT_TARGET}"
> 
> What am I doing wrong here?
> Do we need to set "-DBMCWEB_ENABLE_KVM=ON" in bmcweb?
> 
> Regards,
> Thaj
> 
> On Wed, Mar 20, 2019 at 11:01 AM Lei YU <mine260309@gmail.com 
> <mailto:mine260309@gmail.com>> wrote:
> 
>      > Check if there are /dev/hidg0 and /dev/hidg1. If not, check kernel
>      > configs again.
>      > Also, check 'start-ipkvm.service' file whether that launches
>     obmc-ikvm
>      > using this options:
>      > ExecStart=/usr/bin/env obmc-ikvm -v /dev/video0 -f 10 -k
>     /dev/hidg0 -p
>      > /dev/hidg1
> 
>     Confirmed that both /dev/hidg0 and /dev/hidg1 are created, and the
>     service is
>     started with obmc-ikvm -v /dev/video0 -f 10 -k /dev/hidg0 -p /dev/hidg1.
> 
>      >
>      > Try this patch:
>      > https://gerrit.openbmc-project.xyz/c/openbmc/obmc-ikvm/+/19392
> 
>     Unfortunately, the patch does not fix the issue, the KVM page still
>     shows a
>     small black block when browsed to another page and back.
> 

  reply	other threads:[~2019-03-20 17:43 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-14  2:21 Does obmc-ikvm work with bmcweb? xiuzhi
2019-03-14 17:53 ` Jae Hyun Yoo
2019-03-15  7:18   ` xiuzhi
2019-03-15 17:11     ` Jae Hyun Yoo
2019-03-18  2:25       ` Lei YU
2019-03-18 17:21         ` Jae Hyun Yoo
2019-03-18 17:33           ` Jae Hyun Yoo
2019-03-19  3:05             ` xiuzhi
2019-03-19 18:04               ` Jae Hyun Yoo
2019-03-19  9:22             ` Lei YU
2019-03-19 18:09               ` Jae Hyun Yoo
2019-03-20  5:30                 ` Lei YU
2019-03-20 11:12                   ` Thaju
2019-03-20 17:43                     ` Jae Hyun Yoo [this message]
2019-03-21  7:02                       ` Lei YU
2019-03-21 16:19                         ` Jae Hyun Yoo
2019-03-21 16:27                           ` Thaju
2019-03-21 21:31                             ` Jae Hyun Yoo
2019-04-14  7:12                               ` xiuzhi
2019-04-15 19:26                                 ` Jae Hyun Yoo
2019-04-16  1:53                                   ` xiuzhi
2019-03-22  3:34                           ` Lei YU
2019-03-22 15:21                             ` Eddie James
2019-04-04  5:21     ` ikvm refresh failed on host screen 1680x1050 resolution xiuzhi
2019-04-04 17:16       ` Jae Hyun Yoo
2019-04-08  1:14         ` xiuzhi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=77cb1f2b-96c5-bd14-eab7-0da527343ce1@linux.intel.com \
    --to=jae.hyun.yoo@linux.intel.com \
    --cc=1450335857@qq.com \
    --cc=eajames@linux.vnet.ibm.com \
    --cc=ed@tanous.net \
    --cc=mine260309@gmail.com \
    --cc=openbmc@lists.ozlabs.org \
    --cc=tajudheenk@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.