Skip to contentSkip to conversation

KVM Support?

DISCUSSION xiuzhi 1 participant 1 message Oct 17, 2018

lore
Share & tools
lore

xiuzhi

author
#0 lore raw

Hi Eddie,
The ikvm video can see by vncviewer, but the mouse and keyboard didn't work on AST2500
The kernel error log:

[   99.326586] configfs-gadget gadget: high-speed config #1: c 
[   99.403704] aspeed_vhub 1e6a0000.usb-vhub: status direction mismatch         
[   99.492831] aspeed_vhub 1e6a0000.usb-vhub: status direction mismatch 

The kernel version is : video-dev5,
commit 2acbc35adcfe15971b701770e1105276a18da9f7

How to debug it?
xiuzhi
Hi Eddie,
Thanks, it works now after increasing the reserved memory size.
But the mouse and keyboard didn't work.
The log is:

root@romulus:~# obmc-ikvm -v /dev/video0 -i /dev/hidg0                                                
11/10/2018 08:05:09 Listening for VNC connections on TCP port 5900                                    
11/10/2018 08:05:09 Listening for VNC connections on TCP6 port 5900                                   
11/10/2018 08:05:26 Got connection from client 192.168.120.59                                         
11/10/2018 08:05:26   other clients:                                                                  
11/10/2018 08:05:26 Normal socket connection                                                          
11/10/2018 08:05:26 Client Protocol Version 3.8                                                       
11/10/2018 08:05:26 Protocol version sent 3.8, using 3.8                                              
11/10/2018 08:05:26 rfbProcessClientSecurityType: executing handler for type 1                        
11/10/2018 08:05:26 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 8
11/10/2018 08:05:26 Pixel format for client 192.168.120.59:                                           
11/10/2018 08:05:26   32 bpp, depth 24, little endian                                                 
11/10/2018 08:05:26   true colour: max r 255 g 255 b 255, shift r 16 g 8 b 0                          
11/10/2018 08:05:26 Using compression level 1 for client 192.168.120.59                               
11/10/2018 08:05:26 Using image quality level 6 for client 192.168.120.59                             
11/10/2018 08:05:26 Using JPEG subsampling 0, Q79 for client 192.168.120.59                           
11/10/2018 08:05:26 Enabling X-style cursor updates for client 192.168.120.59                         
11/10/2018 08:05:26 Enabling full-color cursor updates for client 192.168.120.59                      
11/10/2018 08:05:26 Enabling cursor position updates for client 192.168.120.59                        
11/10/2018 08:05:26 Enabling LastRect protocol extension for client 192.168.120.59                    
11/10/2018 08:05:26 Using tight encoding for client 192.168.120.59                                    
[  843.023930] configfs-gadget gadget: usb_ep_queue error on int endpoint -108                        
failed to write ptr report: 108 Cannot send after transport endpoint shutdown                         
[  843.039086] configfs-gadget gadget: usb_ep_queue error on int endpoint -108                        
failed to write [  843.048251] configfs-gadget gadget: usb_ep_queue error on int endpoint -108        
ptr report: 108 Cannot send after transport endpoint shutdown                                         
[  843.060797] configfs-gadget gadget: usb_ep_queue error on int endpoint -108                        
failed to write ptr report: 108 Cannot send after transport endpoint shutdown                         
[  843.081398] configfs-gadget gadget: usb_ep_queue error on int endpoint -108                        
failed to write ptr report: 108 [  843.091217] configfs-gadget gadget: usb_ep_queue error on int endp8
Cannot send afte[  843.099655] configfs-gadget gadget: usb_ep_queue error on int endpoint -108        
r transport endpoint shutdown                                                                  

...
a[ 843.747250] configfs-gadget gadget: usb_ep_queue error on int endpoint -108
iled to write ptr report: 108 Cannot send after transport endpoi[ 843.760110] configfs-gadget gadget8 nt shutdown
failed to write ptr report: 108 Cannot send after transport endpoint shutdown
failed to write ptr report: 108 Cannot send after transport endpoint shutdown
... ...

