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 ||

Hi Alfonso, #1 Did you calibrate the zephyr clock rate? I am not an expert on Zephyr, as I known, clock calibration is needed in Zephyr. #2 Echo to Geoffroy, heavy workloads on SOS may have

It turns out that disabling Intel Turbo Boost in the BIOS makes the times spent in the calculation on Zephyr almost constant regardless of the load on the SOS. Which makes sense after reading that

Hi Geoffroy, I have tried with the new script, and I think it helps a bit, although it does not remove completely the increment in time when something is running in the SOS. But it is a bit difficult

Hi Alfonso, I’m assuming you have been using the standard launch script (from /usr/share/acrn/samples/nuc/launch_zephyr.sh) to test your Zephyr app. If so, can you try to use this script instead

Hi Alfonso, My best guess as to what’s happening is that there is some contention between the Service VM and the Zephyr VM to use the cache, Zephyr would typically stay in cache but now that