ACRN issues on NUC


chin.huat.ang@...
 

Hi,

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

--Chin Huat


[1] https://projectacrn.github.io/latest/getting-started/apl-nuc.html
[2] https://projectacrn.github.io/latest/hardware.html#intel-kaby-lake-nuc
[3] https://downloadcenter.intel.com/download/28475/BIOS-Update-BNKBL357-86A-?product=98414
[4] https://projectacrn.github.io/latest/getting-started/apl-nuc.html#set-up-a-clear-linux-operating-system
[5] https://projectacrn.github.io/latest/getting-started/apl-nuc.html#add-the-acrn-hypervisor-to-the-efi-partition


Tzeng, Tonny <tonny.tzeng@...>
 

If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See [1]

 

[1] https://github.com/projectacrn/acrn-hypervisor/issues/2076

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 2:46 PM
To: acrn-users@...
Subject: [acrn-users] ACRN issues on NUC

 

Hi,

 

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

 

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

 

--Chin Huat

 

 


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.

 

 

Best regards.

Hongbo

Tel: +86-21-6116 7445

MP: +86-1364 1793 689

Mail: hongbo.wang@...

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Tzeng, Tonny
Sent: Wednesday, January 16, 2019 2:52 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See [1]

 

[1] https://github.com/projectacrn/acrn-hypervisor/issues/2076

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 2:46 PM
To: acrn-users@...
Subject: [acrn-users] ACRN issues on NUC

 

Hi,

 

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

 

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

 

--Chin Huat

 

 


Ang, Chin Huat <chin.huat.ang@...>
 

Hi Tonny,

I'm not sure if this is the same as issue #2076. My NUC has 8GB RAM, the documentation [1] says this has been tested [1]?

--Chin Huat

[1] https://projectacrn.github.io/latest/hardware.html#intel-kaby-lake-nuc


From: acrn-users@... [acrn-users@...] on behalf of Tzeng, Tonny [tonny.tzeng@...]
Sent: Wednesday, January 16, 2019 2:52 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See [1]

 

[1] https://github.com/projectacrn/acrn-hypervisor/issues/2076

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 2:46 PM
To: acrn-users@...
Subject: [acrn-users] ACRN issues on NUC

 

Hi,

 

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

 

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

 

--Chin Huat

 

 


Tzeng, Tonny <tonny.tzeng@...>
 

Hi CH,

 

I had similar issue as yours on my NUC7i5BNH, it has 32GB memory and run well with previous ACRN prebuilt binaries. However, I need to change the default settings to meet the memory size on my NUC, and rebuild the hypervisor to be able to boot to the bootloader (where you see the ACRN boot entry).

 

You may enable the internal UEFI shell and launch the acrn.efi manually from the shell. If the system hangs, most likely it’s the memory issue causing the prebuilt acrn.efi doesn’t work, as the difference between our platforms are memory size. An easy way to verify is to install another 8GB on your NUC and see whether the problem goes away. J

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 3:08 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

Hi Tonny,

 

I'm not sure if this is the same as issue #2076. My NUC has 8GB RAM, the documentation [1] says this has been tested [1]?

 

--Chin Huat

 


From: acrn-users@... [acrn-users@...] on behalf of Tzeng, Tonny [tonny.tzeng@...]
Sent: Wednesday, January 16, 2019 2:52 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See [1]

 

[1] https://github.com/projectacrn/acrn-hypervisor/issues/2076

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 2:46 PM
To: acrn-users@...
Subject: [acrn-users] ACRN issues on NUC

 

Hi,

 

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

 

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

 

--Chin Huat

 

 


Tzeng, Tonny <tonny.tzeng@...>
 

Hi CH,

 

I can replicate the issue by reducing the memory by half on my NUC7i5BNH. It turns out there was a regression while using the prebuilt acrn.efi in CL27210 on NUC7i5BNH. Please try to boot your device with the acrn.efi in CL27230 (i.e. ACRN 0.5), it works on my NUC7i5BNH with 8GB memory. FYI.

 

Regards,

Tonny

 

From: Tzeng, Tonny
Sent: Wednesday, January 16, 2019 3:29 PM
To: acrn-users@...
Subject: RE: [acrn-users] ACRN issues on NUC

 

Hi CH,

 

I had similar issue as yours on my NUC7i5BNH, it has 32GB memory and run well with previous ACRN prebuilt binaries. However, I need to change the default settings to meet the memory size on my NUC, and rebuild the hypervisor to be able to boot to the bootloader (where you see the ACRN boot entry).

 

You may enable the internal UEFI shell and launch the acrn.efi manually from the shell. If the system hangs, most likely it’s the memory issue causing the prebuilt acrn.efi doesn’t work, as the difference between our platforms are memory size. An easy way to verify is to install another 8GB on your NUC and see whether the problem goes away. J

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 3:08 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