Why?
Xiuzhi

------------------ Original ------------------
From: "Eddie James";<[email protected]>;
Send time: Friday, Oct 12, 2018 1:32 AM
To: "xiuzhi"<[email protected]>; "Alexander A. Filippov"<[email protected]>; "openbmc"<[email protected]>;

Subject: Re: KVM Support?

Quoted 15 lines · xiuzhi

Hi Eddie,
An error occured when I tested the ikvm on AST2500 now.

root@romulus:~# obmc-ikvm -v /dev/video0 -i /dev/hidg0
[  192.679314] cma: cma_alloc: alloc failed, req-size: 2304 pages, 
ret: -12
[  192.686061] aspeed-video 1e700000.video: Failed to allocate source 
buffer 1, size[900000]
[  192.696715] aspeed-video 1e700000.video: Failed to start video engine
The .dts file:
               vga_memory: framebuffer@9f000000 {
                        no-map;
                        reg = <0x9f000000 0x01000000>; /* 16M */
                };
                gfx_memory: framebuffer {
                        size = <0x01000000>;

Hi,

You may have to increase the size of the reserved memory. I believe I bumped ours up to 0x04000000.

If you use the latest version of the driver it will initially allocate the largest buffer for size detection, but then will free unnecessary memory once the size is detected. That may help you.

Thanks,
Eddie

Quoted 524 lines
                        alignment = <0x01000000>;
                        compatible = "shared-dma-pool";
                        reusable;
                };
&gfx {
     status = "okay";
     memory-region = <&gfx_memory>;
};
&video {
        status = "okay";
        memory-region = <&gfx_memory>;
};
&vhub {
        status = "okay";
};

How to debug it?
Best,
Xiuzhi

------------------ Original ------------------
*From: * "Eddie James";<[email protected]>;
*Send time:* Friday, Aug 24, 2018 10:46 PM
*To:* "xiuzhi"<[email protected]>; "Alexander A. Filippov"<[email protected]>; "openbmc"<[email protected]>; *Subject: * Re: KVM Support?

Quoted 2 lines · xiuzhi

Hi Eddie,
Is there a schedule for integrating one vnc viewer to phosphor webui ?

Hi Xiuzhi,

Well, the VNC server (and Video Engine driver) integration is targeted for the OpenBMC release in February 2019. Hopefully in master before then. There is currently no plan or work being done to integrate a viewer into the BMC webui. But patches are certainly welcome in this area! It could be as simple as dropping in a noVNC html file... not sure.

And thanks for the help on AST2400!

Eddie

Quoted 16 lines

Best,
Xiuzhi

Quoted 10 lines · xiuzhi

Hi Eddie,
The video-dev2 can work on AST2400, the tightvnc connect to BMC
vncserver stably when the host cpu run centos GUI.
Two issues was found in testing process .
1, The obmc-ikvm will stop connection when host server window flush from one to next on BIOS or kernel booting process.
The error log on AST2400 is :
18/07/2018 13:37:32 Listening for VNC connections on TCP port 5900 18/07/2018 13:37:32 Listening for VNC connections on TCP6 port 5900

[11704.151172] aspeed-video 1e700000.video: resolution changed;
Quoted 4 lines

resetting

Quoted 1 line
[11704.888188] aspeed-video 1e700000.video: resolution changed;

resetting

Quoted 1 line
[11705.613868] aspeed-video 1e700000.video: invalid resolution 

detected

Quoted 95 lines
Quoted 2 lines
[11705.620421] aspeed-video 1e700000.video: resolution changed;

couldn't get new resolution

OK, I noticed a similar issue on AST2500 when immediately detecting resolution after mode change. I added a delay, but it probably needs to be longer on AST2400... Also, most client's don't handle server-side resize, so usually the window will close and you'll have to re-open anyway I think, if the size is changing.

Thanks,
Eddie

Quoted 83 lines

