Hi Geoffroy, Container build works fine. Cheers Steve. -- Engineering Director IOTech Systems Ltd.

Hi steve, You’re hitting this issue: https://github.com/projectacrn/acrn-hypervisor/issues/4560 Can you try with the acrn/clearlinux-acrn-builder:latest Docker container (from Docker Hub) as

Hi Steve, Please check my comments below, thanks!

Hi Geoffroy, One step forward, one step back. Deleted the build directories and re-built, but now get a build failure: make[3]: Entering directory

Hi Steve, Could it be that you have a build/ folder under hypervisor? This could cause the problem (this is the problem I had hit previously) If you do, just delete it and re-run the command

Still the problem that if I build with: make all BOARD=nuc7i7dnb SCENARIO=industry RELEASE=0 Build summary says: BOARD = nuc7i7dnb SCENARIO = sdc -- Engineering Director IOTech Systems Ltd.

Hi Steve, Yes. Without this "RELEASE=0", release version ACRN is built and the serial console is disabled. Regards Yin, Fengwei

No I didn't set RELEASE=0 when I rebuild acrn, guess I should of ?-- Engineering Director IOTech Systems Ltd.

Hi Steve, OK. The ACRN has no serial console. And the system could boot actually. Right? Did you have RELEASE=0 as one parameter when you build ACRN? Regards Yin, Fengwei

All I get is: EOSO This is a GtkTerm serial console. -- Engineering Director IOTech Systems Ltd.

Hi Steve, From the kernel, the SOS serial console is using ttyS0: console=ttyS0,115200n8 And it looks like everything is fine from the dmesg output. So which serial port is broken? ACRN? SOS

Have attached dmesg log. Actually looks like ttyS0 is using 0x3f8: # dmesg | grep tty [ 0.000000] Command line: initrd=\EFI\org.clearlinux\freestanding-00-intel-ucode.cpio

Hi Steve, Does ACRN have no serial output or SOS have no serial output? This is for ttyS1. I believe this is a virtual UART emluated by ACRN hypervisor. I suppose it's not for SOS serial

Just a quick update, decided to update to 1.6 release and follow the "out-of-the-box" instructions for the Industry scenario. Everything basically looks good, installed SOS and verified can launch

Hi all, We are very pleased to announceVersion 1.6 release of ACRN. You can see the release blog from https://projectacrn.org/blog/ and detailed Release Notes in website

Hi Nanlin, What Geoff talked about was the issue that ACRN could build without any issue. But the generated binary can't work actually. Will sync with you. Regards Yin, Fengwei

We have one new PR that fix build issue, please refer to PR link: https://github.com/projectacrn/acrn-hypervisor/pull/4534, hope this will fix all build unclear issues. We also provided one docker

ACRN Project TCM - 1st Apr 2020 Location Online by Zoom: https://zoom.com.cn/j/320664063 Attendees (Total 42, 1/4) Note: If need to edit this document, please ask for access. Wedisabled anonymous

Hi Geoff, I was not aware of this documentation issue. Add Nanlin. Basically, there shouldn't cause any difference if we use same Docker build env. Regards Yin, Fengwei