One more thing you may try: add maxcpus=1 to acrn.conf options, so we can skip the SIPI issue and see how it goes.

Hi Dubravko, 1) Enable X2APIC from guest Linux Actually ACRN checks X2APIC capability and it goes panic w/o it. So the host CPUID must have X2APIC support. We met one case where the BIOS DMAR

Hi Dubravko, With my acrn.efi, it switches to guest console by default. Does it switch back to ACRN console by pressing "Ctrl + Space"? The logs show that X2APIC is not enabled by Linux. Is it

Hi Zide, I've checked all the menus and settings in our BIOS, unfortunately I couldn't find anything that looks like the mentioned setting or similar or related to it. We are using coreboot, built

Hi Dubravko, In the meantime, is there something like "AP Thread Idle Manner" in your BIOS? And changing its setting makes any difference? Best Regards, Zide

Not sure why there is no kernel logs come out from serial console. I tried the acrn.efi/bzImage I sent to you, along with the bootargs in your acrn.conf, I was able to see that Linux logs started

Hello, Please find attached the log file and my acrn.conf. My old BIOS didn't have any settings related to Mwait, so I've installed newer BIOS which has "Monitor Mwait Enable" and I've ensured it's

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

Hi Dubravko, "Spurious vector" could because of external interrupts not registered in hypervisor. This may not be an issue and can be ignored for now. For the repeating "Starting VCPU 3" issue, it

Hi Zide, The full log is below, with some additional /* comments */. I've noticed now that ACRN console prompt does appear, but it is unusable due to all the debug messages. ACRN

Hi Dubravko, Is it possible to post the full log here? Thanks, Zide

Hi Zide, Your instructions were clear, unfortunately I'm still having issues. I have followed the instructions from https://projectacrn.github.io/latest/tutorials/kbl-nuc-sdc.html, and first upgraded

<No topic for this week, let’s skip for 2/12> Project ACRN: A flexible, light-weight, opensource reference hypervisor for IoT devices https://projectacrn.org ||

Hi Dubravko, If you see endless vmexit messages, it's possibly that you have successfully loaded the guest kernel. You may remove the vmexit logs by configuring CONFIG_CONSOLE_LOGLEVEL_DEFAULT to

Hi Zide, You were right again, I don't know how it happened but my MAX_PCPU_NUM was set to 3, while there are 4 CPUs. MADT and DMAR tables seem to be correct. I'm using acrn.efi, RELOC is enabled. Now

Hi Dubravko, Did you boot ACRN from acrn.efi (UEFI) or acrn.bin (SBL), or acrn.32.out (Grub)? RELOC is enabled for acrn.efi, but not others. For the init_percpu_lapic_init() issue, it's highly

Hi Zide, Thank you very much, you were right. I've had RELOC already enabled, but apparently one also need to have CONFIG_HV_RAM_START 2MB aligned. I've set it to 0x1400 0000 and now my hypervisor

Hi Dubravko, Host MMU page size is 2MB in ACRN hypervisor. It seems to me that the direct cause for crash could be CONFIG_HV_RAM_START(0x13151000) is not 2MB aligned. Did you disable relocation

Hello, My schedule finally allows me to continue working on getting ACRN to work on our board. I have downloaded the newest version few days ago, added a configuration for our board, used the

<Detailed calendar will be published1 week before meeting> Project ACRN: A flexible, light-weight, opensource reference hypervisor for IoT devices https://projectacrn.org ||