This change update the interrupt from edge triggered to low level triggered. Which is unusual case. Is it possible that this is related with workaround in linux kernel ioapic for version 0x11? Regards

Yes. It's not related with IOAPIC workaround. Here is what I got from SOS: ^M[ 0.041021] ioapic_set_affinity: yfw: eu.w1: 0x931, eu.w2: 0x1000000^M ^M[ 0.041085] ioapic_set_affinity: yfw: eu.w1: 0x930

Yes. This log is showed because the hv logging/tracing has problem. It doesn't impact the VM booting. This log shows the hvlog device is not initialized successfully. Can you share the your whole SOS

Hi Ross, Could you please share the platform you are using? Regards Yin, Fengwei

I meant the hardware platform? Is it MRB, UP2 or NUC? Regards Yin, Fengwei

You need to update the SOS rootfs to latest one. There is iasl update which has more strict rules. We update the ACPI table in DM which needs latest iasl. Regards Yin, Fengwei

This error is related with new version iasl tool which has more strict check to align with ACPI 6.x. So we update the ACPI table definition in acrn-dm and the change breaks old iasl tool. Ross, Could

This log means the UOS kernel hang at very early kernel boot stage. Do you have HV console work or not? Regards Yin, Fengwei

Hi Kris, What's the dm options you are using to run your preempt-rt kernel? What if you add "earlyprintk=ttyS0" to your kernel command and see what we could get from early console? Regards Yin, Fengwe

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

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 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, 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 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, 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, 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, I would like to check: What's the latest status for your new board enabling? Regards Yin, Fengwei

OK. Thanks for the information. Regards Yin, Fengwei

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

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,