2, The VNC Viewer can not connect to bmc server.
The error on VNC Viewer client is :
" Attempting to reconnect to VNC Server ...
RFB protocol error:unknown rect encoding 7
"

The error log on BMC is :
18/07/2018 14:03:18 Got connection from client 192.168.120.58
18/07/2018 14:03:18 other clients:
18/07/2018 14:03:18 Normal socket connection
18/07/2018 14:03:18 Client Protocol Version 3.8 18/07/2018 14:03:18 Protocol version sent 3.8, using 3.8 18/07/2018 14:03:18 rfbProcessClientSecurityType: executing handler for type 1
18/07/2018 14:03:18 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
18/07/2018 14:03:18 Enabling full-color cursor updates for client 192.168.120.58
18/07/2018 14:03:18 Enabling NewFBSize protocol extension for client 192.168.120.58
18/07/2018 14:03:18 Using ZRLE encoding for client 192.168.120.58 18/07/2018 14:03:18 Pixel format for client 192.168.120.58:
18/07/2018 14:03:18 8 bpp, depth 6
18/07/2018 14:03:18 true colour: max r 3 g 3 b 3, shift r 4 g 2 b 0
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
18/07/2018 14:03:18 Enabling full-color cursor updates for client 192.168.120.58
18/07/2018 14:03:18 Enabling NewFBSize protocol extension for client 192.168.120.58
18/07/2018 14:03:18 Switching from ZRLE to raw Encoding for client 192.168.120.58
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000015)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
18/07/2018 14:03:18 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
18/07/2018 14:03:18 Enabling full-color cursor updates for client 192.168.120.58
18/07/2018 14:03:18 Enabling NewFBSize protocol extension for client 192.168.120.58
18/07/2018 14:03:18 Switching from raw to ZRLE Encoding for client 192.168.120.58
18/07/2018 14:03:18 Pixel format for client 192.168.120.58:
18/07/2018 14:03:18 32 bpp, depth 24, little endian
18/07/2018 14:03:18 true colour: max r 255 g 255 b 255, shift r 16 g
8 b 0
18/07/2018 14:03:19 rfbProcessClientNormalMessage: read: Connection reset by peer
18/07/2018 14:03:19 Client 192.168.120.58 gone
18/07/2018 14:03:19 Statistics events Transmit/ RawEquiv (
saved)

18/07/2018 14:03:19  FramebufferUpdate   :      3 |  0/     0 (  0.0%)
18/07/2018 14:03:19  tight               :      1 |  33807/  3145740 (

98.9%)
18/07/2018 14:03:19 raw : 1 | 16396/ 16396
( 0.0%)
18/07/2018 14:03:19 ZRLE : 2 | 62/ 3932160

(100.0%)

Quoted 23 lines
Quoted 23 lines

18/07/2018 14:03:19 RichCursor : 3 | 429/ 429 (
0.0%)
18/07/2018 14:03:19 TOTALS : 10 | 50694/ 7094725 (
99.3%)
18/07/2018 14:03:19 Statistics events Received/ RawEquiv (
saved)

18/07/2018 14:03:19  FramebufferUpdate   :      4 | 40/    40 (  0.0%)
18/07/2018 14:03:19  SetPixelFormat      :      2 | 40/    40 (  0.0%)
18/07/2018 14:03:19  SetEncodings        :      3 |  168/     168 (

0.0%)
18/07/2018 14:03:19 TOTALS : 9 | 248/ 248 (
0.0%)

Best,
Xiuzhi
Hi Eddie,
Very good work!
The video-dev2 works on AST2400 now, I will do more test.
Thanks,
Xiuzhi

Quoted 2 lines · Eddie James
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines · xiuzhi
Quoted 6 lines

Hi Eddie,
I tested the new update source of video-dev on AST2400 and
AST2500. It works on AST2500.
On AST2400,the vncviewer can connect vncserver sucessful, but its
window was blank, not shown any information of the host screen . Would you like to give me some advice or instruments on how to

