|
Re: ACRN-Hypervisor build fail
shibi590268@...
Attaching the xml files
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
ACRN-Hypervisor build fail
Hello,
I am facing the build failure when trying to build acrn-hypervisor. I have generated the board.xml and scenario.xml file as given in the procedure. I am using kontron board which belongs to intel apollo lake APL0. I am attaching the board.xml file and scenaio xml file. Previously, i have removed those lines to suppress the warnings and built the acrn and kernel. User vm is able to launch and worked perfectly. My question is are these configurations mandatory for running the user vm without any problem in future. If not, how to fix them. Traceback (most recent call last):
File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/main.py", line 41, in
main(args)
File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/main.py", line 31, in main
module.fn(board_etree, scenario_etree, allocation_etree)
File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/bdf.py", line 149, in fn
native_used = get_devs_bdf_native(board_etree)
File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/bdf.py", line 89, in get_devs_bdf_native
dev_list.append(lib.lib.BusDevFunc(bus = bus, dev = dev, func = func))
File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/lib/lib.py", line 46, in __init__
raise ValueError(f"Invalid function number (0 ~ 7): {self.func:#x}")
ValueError: Invalid function number (0 ~ 7): 0xff
cp acrnlog.service /home/shibi/acrn-work/acrn-hypervisor/build/misc/debug_tools/acrnlog.service
make[2]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/misc/debug_tools/acrn_log'
make[2]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/misc/debug_tools/acrn_trace'
make[1]: *** No rule to make target '/home/shibi/acrn-work/acrn-hypervisor/build/hypervisor/configs/allocation.xml', needed by '/home/shibi/acrn-work/acrn-hypervisor/build/hypervisor/configs/unified.xml'. Stop.
make[1]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/hypervisor'
Makefile:116: recipe for target 'hvdefconfig' failed
make: *** [hvdefconfig] Error 2
make: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/misc/debug_tools/acrn_crashlog/common'
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
Glad you were able to fix it! Can you tell me what fixed it? I'm specifically interested in there are things we need to update/improve/modify in our documentation.
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
shibi590268@...
I have fixed this issue. Now, the rt patched ubuntu runs successfully in acrn hypervisor
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Intel NUC APL gets powered off when launching uos with gpu passthrough
Geoffroy,
I have attached the service VM kernel debug messages when launching the user vm with GPU passthrough. There is a kernel panic occurring and then the device reboots. I hope this will help identify the root cause. Please check the logs and reply.
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
shibi590268@...
I installed an ubuntu os inside qemu as given in running ubuntu as user vm. I chose OVFM boot loader in qemu. After installation I downloaded the Linux kernel and rt patch, compiled and installed. After reboot rt patched kernel is loaded successfully in qemu. Then, I converted the qcow2 to img. I tried that also by creating another instance in qemu and using the generated image. It loaded successfully. I am facing the issue when using the same image in launch script.
I will update the messages from ACRN console tomorrow.
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
Can you tell me how you installed the RT kernel inside the VM?
Do you have a serial port on your system running ACRN? If so, I would like to see the output from there.
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
shibi590268@...
Geoffroy,
Yeah I am using the same launch script.
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
Are you using the same launch script when you can successfully launch the standard User VM?
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
shibi590268@...
Hello Geoffroy,
I am trying to run Ubuntu with RT patch applied. I followed https://projectacrn.github.io/2.0/tutorials/running_ubun_as_user_vm.html for converting qemu image to img with 20GB as disk space. The user vm runs as expected. But I want to apply RT patch so i applied rt from inside qemu. It boots up properly inside qemu. Then, i converted the rt patched qcow2 image to img to use it with user vm. If i launch the launch script, it loads. But i don't get the login prompt even after a long time. Is there any reference available for using RT patched Ubuntu Os as uservm?
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Has ACRN got the SIL 3 IEC 61508 certification?
shibi590268@...
Zou,
Thanks for the update.
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Has ACRN got the SIL 3 IEC 61508 certification?
Zou, Terry
Yes, for Functional Safety certification, ACRN v1.4 release already received IEC61508 Safety Integrity Level 3(SIL3) certification on 2021-09-06. There is WeChat blog with cert paper for your information: https://mp.weixin.qq.com/s/Qd6aluIZ7LczV4n9I2lKtA For ARM platform, there is no support for ARM-based processors at this stage. but ACRN is designed to support multi-architectures, so welcome anybody from community to discuss and contribute for ARM support, thanks.
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Has ACRN got the SIL 3 IEC 61508 certification?
shibi590268@...
Hello All,
I got to know that the ACRN hypervisor is on track to receive the functional safety certification. Please provide the following information: 1. Has it been received or yet to receive? If it has not been received yet when is expected to receive? 2. When are the arm platforms expected to receive the support for the ACRN hypervisor? We would like to evaluate it for a functional safety application. "IEC 61508 is considered as the “Golden Standard” in the functional safety industry. ACRN is on track to receive the final functional safety certification by the end of 2020."
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Not all RAM usable in ACRN user VM
Liu, Fuzhong
Hi Christoph Do you re-generate the board.xml and scenario.xml after adding two more 16 GB bars? Please check following setting in scenario.xml:
<PLATFORM_RAM_SIZE>0x400000000</PLATFORM_RAM_SIZE>
This value is for 16G memory, please update it to 0x900000000 and build ACRN again.
Thanks!
BR. Fuzhong
From: acrn-users@... <acrn-users@...>
On Behalf Of c.susen@...
Sent: Thursday, February 17, 2022 12:03 AM To: acrn-users@... Subject: [acrn-users] Not all RAM usable in ACRN user VM
Hi everyone,
*-bank:0 description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns) product: HMA851U6CJR6N-VK vendor: Hynix Semiconductor (Hyundai Electronics) physical id: 0 serial: 2E9F46C3 slot: DIMM1 size: 4GiB width: 64 bits clock: 2666MHz (0.4ns) *-bank:1 description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns) product: HMA851U6CJR6N-VK vendor: Hynix Semiconductor (Hyundai Electronics) physical id: 1 serial: 2E9F47C5 slot: DIMM2 size: 4GiB width: 64 bits clock: 2666MHz (0.4ns) *-bank:2 description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns) product: 9905734-073.A00G vendor: AMD physical id: 2 serial: 2AAB4317 slot: DIMM3 size: 16GiB width: 64 bits clock: 2666MHz (0.4ns) *-bank:3 description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns) product: 9905734-073.A00G vendor: AMD physical id: 3 serial: F36B433B slot: DIMM4 size: 16GiB width: 64 bits clock: 2666MHz (0.4ns)
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Not all RAM usable in ACRN user VM
c.susen@...
Hi everyone,
I am probably making some kind of stupid mistake but cannot figure out the problem. Therefore, I would really appreciate if someone could give me a hint on how to proceed. I upgraded the PC that I use to run the ACRN hypervisor from 8 GB of RAM to 40 GB of RAM by adding two 16 GB bars (previously I had two 4 GB bars). When I use the generic Ubuntu kernel, everything works without problems and the memory is recognized and usable. However, when I use the ACRN kernel (version 2.6), and run the "free" command, only 16 GB of the memory are shown. When running "sudo lshw | grep -A 9 bank", all four bars are shown correctly as you can see below. *-bank:0
description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns)
product: HMA851U6CJR6N-VK
vendor: Hynix Semiconductor (Hyundai Electronics)
physical id: 0
serial: 2E9F46C3
slot: DIMM1
size: 4GiB
width: 64 bits
clock: 2666MHz (0.4ns)
*-bank:1
description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns)
product: HMA851U6CJR6N-VK
vendor: Hynix Semiconductor (Hyundai Electronics)
physical id: 1
serial: 2E9F47C5
slot: DIMM2
size: 4GiB
width: 64 bits
clock: 2666MHz (0.4ns)
*-bank:2
description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns)
product: 9905734-073.A00G
vendor: AMD
physical id: 2
serial: 2AAB4317
slot: DIMM3
size: 16GiB
width: 64 bits
clock: 2666MHz (0.4ns)
*-bank:3
description: DIMM DDR4 Synchronous 2666 MHz (0.4 ns)
product: 9905734-073.A00G
vendor: AMD
physical id: 3
serial: F36B433B
slot: DIMM4
size: 16GiB
width: 64 bits
clock: 2666MHz (0.4ns)
So far I only created a new board configuration file and recompiled kernel and hypervisor. Apart from that, I did not make any change to the system and installation except for adding the two RAM bars. Thanks in advance for your help! Best regards, Christoph
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Intel NUC APL gets powered off when launching uos with gpu passthrough
Does that mean this system is completely unusable now?
Have you tried physically pulling the power cable from the device and waiting at least a few seconds before plugging it back in? I'm not sure how to go about resolving this one to be honest with you, Apollo Lake is not a platform that we focus on anymore, we are not testing it at all at this point. A few pointers still, based on inspection of the launch script you attached in the first email: - You can remove the " --pm_notify_channel ioc \" line, you don't have the ioc device on the NUC - I'm curious about this virtio-blk that is mapped to /mnt, what's the purpose of this? Thanks, Geoffroy
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
True, and the longer answer is (and I will also invite all the engineers and architects to correct me if and where needed): you don’t need those because the Service VM is not involved in the scheduling of the RTVM, it is running directly on dedicated CPU cores and that configuration is static. Even the interrupt distribution is passed-through (using the –lapic_pt flag).
I would also add that there are many parameters that should be taken into account when you design a system using RTVMs, we have a number of recommendations and tips listed here [1] but it is not exhaustive and we always, of course, recommend that you do your own testing and analysis of your systems when it’s running.
[1] https://projectacrn.github.io/latest/tutorials/rtvm_performance_tips.html
Cheers, Geoffroy
From: acrn-users@... <acrn-users@...>
On Behalf Of Liu, Fuzhong
Sent: Tuesday, February 15, 2022 1:01 pm To: acrn-users@... Subject: Re: [acrn-users] Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
The service vm kernel doesn’t need RT related patches.
From:
acrn-users@... <acrn-users@...>
On Behalf Of shibi590268@...
Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched?
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Re: Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
Liu, Fuzhong
The service vm kernel doesn’t need RT related patches.
From: acrn-users@... <acrn-users@...>
On Behalf Of shibi590268@...
Sent: Tuesday, February 15, 2022 12:15 PM To: acrn-users@... Subject: [acrn-users] Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched?
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched
shibi590268@...
Does running an RT patched ubuntu as user vm require the service vm kernel to be RT patched?
|
|||||||||||||||||||||||||
|
|
|||||||||||||||||||||||||
|
2022 ACRN Project Technical Community Meeting: @ 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
|
|||||||||||||||||||||||||
|
|