|
Invitation - ACRN Virtual Meet-Up Europe 2021
Dear ACRN community,
The ACRN team is hosting a virtual Meet-Up, brought to you by Intel. Please join us to learn more about ACRN, how far it has come over the last three years, and where it is headed. The Meet-Up is intended for attendees with a technical profile (but no prior knowledge on ACRN is required). Dates: 25th and 26th of May 2021 Time: 9AM to 1PM (Central European Time) Here is the link to register for this event: https://plan.seek.intel.com/ACRN-Meet-Up-Europe-REG Agenda Day 1 =========== 9:00 AM: Welcome 9:10 AM: ACRN Introduction and Architecture 9:50 AM: Real-Time Management and Performance Optimization 10:30 AM: Functional Safety Design and Certification Plan 11:10 AM: Break 11:30 AM: Installation and Configuration Introduction 12:10 PM: Enabling ACRN on new Hardware Platforms 12:50 PM: Conclusions 1:00 PM: End of Day 1 Agenda Day 2 =========== 9:00 AM: Welcome 9:10 AM: Orchestration with Libvirt and Kata Container 9:50 AM: Boot process and secure boot 10:30 AM: Community & Development Model 11:10 AM: Break 11:30 AM: Debugging ACRN (inc. tracing & logging) 12:10 PM: Inter-VM communication Introduction 12:50 PM: Conclusions 1:00 PM: End We look forward to seeing you there! Best regards, Geoffroy Senior Technical Marketing Engineer IAGS - System Software Products Tel: +32 (0)3 450 0851 ----------------------------------------------- Intel Corporation NV/SA Kings Square, Veldkant 31 2550 Kontich RPM (Bruxelles) 0415.497.718. Citibank, Brussels, account 570/1031255/09
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
2021 ACRN Project Technical Community Meeting Minutes - WW17'21
Zou, Terry
ACRN Project TCM - 21th Apr 2021
Location Online by Zoom:
https://zoom.com.cn/j/320664063
Attendees (Total 18, 21/04)
Note: If you need to edit this document, please ask for access.
We disabled anonymous editing to keep track of changes and identify who are the owners of the opens and agenda items.
Opens Note: When adding opens or agenda items, please provide details (not
only links), add your name next to the item you have added and specify your expectation from the TCM
Agenda
New configuration system: board/scenario XMLs, and BOARD=xxx/ SCENARIO_FILE.
Special notes of upgrading to v2.4 From Previous Releases.
Download foil from ACRN Presentation->WW17’21
Description: We will briefly introduce TGL NUC 11th
platform and how to enable ACRN v2.4 release on it with demo video, and also external PCIe serial port solution on NUC.
Q&A:
A: Change ‘RAM_SIZE’ in Config Tool, default is 16G, if >16G, you can change in app.py. ‘Hypervisor automatically detects memory config on board’ is also under development.
A: Yes, will upload NUC11TNHi5
config xml in github repo after verification.
A: Additional NVMe M.2 to PCIe converter is just HW connection, no SW/FW impact to PCIe to serial port.
N/A
Project URL:
Technical Mailing list: acrn-dev@...g
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
2021 ACRN Project Technical Community Meeting (2021/1~2021/6): @ Monthly 3rd Wednesday 4PM (China-Shanghai), Wednesday 10AM (Europe-Munich), Tuesday 1AM (US-West Coast)
Zou, Terry
Special Notes: If you have Zoom connection issue by using web browser, please
install & launch Zoom application, manually input the meeting ID (320664063)
to join the Zoom meeting.
Agenda & Archives:
Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices
We invite you to attend a monthly "Technical Community" meeting where we'll meet community members and talk about the ACRN project and plans.
As we explore community interest and involvement opportunities, we'll (re)schedule these meetings at a time convenient to most attendees:
Or visit Github wiki if you can’t access Google doc: https://github.com/projectacrn/acrn-hypervisor/wiki/ACRN-Committee-and-Working-Group-Meetings#technical-community-meetings
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
[Announce] ACRN Open Source Ver2.4 Release Notes
Zou, Terry
Hi all,
We are very pleased to announce Version 2.4 release of ACRN. You can see the release blog from https://projectacrn.org/blog/ and detailed Release Notes in website https://projectacrn.github.io/latest/release_notes/release_notes_2.4.html What’s New in v2.4Extensive work was done to redesign how ACRN configuration is handled, update the build process to use the new configuration system, and update the corresponding documentation. This is a significant change and improvement to how you configure ACRN but also impacts existing projects, as explained in the next section. We’ve also validated the hybrid_rt scenario on the next generation of Intel® Core™ processors (codenamed Elkhart Lake) and enabled software SRAM and cache locking for real time performance on Elkhart Lake. · ACRN Configuration and Build: The following major changes on ACRN configuration and build process have been integrated into v2.4: · Metadata of configuration entries, including documentation and attributes, has been removed from scenario XMLs. · The C sources generated from board and scenario XMLs are no longer maintained in the repository. Instead they’ll be generated as part of the hypervisor build. Users can now find them under configs/ of the build directory. · Kconfig is no longer used for configuration. Related build targets, such as defconfig, now apply to the configuration files in XML. · The make command-line variables BOARD and BOARD_FILE have been unified. Users can now specify BOARD=xxx when invoking make with xxx being either a board name or a (relative or absolute) path to a board XML file. SCENARIO and SCENARIO_FILE have been unified in the same way. For complete instructions to get started with the new build system, refer to Build ACRN From Source. For an introduction on the concepts and workflow of the new configuration mechanism, refer to Introduction to ACRN Configuration. · Document Updates: With the changes to ACRN configuration noted above, we made substantial updates to the ACRN documentation around configuration and options, as listed here: ² Scenario Configuration Options ² Introduction to ACRN Configuration Additional new or updated reference documents are also available, including: ² Getting Started Guide for ACRN Industry Scenario With Ubuntu Service VM ² Configure ACRN Using OpenStack and Libvirt ² Launch Windows as the Guest VM on ACRN
See the v2.4 full release notes and documentation for more information about this release including fixed and known issues. Upgrading to v2.4 From Previous ReleasesWe highly recommended that you follow the instructions below to upgrade to v2.4 from previous ACRN releases. · Additional Dependencies Python version 3.6 or higher is required to build ACRN v2.4. In addition, the following new tools and packages are needed to build ACRN v2.4: $ sudo apt install libxml2-utils xsltproc
$ sudo pip3 install lxml xmlschema
· Configuration File Format Starting with release v2.4, Kconfig is no longer used, and the contents of scenario XML files have been simplified. You need to upgrade your own Kconfig-format files or scenario XML files if you maintain any. For Kconfig-format file, you must translate your configuration to a scenario XML file where all previous Kconfig configuration entries are also available. Refer to Scenario Configuration Options for the full list of settings available in scenario XML files. · New Configuration Options The following element is added to scenario XML files in v2.4: hv.FEATURES.ENFORCE_TURNOFF_AC
· Build Commands We recommend you update the usage of variables BOARD_FILE and SCENARIO_FILE, which are being deprecated, and RELEASE: BOARD_FILE should be replaced with BOARD. You should not specify BOARD and BOARD_FILE at the same time. Similarly, SCENARIO_FILE should be replaced with SCENARIO. The value of RELEASE should be either y (previously was 1) or n (previously was 0). BOARD_FILE and SCENARIO_FILE can still be used but will take effect only if BOARD and SCENARIO are not defined. They will be deprecated in a future release. · Patches on Generated Sources The C files generated from board and scenario XML files have been removed from the repository in v2.4. Instead they will be generated in the build output when building the hypervisor. Typically you should be able to customize your scenario by modifying the scenario XML file rather than the generated files directly. But if that is not possible, you can still register one or more patches that will be applied to the generated files by following the instructions in Makefile Targets for Configuration. Modifying generated files is not a recommended practice. If you find a configuration that is not flexible enough to meet your needs, please let us know by sending mail to the acrn-dev mailing list or submitting a GitHub issue.
Best & Regards Terry
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: some issues when launch debian and windows uos
ZhangShuai
Hi Fuzhong,
The windows uos is works normally after enable "multi-user.target". The reason of this issue is I didn't change the Ubuntu sos to text mode. Thanks. About the GVT parameter, do you mean "-s 2,pci-gvt -G "$2" \"? I attached the scripts, please help to confirm. I have checked the BIOS setting, it's same like the GSG. The ACRN version is V2.3, Industry Scenario. Other questions: 1. How to make VGA and USB controller works again on Ubuntu sos after the windows uos poweroff? 2. launch_xenomai.sh script make the WHL stuck. It didn't happen on the KBL platform. Command : "sudo ./launch_xenomai.sh -f ./preempt-rt-32030.img -k ./linux-4.19.59-xenomai-3.1-acrn+-x86.tar.gz" Best Regards,
On 2021/3/26 am 9:08, Liu, Fuzhong
wrote:
-- Xi'an R&D Center Computerized Numerical Control R&D Dept. Shuai Zhang Tel : 029-84503040-8360 E-mail : zhangshuai@... Web : www.jingdiao.com
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: some issues when launch debian and windows uos
Liu, Fuzhong
Hi ZhangShuai Which codebase are you using for WhiskyLake Platform? Do you follow the GSG to set BIOS: https://projectacrn.github.io/latest/getting-started/rt_industry_ubuntu.html#additional-settings-in-the-service-vm Item 1, please ignore the waring message; Item 2, Do you add GVT parameter in your launch script? GVT-g doesn’t work since v2.1. Please share it to us. Item3, Please enable “multi-user.target” with systemctl set-default multi-user.target in Ubuntu sos.
BR. Fuzhong From: acrn-users@... <acrn-users@...>
On Behalf Of ZhangShuai
updates Change to a WhiskyLake Platform, still have these issues. 2. when launch a uos (debian, ubuntu or clr linux), the uart output : [721704238us][cpu=0][vm0:vcpu0][sev=3][seq=224]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler
3. at the first time of running install_win.sh, got the message like below. I saw the UEFI shell on the HDMI screen, then the WHL restarted. [758442306us][cpu=0][vm0:vcpu0][sev=1][seq=224]:vpci_assign_pcidev 0:14.0 not support FLR or not support PM reset After this time, the system always restarted directly when running install_win.sh. Nothing output on the uart.
Best Regards,
On 2021/3/19
上午10:57, zhangshuai wrote:
-- Xi'an R&D Center Computerized Numerical Control R&D Dept. Shuai Zhang Tel : 029-84503040-8360 E-mail : zhangshuai@... Web : www.jingdiao.com
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: some issues when launch debian and windows uos
ZhangShuai
updates
Change to a WhiskyLake Platform,
still have these issues.
I enabled the serial port of the WHL, got some debug messages of ACRN when launch sos and uos. 1. at acrn startup, the uart output: [11007973us][cpu=0][vm0:vcpu0][sev=2][seq=37]:vpci_write_cfg 0:1c.1 not found! off: 0xdb, val: 0xbf [11018799us][cpu=0][vm0:vcpu0][sev=2][seq=38]:vpci_write_cfg 0:1c.2 not found! off: 0xdb, val: 0xbf [11029675us][cpu=0][vm0:vcpu0][sev=2][seq=39]:vpci_write_cfg 0:1c.3 not found! off: 0xdb, val: 0xbf ...... 2. when launch a uos (debian, ubuntu
or clr linux), the uart output :
[721704238us][cpu=0][vm0:vcpu0][sev=3][seq=224]:ret=-1
hypercall=0x80000080 failed in vmcall_vmexit_handler
[721716301us][cpu=0][vm0:vcpu0][sev=3][seq=225]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler [721727986us][cpu=0][vm0:vcpu0][sev=3][seq=226]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler [721739730us][cpu=0][vm0:vcpu0][sev=3][seq=227]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler [733552988us][cpu=0][vm1:vcpu0][sev=3][seq=230]:vlapic: Start Secondary VCPU1 for VM[1]... 3. at the first time of running
install_win.sh, got the message like below. I saw the UEFI shell
on the HDMI screen, then the WHL restarted.
[758442306us][cpu=0][vm0:vcpu0][sev=1][seq=224]:vpci_assign_pcidev
0:14.0 not support FLR or not support PM reset
[758549509us][cpu=0][vm0:vcpu0][sev=3][seq=225]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler [758575283us][cpu=0][vm0:vcpu0][sev=3][seq=226]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler [758602622us][cpu=0][vm0:vcpu0][sev=3][seq=227]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler [758629819us][cpu=0][vm0:vcpu0][sev=3][seq=228]:ret=-1 hypercall=0x80000080 failed in vmcall_vmexit_handler After this time, the system always
restarted directly when running install_win.sh. Nothing output
on the uart.
Best Regards,
ZhangShuai On 2021/3/19 上午10:57, zhangshuai
wrote:
Hi all, -- Xi'an R&D Center Computerized Numerical Control R&D Dept. Shuai Zhang Tel : 029-84503040-8360 E-mail : zhangshuai@... Web : www.jingdiao.com
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
回复：[acrn-users] 2021 ACRN Project Technical Community Meeting (2021/1~2021/6): @ Monthly 3rd Wednesday 4PM (China-Shanghai), Wednesday 9AM (Europe-London), Tuesday 0AM (US-West Coast),
杰克朱 <zhujun74@...>
好的，Jerry Zou. 我的网上参会信息是来自以下这份邮件。感谢您给予的更正信息。 -------- 原始邮件 -------- 主题：[acrn-users] 2021 ACRN Project Technical Community Meeting (2021/1~2021/6): @ Monthly 3rd Wednesday 4PM (China-Shanghai), Wednesday 9AM (Europe-London), Tuesday 0AM (US-West Coast), 发件人："Zou, Terry" 收件人：acrn-dev@...," acrn-users@..." 抄送："Fang, Peter" ,"Chang, Stanley " ,"Schroeder, Henning " ,"Liu, Junming" ,"Ueda, Kenta" ,"Schweikhardt, Markus " ,"VanCutsem, Geoffroy " ,"Li, Wilson" ,"Liang, Yi" ,"Chen, Gang C" ,"Taylor, Deb" ,"Kim, Dongwon" ,"Kinder, David B"
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
回复：回复：[acrn-users] 2021 ACRN Project Technical Community Meeting Minutes - WW13'21
杰克朱 <zhujun74@...>
谢谢Jerry Zou.原来是这样，但在ACRN主页上的信息应该更正一下了。还有，如果我想线下联系ACRN的开发技术人员交流，可以有联系电话吗？
toggle quoted messageShow quoted text
-------- 原始邮件 -------- 主题：Re: 回复：[acrn-users] 2021 ACRN Project Technical Community Meeting Minutes - WW13'21 发件人："Zou, Terry" 收件人：杰克朱 抄送：acrn-users@...
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: 回复：[acrn-users] 2021 ACRN Project Technical Community Meeting Minutes - WW13'21
Zou, Terry
Hi Jack, ACRN TCM is planned on every 3rd Wednesday (monthly from 2021), 16:00~17:00 afternoon (PRC time). I will re-send TCM meeting-series to you, welcome to join the next session : )
Best & Regards Terry From: acrn-users@... <acrn-users@...>
On Behalf Of ???
你好，
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
回复：[acrn-users] 2021 ACRN Project Technical Community Meeting Minutes - WW13'21
杰克朱 <zhujun74@...>
你好，
toggle quoted messageShow quoted text
。今天我参加11：00～12：00am的网上会议的时候没人么？是由于什么原因吗？ -------- 原始邮件 -------- 主题：[acrn-users] 2021 ACRN Project Technical Community Meeting Minutes - WW13'21 发件人："Zou, Terry" 收件人：acrn-users@...," acrn-dev@..." 抄送：
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
2021 ACRN Project Technical Community Meeting Minutes - WW13'21
Zou, Terry
ACRN Project TCM - 24th Mar 2021
Location Online by Zoom: https://zoom.com.cn/j/320664063
Attendees (Total 16, 24/03)
Note: If you need to edit this document, please ask for access. We disabled anonymous editing to keep track of changes
and identify who are the owners of the opens and agenda items.
Note: When adding opens or agenda items, please provide details (not only links), add your name next to the item you have added
and specify your expectation from the TCM
Agenda
Download foil from ACRN
Presentation->WW13’21
Description: We will briefly introduce key challenges of Real-Time, Latency in industrial usage and typical enhancement methodology in ACRN.
Q&A: IO device performance with VirtIO in post-launched RTVM maybe lower than Pass-through devices in pre-launched RTVM. But pass-through device performance in Post-launched
RTVM is similar to Pre-launched RTVM.
Resources
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
some issues when launch debian and windows uos
ZhangShuai
Hi all,
I build a Ubuntu18.04 SOS on our 7300U board. SCENARIO = industry $ uname -a Linux acrn-Kabylake 5.4.72-PKT-200203T060100Z #2 SMP PREEMPT Mon Mar 8 10:59:26 CST 2021 x86_64 x86_64 x86_64 GNU/Linux $ dmesg | grep ACRN [ 0.000000] Hypervisor detected: ACRN [ 65.293721] ACRNTrace: Initialized acrn trace module with 4 cpu [ 65.293722] ACRN HVLog: no fixed memory reserve for hvlog. $ acrn-dm -v DM version is: 2.3-b6e24ea4-dirty (daily tag:acrn-2020w48.5-180000p), build by acrn@2021-03-08 10:28:57 There are some issues when launch UOS: issue1: The SOS freezes for 60s at startup after the i915.enable_gvt=1 added in 40_customer.  the dmesg file is in attachment. issue2: launch Debian as UOS, warning messages(as follows) keep printing but the UOS works fine. Failed to emulate instruction [mmio address 0xdf57e000, size 4Unhandled memory access to 0xdf57e004 Failed to emulate instruction [mmio address 0xdf57e004, size 4Unhandled memory access to 0xdf57e008 Failed to emulate instruction [mmio address 0xdf57e008, size 4Unhandled memory access to 0xdf57e00c .... issue3: follow the latest document to using_windows_as_uos, Enable the GVT-d GOP Driver. The board often restarts after running the install_win.sh script. have tried 10 times, see UEFI shell only twice, and the rest are restarted directly. finished the windows installation by GVT-d, but never launch WaaG successfully because the board always restart when running launch_win.sh the attachment is the tar of the dmesg files and scripts. Any information, or thoughts would be greatly appreciated. Thanks and Best Regards, ZhangShuai
-- Xi'an R&D Center Computerized Numerical Control R&D Dept. Shuai Zhang Tel : 029-84503040-8360 E-mail : zhangshuai@... Web : www.jingdiao.com
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
2021 ACRN Project Technical Community Meeting (2021/1~2021/6): @ Monthly 3rd Wednesday 4PM (China-Shanghai), Wednesday 9AM (Europe-London), Tuesday 0AM (US-West Coast),
Zou, Terry
Special Notes: If you have Zoom connection issue by using web browser, please
install & launch Zoom application, manually input the meeting ID (320664063)
to join the Zoom meeting.
Agenda & Archives:
Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices
We invite you to attend a monthly "Technical Community" meeting where we'll meet community members and talk about the ACRN project and plans.
As we explore community interest and involvement opportunities, we'll (re)schedule these meetings at a time convenient to most attendees:
Or visit Github wiki if you can’t access Google doc: https://github.com/projectacrn/acrn-hypervisor/wiki/ACRN-Committee-and-Working-Group-Meetings#technical-community-meetings
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Paid ACRN developer research opportunity
[The ACRN mailing list admin has approved this message, posted by an ACRN maintainer.]
I'm looking to do paid interviews with embedded developers and system integration engineers who have completed one or more projects on ACRN, so we can learn about hypervisor usage. My name is Greg Labavitch, and I work at a user-centered research and design company (concreteux.com) that does research with technology professionals to provide input on the usefulness and usability of technical products and tools. I’m asking for one hour of your time for a remote video conference in the first half of March 2021, and we'll give you $150 for your participation. Your input will directly help the ACRN team understand your usage and development experience with ACRN. If you're interested, please fill out this Google Form questionnaire. For questions, please feel free to contact me at greg.labavitch@.... Thank you!
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Running ACRN in Virtualbox on NUC7i7DNH?
Hi Lonnie,
I have never heard of anyone attempting to boot ACRN in a VirtualBox VM… do let us know if you and have any success there! 😉
One other path you could take is to QEMU on Windows and follow this tutorial: https://projectacrn.github.io/latest/tutorials/acrn_on_qemu.html. I don’t have any experience with QEMU on Windows, but assuming it only does the emulation piece, you’d probably also want to use the HAXM driver to expose VT-x (https://github.com/intel/haxm).
Unfortunately, I don’t have any Windows machine other than my official IT machine… and I don’t think my IT department would be too thrilled if I was to try this on it 😊
Cheers, Geoffroy
From: acrn-users@... <acrn-users@...>
On Behalf Of Lonnie Cumberland
Hi All,
I am running my new NUC7i7DNHE that has Windows 10 on it and have installed VirtualBox so that I can use it as a build platform for ACRN in some VM's.
I am wondering if anyone has been able to install and boot up ACRN in a VirtualBox VM with Clear Linux or other?
I have been using these dated ACRN videos as guides while trying to replicate just a basic install and boot up of ACRN to see it in action before wiping my NUC and working from that pathway.
--- ACRN Getting Started and Demo
--- Info on ACRN design
Basically, I would just like to see it run locally, in a VM if possible, before digging heavier into it.
Cheers, Lonnie
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Running ACRN in Virtualbox on NUC7i7DNH?
Lonnie Cumberland <lonnie@...>
Hi All, I am running my new NUC7i7DNHE that has Windows 10 on it and have installed VirtualBox so that I can use it as a build platform for ACRN in some VM's. I am wondering if anyone has been able to install and boot up ACRN in a VirtualBox VM with Clear Linux or other? I have been using these dated ACRN videos as guides while trying to replicate just a basic install and boot up of ACRN to see it in action before wiping my NUC and working from that pathway. --- ACRN Getting Started and Demo --- Info on ACRN design Basically, I would just like to see it run locally, in a VM if possible, before digging heavier into it. Cheers, Lonnie
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Can't enable uart for Ubuntu SOS
Liu, Fuzhong
Hi zhangshuai
toggle quoted messageShow quoted text
Could you please try "make install" instead of copy the grubx64.efi? It works for my setup: root@acrn-OptiPlex-9010:/home/acrn/work/grub-2.04# make install root@acrn-OptiPlex-9010:/home/acrn/work/grub-2.04# grub-install -V grub-install (GRUB) 2.02-2ubuntu8.17 root@acrn-OptiPlex-9010:/home/acrn/work/grub-2.04# reboot root@acrn-OptiPlex-9010:/home/acrn# grub-install -V grub-install (GRUB) 2.04 BR. Fuzhong
-----Original Message-----
From: acrn-users@... <acrn-users@...> On Behalf Of "??????-?????-?? Sent: Thursday, February 4, 2021 5:27 PM To: acrn-users@... Cc: ligang@...; wumengkui@...; lijia@...; hujunke@...; hudongjiang@... Subject: Re: [acrn-users] Can't enable uart for Ubuntu SOS Hi Victor, update the grub2.05 according to this https://projectacrn.github.io/latest/tutorials/using_grub.html?#installing-self-built-grub, copy the grubx64.efi to /boot/efi/EFI/ubuntu . But grub cannot boot ubuntu to startup. Is the file in the wrong place? Thanks and Best Regards, zhangshuai -- Xi'an R&D Center Computerized Numerical Control R&D Dept. Shuai Zhang Tel : 029-84503040-8360 E-mail :zhangshuai@... Web :www.jingdiao.com
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Can't enable uart for Ubuntu SOS
Victor Sun
hi Shuai,
toggle quoted messageShow quoted text
If you follows https://projectacrn.github.io/latest/tutorials/using_grub.html?#installing-self-built-grub then you should not replace grubx64.efi to /boot/efi/EFI/ubuntu since grub-mkimge -p parameter is incorrect. Ubuntu GRUB is built with its own build script and parameters. please put efi application to your "-p" specified folder, (maybe you can try "grub-mkimage -p /EFI/grub ..." to replace your Ubuntu grub efi but I am not sure it can work, depends on your ubuntu version.) BR, Victor
On 2/4/2021 5:27 PM, "西安研发中心-数控研发部-张帅 wrote:
Hi Victor,
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Can't enable uart for Ubuntu SOS
Hi Zhangshuai,
toggle quoted messageShow quoted text
What is your version of Ubuntu? I'm running Ubuntu 20.04 on a machine and did not have to update Grub to install ACRN. This is the right location, do you see the Grub menu at all after updating the Grub binary? If not, can you get to the EFI shell and manually start it from there? Make sure you have secure boot turned off in your bios as well. Back to your question about the UART, can you also try to use the bdf info instead, i.e.: # lspci | grep UART 00:18.0 . Series HSUART Controller #1 (rev 0b) 00:18.1 . Series HSUART Controller #2 (rev 0b) Which translates into uart=bdf@00:18.1 (if you want to use the second one for example). One last thing, make sure you have flow control (HW and SW) turned off in your serial port program (e.g. minicom). Geoffroy
-----Original Message-----
|
|||||||||||||||||||||||||
|
|