debug

Quoted 4 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line

this issue?

Hey, I also just pushed a new branch to my github with some simplifications to the driver... It no longer uses the auto mode

and may

Quoted 5 lines
Quoted 5 lines

work better on AST2400... I don't have any AST2400 to test on, but let me know if you have any luck:

https://github.com/eddiejames/linux/commits/video-dev2

Quoted 7 lines
Quoted 7 lines

Thanks,
Eddie

Quoted 4 lines

Hi,

You could try enabling the debug tracing, if dynamic debug is

enabled

Quoted 3 lines
Quoted 3 lines
Quoted 3 lines

on your kernel. (CONFIG_DYNAMIC_DEBUG)

echo file aspeed-video.c +p >

/sys/kernel/debug/dynamic_debug/control

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

That should print every register access, as well as some other info.

Thanks,
Eddie

Quoted 2 lines

Hi,

Quoted 25 lines
Quoted 4 lines
Quoted 1 line
Quoted 1 line

There are some differences with the video engine between the

AST2400 and

Quoted 2 lines
Quoted 2 lines

AST2500 that I haven't addressed yet, so probably the driver is not working correctly on the AST2400 yet. Some registers have

different bit

Quoted 1 line
Quoted 1 line
Quoted 1 line

mapping, and things like that. Sorry about that... thanks for

trying it

Quoted 18 lines
Quoted 18 lines
Quoted 18 lines

out! I'll look at the changes needed for AST2400 next.

Thanks,

Eddie

Quoted 10 lines · xiuzhi

Hi Eddie,
Now It works, but the vncviewer can not connect the BMC server
successful.
When I use vncviewer connect to the BMC the error read:
"RFB protocol error: bad desktop size 0x1"
"RFB protocol error: unknow rect encoding 7"
The information on BMC are :

root@zhaoxinc:~# obmc-ikvm -v /dev/video0 -i /dev/hidg0
frame buffer size: 3145728
19/07/2018 08:20:57 Listening for VNC connections on TCP port 

5900

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

19/07/2018 08:20:57 Listening for VNC connections on TCP6

port 5900

Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines
Quoted 7 lines

19/07/2018 08:52:08 Got connection from client 192.168.120.58
19/07/2018 08:52:08 other clients:
19/07/2018 08:52:08 Normal socket connection 19/07/2018 08:52:08 Client Protocol Version 3.8 19/07/2018 08:52:08 Protocol version sent 3.8, using 3.8 19/07/2018 08:52:08 rfbProcessClientSecurityType: executing

handler

Quoted 36 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

for type 1
19/07/2018 08:52:08 rfbProcessClientSecurityType: returning securityResult for client rfb version >= 3.8 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018) 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016) 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

unsupported encoding type Enc(0x00000015)
19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
19/07/2018 08:52:08 Enabling full-color cursor updates for client 192.168.120.58
19/07/2018 08:52:08 Enabling NewFBSize protocol extension for

client

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

192.168.120.58
19/07/2018 08:52:08 Using ZRLE encoding for client 192.168.120.58 19/07/2018 08:52:08 Pixel format for client 192.168.120.58:
19/07/2018 08:52:08 8 bpp, depth 6
19/07/2018 08:52:08 true colour: max r 3 g 3 b 3, shift r 4 g

2 b 0

Quoted 5 lines
Quoted 5 lines
Quoted 5 lines
Quoted 5 lines

19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018) 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016) 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

unsupported encoding type Enc(0x00000015)
19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
19/07/2018 08:52:08 Enabling full-color cursor updates for client 192.168.120.58
19/07/2018 08:52:08 Enabling NewFBSize protocol extension for

Quoted 3 lines

client

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

192.168.120.58
19/07/2018 08:52:08 Switching from ZRLE to raw Encoding for

client

Quoted 14 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

192.168.120.58
19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000018) 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x00000016) 19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

