Hi Steve, I tried same thing on my env. Everything works fine. Here is the ttySx info in SOS: [ 0.680315] 00:01: ttyS0 at I/O 0x3f8 (irq = 4, base_baud = 115200) is a 16550A [ 0.938131] serial8250: tt

Hi Steve, Checking VM0 (which is SOS) UART definition in Industry scenario: .vuart[0] = { .type = VUART_LEGACY_PIO, .addr.port_base = SOS_COM1_BASE, .irq = SOS_COM1_IRQ, }, and hypervisor/arch/x86/con

Hi Steve, We could see here: [ 3.608930] pnp 00:02: [dma 0 disabled] [ 3.612858] pnp 00:02: Plug and Play ACPI device, IDs PNP0501 (active) [ 4.384915] 00:02: ttyS0 at I/O 0x3f8 (irq = 4, base_baud =

Hi Steve, It looks like the physical UART is used by HV and SOS at the same time. Per my experience, it's not possible if the UART port is legacy UART. Could you please ssh to your SOS and dump the dm

I highly suspect this endless "Starting VCPU" thing is not from SOS kernel. It's more like from BIOS. It could be related with some BIOS setting. I suggest checking the BIOS setting and disable mwait

Fixing patch was sent to acrn-dev mail list: https://lists.projectacrn.org/g/acrn-dev/topic/patch_makefile_disable/69659519?p=,,,20,0,0,0::recentpostdate%2Fsticky,,,20,2,0,69659519 Regards Yin, Fengwe

The kernel also hit same issue and it disabled the -fcf-protection if the -mindirect-branch is enabled (for retpoline): https://lkml.org/lkml/2019/7/9/641 I will submit a patch accordingly. Regards Yi

Hi Steve, The default way is change it through "make menuconfig" command and rebuild the ACRN. Changing Kconfig is kind of hack here. For default value, we need trade off like whether there are many s

Hi Steve, The easiest way to try is change the file: hypervisor/arch/x86/Kconfig which has: config MAX_MSIX_TABLE_NUM int "Maximum number of MSI-X tables per device" range 1 2048 default 16 ---> 64 Yo

Hi Osselton, It looks like there is one PCI device in your system which has more than 16 MSIX table. Can you boot to native linux and dump the MSI table of each PCI devices on your board? Regards Yin,

Hi Alfonso, It's related with iasl in your SOS. We have constrain for iasl version. Regards Yin, Fengwei

OK. Thanks for the information. Regards Yin, Fengwei

Hi Dubravko, I would like to check: What's the latest status for your new board enabling? Regards Yin, Fengwei

Hi Dubravko, For SOS kernel, I suppose you could build it based on our acrn-kernel with igb enabled. It looks like the serial port is a little bit mess. From dmesg_nohv.log, we could see following ser

Hi Dubravko, The UP2 board uses realtek network controller. I believe the reason that your network can't work is the network controller is not enabled in SOS kernel. Could you please find out the netw

Hi Dubravko, I only see following message from your sos kernel log: [ 1.200862] ixgbevf: Intel(R) 10 Gigabit PCI Express Virtual Function Network Driver - version 4.1.0-k [ 1.201695] ixgbevf: Copyrigh

Hi Dubravko, Which ttyS is used for console depends on your hardware design. You need to check with your hardware engineer to figure out which ttyS is used for console. If you are using the UP2 config

Hi Conghui, Yes. Emulated ttyS0 and physical ttyS1 share same irq. But there is no user of ttyS1. we can't see ttyS0/ttyS1 share irq4 in interrupt dump. But as Anthony said, the emulated ttyS0 share i

Hi Dubravko, We checked the log you shared and didn't see anything unusual. We had one issue which could make serial console use polling mode. I suspected you hit that issue. But from the interrupt in

Hi, Could you share: 1. ACRN last git commit hash 2. dmesg output in your SOS 3. the output of cat /proc/interrupt in your SOS Regards Yin, Fengwei