Does obmc-ikvm work with bmcweb?

[Jae Hyun Yoo]

Hi Lei,

Are you using a web browser from Windows OS? It seems that there is an
issue of Windows websockify/novnc. Use a browser from OS other than
Windows til the issue is resolved.

Did you test it using Tight VNC viewer after enabling external
connection? The reason why I suggested that is to identify whether
this issue comes from KVM web proxy or from KVM server.

Need more information of your test environment.
Server platform:
BMC SoC:
Host OS:

Regards,
Jae

On 3/21/2019 12:02 AM, Lei YU wrote:
>> Check journal (journalctl -f) while you're testing KVM if there is any
>> suspicious error. In normal opration, you should see logs like below:
> 
> I see the same logs as Thaj, only below logs show when the issue occurs.
> 
> Mar 21 05:26:02 romulus env[1564]: 21/03/2019 05:26:02 Unable to
> establish connection with systemd socket
> Mar 21 05:26:02 romulus env[1564]: 21/03/2019 05:26:02 Listening for
> VNC connections on TCP port 5900
> Mar 21 05:26:02 romulus env[1564]: 21/03/2019 05:26:02 Listening for
> VNC connections on TCP6 port 5900
> Mar 21 05:26:06 romulus env[1564]: 21/03/2019 05:26:06 Got connection
> from client 127.0.0.1
> Mar 21 05:26:06 romulus env[1564]: 21/03/2019 05:26:06   other clients:
> Mar 21 05:26:06 romulus env[1564]: 21/03/2019 05:26:06 Normal socket connection
> 
> And sometimes it works, then I see logs like:
> 
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Normal socket connection
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Client Protocol
> Version 3.8
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Protocol
> version sent 3.8, using 3.8
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12
> rfbProcessClientSecurityType: executing handler for type 1
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12
> rfbProcessClientSecurityType: returning securityResult for client rfb
> version >= 3.8
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Pixel format
> for client 192.168.10.11:
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12   32 bpp, depth
> 24, little endian
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12   true colour:
> max r 255 g 255 b 255, shift r 16 g 8 b 0
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Using
> compression level 1 for client 192.168.10.11
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Using image
> quality level 6 for client 192.168.10.11
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Using JPEG
> subsampling 0, Q79 for client 192.168.10.11
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Enabling
> X-style cursor updates for client 192.168.10.11
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Enabling
> full-color cursor updates for client 192.168.10.11
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Enabling cursor
> position updates for client 192.168.10.11
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Enabling
> LastRect protocol extension for client 192.168.10.11
> Mar 21 06:54:12 romulus env[1957]: 21/03/2019 06:54:12 Using tight
> encoding for client 192.168.10.11
> 
> It's found that the VNC server may work when the screen is changed, e.g.
> reboot the OS, or enter the OS.
> When OS is in idle, usually it will not work.
> 
>> 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
> 
> Tried the patches, still the same issue as above.
>