Hi Tonny,

 

I'm not sure if this is the same as issue #2076. My NUC has 8GB RAM, the documentation [1] says this has been tested [1]?

 

--Chin Huat

 


From: acrn-users@... [acrn-users@...] on behalf of Tzeng, Tonny [tonny.tzeng@...]
Sent: Wednesday, January 16, 2019 2:52 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See [1]

 

[1] https://github.com/projectacrn/acrn-hypervisor/issues/2076

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 2:46 PM
To: acrn-users@...
Subject: [acrn-users] ACRN issues on NUC

 

Hi,

 

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

 

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

 

--Chin Huat

 

 


Ang, Chin Huat <chin.huat.ang@...>
 

Hi Tonny,

I just tried CL27300 and it's working now. Thanks!

--Chin Huat


From: acrn-users@... [acrn-users@...] on behalf of Tzeng, Tonny [tonny.tzeng@...]
Sent: Thursday, January 17, 2019 8:50 AM
To: 'acrn-users@...'
Subject: Re: [acrn-users] ACRN issues on NUC

Hi CH,

 

I can replicate the issue by reducing the memory by half on my NUC7i5BNH. It turns out there was a regression while using the prebuilt acrn.efi in CL27210 on NUC7i5BNH. Please try to boot your device with the acrn.efi in CL27230 (i.e. ACRN 0.5), it works on my NUC7i5BNH with 8GB memory. FYI.

 

Regards,

Tonny

 

From: Tzeng, Tonny
Sent: Wednesday, January 16, 2019 3:29 PM
To: acrn-users@...
Subject: RE: [acrn-users] ACRN issues on NUC

 

Hi CH,

 

I had similar issue as yours on my NUC7i5BNH, it has 32GB memory and run well with previous ACRN prebuilt binaries. However, I need to change the default settings to meet the memory size on my NUC, and rebuild the hypervisor to be able to boot to the bootloader (where you see the ACRN boot entry).

 

You may enable the internal UEFI shell and launch the acrn.efi manually from the shell. If the system hangs, most likely it’s the memory issue causing the prebuilt acrn.efi doesn’t work, as the difference between our platforms are memory size. An easy way to verify is to install another 8GB on your NUC and see whether the problem goes away. J

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 3:08 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

Hi Tonny,

 

I'm not sure if this is the same as issue #2076. My NUC has 8GB RAM, the documentation [1] says this has been tested [1]?

 

--Chin Huat

 


From: acrn-users@... [acrn-users@...] on behalf of Tzeng, Tonny [tonny.tzeng@...]
Sent: Wednesday, January 16, 2019 2:52 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See [1]

 

[1] https://github.com/projectacrn/acrn-hypervisor/issues/2076

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 2:46 PM
To: acrn-users@...
Subject: [acrn-users] ACRN issues on NUC

 

Hi,

 

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

 

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

 

--Chin Huat

 

 


Wang, Minxia
 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Wang, Hongbo
Sent: Wednesday, January 16, 2019 2:56 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

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.

 

 

Best regards.

Hongbo

Tel: +86-21-6116 7445

MP: +86-1364 1793 689

Mail: hongbo.wang@...

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Tzeng, Tonny
Sent: Wednesday, January 16, 2019 2:52 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See [1]

 

[1] https://github.com/projectacrn/acrn-hypervisor/issues/2076

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 2:46 PM
To: acrn-users@...
Subject: [acrn-users] ACRN issues on NUC

 

Hi,

 

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

 

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

 

--Chin Huat

 

 


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.

 

Thanks,

Geoffroy

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Wang, Minxia
Sent: Thursday, January 17, 2019 3:49 AM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

Now only mentioned in below Q&A shared in wechat.

 

https://mp.weixin.qq.com/s?__biz=MzU5NjQ3MjI0OQ==&mid=2247483886&idx=1&sn=edc7ebca9dac0b1f4acdf76597c70e3e&chksm=fe637938c914f02ef233f50929e09f9e2f4912f04dcef668c947cdfab9d3f602f02c62e7a203&mpshare=1&scene=1&srcid=0111BQtbpCxKsPJrmaM9tLdY&pass_ticket=ze1CuvheXvXyvsjUIK7ZUjnQfd2mIXx5stLELr%2FGDvv3rN0aojo40yagGd3%2B6fqz#rd

 

It will be included in Q&A document planning for v0.6 release.

 

 

Best & Regards,

Wang Minxia(Vanda)

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Wang, Hongbo
Sent: Wednesday, January 16, 2019 2:56 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

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.

 

 

Best regards.

Hongbo

Tel: +86-21-6116 7445

MP: +86-1364 1793 689

Mail: hongbo.wang@...

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Tzeng, Tonny
Sent: Wednesday, January 16, 2019 2:52 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See [1]

 

