Re: Getting ACRN to work


Chen, 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 right after VM0 is launched:

[6931479us][cpu=0][(null)][sev=2][seq=25]:Start VM id: 0 name: ACRN SOS VM
[6938866us][cpu=0][vm0:vcpu0][sev=5][seq=26]:VM 0 Starting VCPU 0
[6945396us][cpu=0][vm0:vcpu0][sev=5][seq=27]:VM 0 VCPU 0 successfully launched
early console in extract_kernel
input_data: 0x00000000025403b1
input_len: 0x0000000000c2416d
output: 0x0000000001000000
output_len: 0x0000000002132574
kernel_total_size: 0x0000000001e2c000
trampoline_32bit: 0x000000000008c000
booted via startup_64()
Physical KASLR using RDRAND RDTSC...
Virtual KASLR using RDRAND RDTSC...

Decompressing Linux... og=2M@0x1FE00000 i915.avail_planes_per_pipe=0x01010F i915.domain_plane_owners=0x011111110000 i915.enable_guc=0 i915.enable_gvt=1 i915.nuclear_pageflip=1 ignore_loglevel init=/usr/lib/systemd/systemd-bootchart intel_iommu=igfx_off memmap=2M$0x1FE00000 no_timer_check no_timer_check noreplace-smp rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs rootwait tsc=reliable rw ignore_loglevel earlyprintk=serial,ttyS0,115200n8,keep
[ 0.000000] ------------[ cut here ]------------
[ 0.000000] XSAVE consistency problem, dumping leaves
[ 0.000000] WARNING: CPU: 0 PID: 0 at arch/x86/kernel/fpu/xstate.c:614 fpu__init_system_xstate+0x464/0x868
[ 0.000000] Modules linked in:
...

[14737156us][cpu=0][vm0:vcpu0][sev=3][seq=30]:vlapic: Start Secondary VCPU1 for VM[0]...
[14745830us][cpu=1][vm0:vcpu1][sev=5][seq=31]:VM 0 Starting VCPU 1
[14761070us][cpu=0][vm0:vcpu0][sev=3][seq=32]:vlapic: Start Secondary VCPU2 for VM[0]...

Best Regards,
Zide

On 2/12/20 8:02 AM, Dubravko Moravski | Exor Embedded S.r.l. wrote:
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 set to "Disabled". Changing the BIOS seems to have also changed some data in logs, but the overall behavior is the same.
New acrn.efi seems to work reasonably well. Our custom board is obviously specific, but in general it is similar to reference Leaf Hill CRB.
After the last printout from the log, everything stops working (there is nothing on the screen attached to the board and the keyboard doesn't do anything; also typing in the serial terminal doesn't do anything).
Best regards,
Dubravko
*Dubravko Moravski*
/SW engineering/
*Exor Embedded S.r.l.*
p: +38 512455659 <tel:+38 512455659>  m:+38 5915402413 <tel:+38 5915402413>
a: Slavonska avenija, 50, Zagreb, Croatia, 10000
w: exorint.com <https://exorint.com/>

 Prima di stampare pensa ai costi ambientali. Please consider the environment before printing this email.
Privacy <https://www.exorint.com/it/privacy>
--------------------------------------------------------------------------------------------------------------------------
*From:* acrn-users@... <acrn-users@...> on behalf of Chen, Zide via Lists.Projectacrn.Org <zide.chen=intel.com@...>
*Sent:* Wednesday, February 12, 2020 1:04 AM
*To:* acrn-users@... <acrn-users@...>
*Subject:* Re: [acrn-users] Getting ACRN to work
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 seems some thing related to SIPI delivery. But nothing is obvious to me and
need to debug it.
I built a Clear Linux kernel with additional logs showing how it's bringing up APs. Could you please try the attached
bzImage?
Also please enable early printk by adding "ignore_loglevel earlyprintk=serial,ttyS0,115200n8,keep" to the options in
acrn.conf; And use the attached acrn.efi (I enabled some additional logs and print out Linux logs even before ACRN console
is operational). If acrn.efi doesn't boot, which is highly possibly since it's not built against your custom board, you
may need to apply the attached patch to ACRN hypervisor.
Hopefully the full logs can give us some clues.
Best Regards,
Zide
zide.chen@...

Join acrn-users@lists.projectacrn.org to automatically receive all group messages.