Re: ACRN issues on NUC
Geoffroy Van Cutsem
I’m not able to find the info on that page (and I’m sure the fact I can’t read Chinese is not helping me J). If it’s a simple and short explanation, we can add that to our Getting Started Guide as a new paragraph. If it’s more complicated than that, then we should think about having a dedicated tutorial on the topic.
From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Wang, Minxia
Sent: Thursday, January 17, 2019 3:49 AM
Subject: Re: [acrn-users] ACRN issues on NUC
Now only mentioned in below Q&A shared in wechat.
It will be included in Q&A document planning for v0.6 release.
Best & Regards,
On Behalf Of Wang, Hongbo
To Nanlin and Minxia,
Based on the description, have we documented the kconfig change in any document to support 32G?
“Try to modify 4 lines of content in the file(arch/x86/Kconfig), modify default value from 16G to 32G,and add 64M size for acrn hypervisor. the acrn.efi is loading success and the system started successfully.”
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
On Behalf Of Tzeng, Tonny
If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See 
On Behalf Of Ang, Chin Huat
I tried the Getting Started guide for Intel NUC  on a NUC7i5BNH (Kaby Lake i5-7260U)  with the latest BIOS , however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz ), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.
In Step 6 , rebooting the NUC seems to cause the NUC to freeze at the splash screen. Selecting "ACRN" from the F10 Boot Menu only shows a blank screen.
I had to undo Step 3  in order to get to the ACRN Service OS Boot Menu as shown in Step 6 . I'm able to boot "The ACRN Service OS", although "dmesg | grep -i acrn" reported:
[ 0.624715] acrngt found
[ 0.715568] ACRNTrace: acrn_trace: not support acrn hypervisor!
[ 0.715983] ACRN HVLog: acrn_hvlog_init
[ 0.717541] ACRN HVLog: Failed to setup acrn_hvlog_cur_0, errno -19
[ 1.914477] IPv6: ADDRCONF(NETDEV_UP): acrn-br0: link is not ready
[ 1.917454] acrn-br0: port 1(acrn_tap0) entered blocking state
[ 1.919393] acrn-br0: port 1(acrn_tap0) entered disabled state
[ 1.921345] device acrn_tap0 entered promiscuous mode
[ 1.925281] IPv6: ADDRCONF(NETDEV_UP): acrn_tap0: link is not ready
[ 2.185910] acrn-br0: port 2(eno1) entered blocking state
[ 2.186331] acrn-br0: port 2(eno1) entered disabled state
[ 2.401027] acrn-br0: port 2(eno1) entered blocking state
[ 2.401427] acrn-br0: port 2(eno1) entered forwarding state
[ 2.402109] IPv6: ADDRCONF(NETDEV_CHANGE): acrn-br0: link becomes ready
[ 2.904381] acrn-br0: port 2(eno1) entered disabled state
[ 5.588074] acrn-br0: port 2(eno1) entered blocking state
[ 5.588470] acrn-br0: port 2(eno1) entered forwarding state
[ 964.771971] acrn-br0: port 2(eno1) entered disabled state
[ 969.618340] acrn-br0: port 2(eno1) entered blocking state
[ 969.619649] acrn-br0: port 2(eno1) entered forwarding state
The kernel info as reported by "uname -a":
Linux clr-575a8d97bf9f40caad9b8c3244748f08 4.19.8-1901111952.iot-lts2018-sos #1 SMP PREEMPT Sat Jan 12 04:05:35 UTC 2019 x86_64 GNU/Linux
I've also tried to rollback to Clear Linux version 26770 and reapplied all the steps , unfortunately I'm still seeing the same splash screen freeze/blank screen issue.