Re: ACRN issues on NUC
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
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
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, Wang Minxia(Vanda)
From:
acrn-users@... [mailto:acrn-users@...]
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.”
From:
acrn-users@... [mailto:acrn-users@...]
On Behalf Of Tzeng, Tonny
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
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
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
[Announce] ACRN ver0.5 Release Notes
Hi all,
We are pleased to announce version 0.5 release of ACRN. You can see the Release Notes in the website https://projectacrn.github.io/latest/release_notes.html.
To learn more about ACRN: ACRN is a flexible, lightweight reference hypervisor, built with real-time and safety-criticality in mind, optimized to streamline embedded development through an open source platform. Check out the ACRN project portal (https://projectacrn.org/) for more information.
Best regards. Hongbo Tel: +86-21-6116 7445 MP: +86-1364 1793 689 Mail: hongbo.wang@...
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: 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
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, Wang Minxia(Vanda)
From:
acrn-users@... [mailto:acrn-users@...]
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.”
From:
acrn-users@... [mailto:acrn-users@...]
On Behalf Of Tzeng, Tonny
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
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
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN issues on NUC
Wang, Minxia
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, Wang Minxia(Vanda)
From: acrn-users@... [mailto:acrn-users@...]
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.”
From:
acrn-users@... [mailto:acrn-users@...]
On Behalf Of Tzeng, Tonny
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
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
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN issues on NUC
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
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
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@...] 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
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
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN issues on NUC
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
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
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@...] 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
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
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN issues on NUC
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
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@...] 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
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
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN issues on NUC
Ang, Chin Huat <chin.huat.ang@...>
Hi Tonny,
--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
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
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: 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.”
From: acrn-users@...
[mailto:acrn-users@...] On Behalf Of Tzeng, Tonny
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
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
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN issues on NUC
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
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
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
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
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
ACRN Project Technical Community Meeting Minutes - 1/16/2019
Meeting Minutes Archive: https://drive.google.com/drive/u/1/folders/1_XTGu6re3BOQAjtPx636Mz1T5lOy2UWC
ACRN Project TCM - 16th January 2019
Location
Attendees (Total 41, 1/16)
Agenda
Download it from http://projectacrn.org
under Handout
Download foil from ACRN Presentation->ACRN_TCM->WW03’19
3. All: Community open discussion.
4. Next meeting agenda proposal:
Marketing/Events
Resources
===================================
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@...
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN's OTA: it leverage SOS's capability to do OTA
There is a bit more to it as it also needs to: * Configure the boot firmware (EFI) to load 'acrn.efi' (this is manually done today using efibootmgr) * Configure and maintain the 'acrn.conf' file which is the menu entry that loads the right kernel and options for the Service OS. Geoffroy
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN's OTA: it leverage SOS's capability to do OTA
Choong, Yin Thong
Hi, Just FYi.
Clear linux have swupd behavior which can get latest acrn.efi from upstream. Maybe need some extra post process to complete the arcn.efi update by copying the latest into /boot.
Thanks and Regards Choong Yin Thong
From: acrn-users@... [mailto:acrn-users@...]
On Behalf Of Ming Liu
Hi,
Sorry for broadcasting, but FYI..
I have ported ACRN hypervisor/SOS/UOS to yocto, please see my project if you have interest: https://github.com/liuming50/meta-acrn-manifest
With this meta-acrn, there is also a TUF based OTA framework and a meta-updater yocto layer: https://github.com/advancedtelematic/meta-updater.git, that we can implement a OTA solution on top of them, which I am working on. Please join me if you also have interest.
//Ming Liu
Wang, Hongbo <hongbo.wang@...> 於 2019年1月10日 週四 下午12:56寫道:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN's OTA: it leverage SOS's capability to do OTA
Nice job, thanks for sharing Ming Liu!
Are you saying that you already have a basic capability to upgrade the ACRN hypervisor (using OStree)?
Thanks, Geoffroy
From: acrn-users@... [mailto:acrn-users@...]
On Behalf Of Wang, Hongbo
Perfect! I’ll add your BKM into ACRN’s wiki
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 Ming Liu
Hi,
Sorry for broadcasting, but FYI..
I have ported ACRN hypervisor/SOS/UOS to yocto, please see my project if you have interest: https://github.com/liuming50/meta-acrn-manifest
With this meta-acrn, there is also a TUF based OTA framework and a meta-updater yocto layer: https://github.com/advancedtelematic/meta-updater.git, that we can implement a OTA solution on top of them, which I am working on. Please join me if you also have interest.
//Ming Liu
Wang, Hongbo <hongbo.wang@...> 於 2019年1月10日 週四 下午12:56寫道:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN's OTA: it leverage SOS's capability to do OTA
Hi Hongbo,
Thanks for your follow-up on that question. I missed the TCM call but was that question specific to systems running with SBL or UEFI (or both)?
You mention that the hypervisor is “stitched” in the SOS image which makes me believe you are really talking about systems running the SBL boot firmware. Systems running UEFI boot firmware are a bit different and it would be really nice to see a solution to be able to upgrade the hypervisor for both platforms. This is not in place yet for either of those and contributions in that area would be very welcome!
Geoffroy
From: acrn-users@... [mailto:acrn-users@...]
On Behalf Of Wang, Hongbo
Hi all,
One question from ACRN Technical Community Meeting (TCM) this week is whether ACRN support updated feature like OTA. Here’s the feedback from ACRN’s engineering team: right now ACRN hypervisor is stitched (build-in) with SOS image, for example Clear Linux as Service OS, so the ACRN’s update could be done by SOS if SOS has such capability.
Thanks for the questions.
Best regards. Hongbo Tel: +86-21-6116 7445 MP: +86-1364 1793 689 Mail: hongbo.wang@...
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN's OTA: it leverage SOS's capability to do OTA
Perfect! I’ll add your BKM into ACRN’s wiki
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 Ming Liu
Hi,
Sorry for broadcasting, but FYI..
I have ported ACRN hypervisor/SOS/UOS to yocto, please see my project if you have interest: https://github.com/liuming50/meta-acrn-manifest
With this meta-acrn, there is also a TUF based OTA framework and a meta-updater yocto layer: https://github.com/advancedtelematic/meta-updater.git, that we can implement a OTA solution on top of them, which I am working on. Please join me if you also have interest.
//Ming Liu
Wang, Hongbo <hongbo.wang@...> 於 2019年1月10日 週四 下午12:56寫道:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
Re: ACRN's OTA: it leverage SOS's capability to do OTA
Ming Liu
Hi, Sorry for broadcasting, but FYI.. I have ported ACRN hypervisor/SOS/UOS to yocto, please see my project if you have interest: https://github.com/liuming50/meta-acrn-manifest With this meta-acrn, there is also a TUF based OTA framework and a meta-updater yocto layer: https://github.com/advancedtelematic/meta-updater.git, that we can implement a OTA solution on top of them, which I am working on. Please join me if you also have interest. //Ming Liu Wang, Hongbo <hongbo.wang@...> 於 2019年1月10日 週四 下午12:56寫道:
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
ACRN's OTA: it leverage SOS's capability to do OTA
Hi all,
One question from ACRN Technical Community Meeting (TCM) this week is whether ACRN support updated feature like OTA. Here’s the feedback from ACRN’s engineering team: right now ACRN hypervisor is stitched (build-in) with SOS image, for example Clear Linux as Service OS, so the ACRN’s update could be done by SOS if SOS has such capability.
Thanks for the questions.
Best regards. Hongbo Tel: +86-21-6116 7445 MP: +86-1364 1793 689 Mail: hongbo.wang@...
|
||||||||||||||||||||||||
|
||||||||||||||||||||||||
ACRN Project Technical Community Meeting Minutes - 1/9/2019
Wish all you a Happy New Year! Looking forward to your collaboration in ACRN community in 2019!
Meeting Minutes Archives: https://drive.google.com/drive/u/1/folders/1_XTGu6re3BOQAjtPx636Mz1T5lOy2UWC
ACRN Project TCM - 9th January 2019
Location
Agenda
Download foil from ACRN Presentation->ACRN_TCM->WW02’19
Download foil from ACRN Presentation->ACRN_TCM->WW02’19
Marketing/Events
Resources
====================================
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@...
|
||||||||||||||||||||||||
|