[1] https://github.com/projectacrn/acrn-hypervisor/issues/2076

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 2:46 PM
To: acrn-users@...
Subject: [acrn-users] ACRN issues on NUC

 

Hi,

 

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

 

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

 

--Chin Huat

 

 


Xie, Nanlin
 

We are scheduled to put one document called Q&A document to locate such issues in v0.6 release. It’s on internal review now and will be online soon.

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Geoffroy Van Cutsem
Sent: Thursday, January 17, 2019 4:35 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

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.

 

Thanks,

Geoffroy

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Wang, Minxia
Sent: Thursday, January 17, 2019 3:49 AM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

Now only mentioned in below Q&A shared in wechat.

 

https://mp.weixin.qq.com/s?__biz=MzU5NjQ3MjI0OQ==&mid=2247483886&idx=1&sn=edc7ebca9dac0b1f4acdf76597c70e3e&chksm=fe637938c914f02ef233f50929e09f9e2f4912f04dcef668c947cdfab9d3f602f02c62e7a203&mpshare=1&scene=1&srcid=0111BQtbpCxKsPJrmaM9tLdY&pass_ticket=ze1CuvheXvXyvsjUIK7ZUjnQfd2mIXx5stLELr%2FGDvv3rN0aojo40yagGd3%2B6fqz#rd

 

It will be included in Q&A document planning for v0.6 release.

 

 

Best & Regards,

Wang Minxia(Vanda)

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Wang, Hongbo
Sent: Wednesday, January 16, 2019 2:56 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

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.

 

 

Best regards.

Hongbo

Tel: +86-21-6116 7445

MP: +86-1364 1793 689

Mail: hongbo.wang@...

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Tzeng, Tonny
Sent: Wednesday, January 16, 2019 2:52 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See [1]

 

[1] https://github.com/projectacrn/acrn-hypervisor/issues/2076

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 2:46 PM
To: acrn-users@...
Subject: [acrn-users] ACRN issues on NUC

 

Hi,

 

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

 

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

 

--Chin Huat

 

 


Geoffroy Van Cutsem
 

OK, thanks!

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Xie, Nanlin
Sent: Thursday, January 17, 2019 3:14 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

We are scheduled to put one document called Q&A document to locate such issues in v0.6 release. It’s on internal review now and will be online soon.

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Geoffroy Van Cutsem
Sent: Thursday, January 17, 2019 4:35 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

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.

 

Thanks,

Geoffroy

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Wang, Minxia
Sent: Thursday, January 17, 2019 3:49 AM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

Now only mentioned in below Q&A shared in wechat.

 

https://mp.weixin.qq.com/s?__biz=MzU5NjQ3MjI0OQ==&mid=2247483886&idx=1&sn=edc7ebca9dac0b1f4acdf76597c70e3e&chksm=fe637938c914f02ef233f50929e09f9e2f4912f04dcef668c947cdfab9d3f602f02c62e7a203&mpshare=1&scene=1&srcid=0111BQtbpCxKsPJrmaM9tLdY&pass_ticket=ze1CuvheXvXyvsjUIK7ZUjnQfd2mIXx5stLELr%2FGDvv3rN0aojo40yagGd3%2B6fqz#rd

 

It will be included in Q&A document planning for v0.6 release.

 

 

Best & Regards,

Wang Minxia(Vanda)

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Wang, Hongbo
Sent: Wednesday, January 16, 2019 2:56 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

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.

 

 

Best regards.

Hongbo

Tel: +86-21-6116 7445

MP: +86-1364 1793 689

Mail: hongbo.wang@...

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Tzeng, Tonny
Sent: Wednesday, January 16, 2019 2:52 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN issues on NUC

 

If your NUC7i5BNH installed 32GB memory, you’d need to rebuild the hypervisor from source. See [1]

 

[1] https://github.com/projectacrn/acrn-hypervisor/issues/2076

 

Regards,

Tonny

 

From: acrn-users@... [mailto:acrn-users@...] On Behalf Of Ang, Chin Huat
Sent: Wednesday, January 16, 2019 2:46 PM
To: acrn-users@...
Subject: [acrn-users] ACRN issues on NUC

 

Hi,

 

I tried the Getting Started guide for Intel NUC [1] on a NUC7i5BNH (Kaby Lake i5-7260U) [2] with the latest BIOS [3], however I'm having issues getting ACRN working on Clear Linux version 27210 (installed using clear-26770-installer.img.xz [4]), and I was hoping if someone can help to confirm the issues below or advice on how to troubleshoot them.

 

In Step 6 [5], 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 [5] in order to get to the ACRN Service OS Boot Menu as shown in Step 6 [5]. 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 [5], unfortunately I'm still seeing the same splash screen freeze/blank screen issue.

 

--Chin Huat