unsupported encoding type Enc(0x00000015)
19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0x0000000F)
19/07/2018 08:52:08 rfbProcessClientNormalMessage: ignoring unsupported encoding type Enc(0xFFFFFEC6)
19/07/2018 08:52:08 Enabling full-color cursor updates for client 192.168.120.58
19/07/2018 08:52:08 Enabling NewFBSize protocol extension for

Quoted 3 lines

client

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

192.168.120.58
19/07/2018 08:52:08 Switching from raw to ZRLE Encoding for

client

Quoted 10 lines
Quoted 7 lines
Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

192.168.120.58
19/07/2018 08:52:08 Pixel format for client 192.168.120.58:
19/07/2018 08:52:08 32 bpp, depth 24, little endian
19/07/2018 08:52:08 true colour: max r 255 g 255 b 255, shift r

16 g

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

8 b 0

[ 6928.751385] aspeed-video 1e700000.video: disabling comp

ready irq,

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

seq_ctrl[000500a8]
19/07/2018 08:52:09 rfbProcessClientNormalMessage: read:

Connection

Quoted 58 lines
Quoted 47 lines
Quoted 47 lines
Quoted 47 lines
Quoted 5 lines

reset by peer
19/07/2018 08:52:09 Client 192.168.120.58 gone
19/07/2018 08:52:09 Statistics events Transmit/
RawEquiv ( saved)
19/07/2018 08:52:09 FramebufferUpdate : 3 | 0/ 0 (

0.0%)

Quoted 7 lines

19/07/2018 08:52:09 tight : 1 | 30991/ 3145740
( 99.0%)
19/07/2018 08:52:09 raw : 1 | 16396/ 16396
( 0.0%)
19/07/2018 08:52:09 ZRLE : 2 | 62/ 3932160
(100.0%)
19/07/2018 08:52:09 RichCursor : 3 | 429/ 429

( 0.0%)

Quoted 5 lines

19/07/2018 08:52:09 TOTALS : 10 | 47878/ 7094725
( 99.3%)
19/07/2018 08:52:09 Statistics events Received/
RawEquiv ( saved)
19/07/2018 08:52:09 FramebufferUpdate : 4 | 40/ 40 (

0.0%)

Quoted 1 line

19/07/2018 08:52:09 SetPixelFormat : 2 | 40/ 40 (

0.0%)

Quoted 1 line

19/07/2018 08:52:09 SetEncodings : 3 | 168/ 168

( 0.0%)

Quoted 1 line

19/07/2018 08:52:09 TOTALS : 9 | 248/ 248

( 0.0%)

Quoted 13 lines

What wrong with it?
BTW, vncview download from
https://www.realvnc.com/en/connect/download/viewer/linux/
I also got the same error using Tightvnc viewer Thanks,
xiuzhi
Hi Eddie,
My bmc is AST2400, I modified the aspeed-g4.dtsi(adding gfx:
display@1e6e6000 and video: video@1e700000)
and the aspeed-bmc-opp-xxx.dts (adding &video &vhub) .
An error occured when I executed the following instructions:

Quoted 3 lines
root@zhaoxinc:~# create_usbhid.sh
root@zhaoxinc:~# obmc-ikvm -v /dev/video0 -i /dev/hidg0
[  125.586061] aspeed-video 1e700000.video: timed out on 1st mode

detect

Quoted 1 line
[  125.602732] aspeed-video 1e700000.video: Failed to start video

engine

Quoted 2 lines

failed to open /dev/video0: 62 Timer expired
Need I modify drivers/media/platform/aspeed-video.c or any other

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

files?

Quoted 7 lines

Thanks ,
Xiuzhi

Quoted 3 lines · xiuzhi

Hi Alexander ,Eddie,
I merged the source from

https://gerrit.openbmc-project.xyz/#/c/openbmc/openbmc/+/11500/,and

Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines
Quoted 2 lines

kernel branch video-dev.
How to test the video kvm feature by phosphor-webui or command

Quoted 9 lines
Quoted 5 lines

line?

Quoted 4 lines
Quoted 4 lines
Quoted 4 lines

