"root@acrn-OptiPlex-5040:~# dmesg |grep ACRN [ 0.878968] ACRNTrace: acrn_trace: not support acrn hypervisor! [ 0.878971] ACRN HVLog: acrn_hvlog: not running under acrn hypervisor!" Looks like the kern

Hi Siming, This is not a topic on the ACRN mail list. You could ask on clear linux community. Regards Yin, Fengwei

Hi Siming, You need to update your launch_hard_rt_vm2.sh: echo ${passthru_vpid["sata"]} > /sys/bus/pci/drivers/pci-stub/new_id echo ${passthru_bdf["sata"]} > /sys/bus/pci/devices/${passthru_bdf["sata"

Hi Siming, So you saw "pci passthru fail" when you use your launch_hard_rt_vm1.sh? Could you please share the whole launch_hard_rt_vm1.sh script? Also the version of acrn hypervisor, acrn-dm and SOS k

Hi Siming, I suppose you need passthru the SATA controller to your second VM. Not using virtio block based /dev/sda. Regards Yin, Fengwei ------------------------------------ On 8/3/20 8:52 AM, siming

Hi Tomasz, Tomasz Bursztyka <tomasz.bursztyka@...> wrote: My understanding is that you want to debug UOS (which is zephyr) itself. There are two thing need check: 1. Whether zephyr could s

Hi Tomasz, Not sure whether you are familiar with EFI shell. If yes, can you try to load acrn.efi from EFI shell? That make sure the ACRN is loaded. Regards Yin, Fengwei

This means you boot sos kernel directly without ACRN. Regards Yin, Fengwei

Hi Steve, "fine" here means the build work or the ACRN serial console also work? Regards Yin, Fengwei

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

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

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 kernel? R

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 console. You

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

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

Hi Steve, Great. Stay healthy! Regards Yin, Fengwei

Hi Steve, I just copied exactly same env as yours. But didn't reproduce the issue as yours. ACRN:\>version HV version 1.5-unstable-2020-03-30 02:50:13-008c35a8 DBG (daily tag: acrn-2020w02.5-140000p)

Hi Steve, Here 008c35a8 is the base commit your changes based on. I checked the vUART definition for SOS with this base commit checked out. It's like: .vuart[0] = { .type = VUART_LEGACY_PIO, .addr.por

Hi Steve, ACRN will print the version info during system boot phase. Just capture the serial port log when boot the system with ACRN. Regards Yin, Fengwei

Hi Steve, OK. Can you check the version output of your ACRN? So we could know which git commit is based on. So the HV serial port is from here: IO port serial with 0x3f8 as base IO port. Regards Yin,