Hi,

You need to make sure the video device is enabled in your

device-tree

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

for the machine you use... My kernel patch enabled it for our

AST2500

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

witherspoon system. If you're using AST2500 as well, then you

just

Quoted 8 lines
Quoted 8 lines
Quoted 8 lines
Quoted 8 lines

need

Quoted 7 lines

something like:

&video {
     status = "okay";
     memory-region = <&gfx_memory>;
};
Quoted 35 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines

And the virtual USB hub:

&vhub {
     status = "okay";
};

If you're not using AST2500, you'll need more changes to

device-tree.

Quoted 27 lines
Quoted 26 lines
Quoted 26 lines
Quoted 25 lines

Then on the BMC command line:
create_usbhid.sh
obmc-ikvm -v /dev/video0 -i /dev/hidg0
And connect with any VNC client to port 0 of your BMC IP.

Thanks,
Eddie

Quoted 8 lines

Best,
xiuzhi

------------------ 原始邮件 ------------------ *发件人:* "Alexander A. Filippov"<[email protected]>; *发送时间:* 2018年7月25日(星期三) 下午4:56
*收件人:*

"openbmc"<[email protected]>;"xiuzhi"<[email protected]>;

Quoted 6 lines

*主题:* Re: KVM Support?

Hello everybody,

Could you check the size of

build/tmp/deploy/image/<platformname>/fitImage-openbmc-phosphor-initramfs-*.bin?

Quoted 20 lines
Quoted 6 lines
Quoted 6 lines
Quoted 6 lines
Quoted 1 line
Quoted 1 line

If it exceeds 4456448 (0x440000) bytes, this is the problem

described

Quoted 4 lines
Quoted 4 lines

at https://github.com/openbmc/openbmc/issues/3314

In this case you should modify flash partitions layout or

trying to

Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 13 lines
Quoted 13 lines

decrease kernel size.

--
Alexander

Quoted 7 lines · xiuzhi

Hi Eddie,

I read your KVM Support email on mailinglist.

I am going to port the BMC kvm to ast2400 . The u-boot

can not

Quoted 60 lines
Quoted 48 lines
Quoted 48 lines
Quoted 48 lines

load

Quoted 47 lines
Quoted 47 lines

kernel ,the error message read:

Quoted 46 lines

""U-Boot 2016.07 (Jul 23 2018 - 11:11:50 +0000)

DRAM: 240 MiB
WARNING: Caches not enabled
Flash: 32 MiB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   aspeednic#0
Error: aspeednic#0 address not set.

Hit any key to stop autoboot: 0
## Loading kernel from FIT Image at 20080000 ...
Bad FIT kernel image format!
ERROR: can't get kernel image!
ast#

I added config options to defconfig of ast2400 as follows:

CONFIG_MEDIA_SUPPORT=y
CONFIG_MEDIA_CAMERA_SUPPORT=y
CONFIG_MEDIA_SUPPORT=y
CONFIG_MEDIA_CAMERA_SUPPORT=y
# CONFIG_MEDIA_ANALOG_TV_SUPPORT is not set
# CONFIG_MEDIA_DIGITAL_TV_SUPPORT is not set
# CONFIG_MEDIA_RADIO_SUPPORT is not set
# CONFIG_MEDIA_SDR_SUPPORT is not set
# CONFIG_MEDIA_CEC_SUPPORT is not set
# CONFIG_MEDIA_CONTROLLER is not set
CONFIG_RATIONAL=y
CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_V4L2=y
CONFIG_V4L_PLATFORM_DRIVERS=y
CONFIG_VIDEO_ASPEED=y
CONFIG_MEDIA_SUBDRV_AUTOSELECT=y

Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line
Quoted 1 line

Need I modify the aspeed-bmc-opp-palmetto.dts and

aspeed-g4.dtsi?

Quoted 10 lines
Quoted 10 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines
Quoted 9 lines

Can you give me the file list need to modify?

Thanks,

xiuzhi