Re: Cannot launch hart RT UOS when running Ubuntu as SOS
Liu, Fuzhong
Hi Alfonso Please share your acrn.efi and acrn-dm, will reproduce this issue on our side. Thanks!
BR. Fuzhong
From: acrn-users@... <acrn-users@...>
On Behalf Of Alfonso Sanchez-Beato
Sent: Wednesday, January 8, 2020 7:39 PM To: acrn-users@... Subject: Re: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS
Hi Liu,
On Wed, Jan 8, 2020 at 12:12 PM Liu, Fuzhong <fuzhong.liu@...> wrote:
I tried with that, but no difference in the traces :-/. Actually I had already tried with 'make all BOARD=nuc7i7dnb SCENARIO=industry', which I guess i the same.
Thanks Alfonso
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Problem with Industry Scenario on a NUC7i7DNH
Steve Osselton
Hi Liu, On inspection was running an old BIOS version, have upgraded to latest version (DNi70067) and disabled hyper threading. Things are improved in that I now get diagnostics from the serial port: ACRN Hypervisor calibrate_tsc, tsc_khz=2100000 [11041475us][cpu=0][sev=2][seq=1]:HV version 1.4-unstable-2019-11-18 09:13:55- DBG (daily tag:) build by mockbuild, start time 11028016us [11054921us][cpu=0][sev=2][seq=2]:API version 1.0 [11059914us][cpu=0][sev=2][seq=3]:Detect processor: Intel(R) Core(TM) i7-8650U CPU @ 1.90GHz [11069846us][cpu=0][sev=2][seq=4]:Assertion failed in file hw/pci.c,line 250 : fatal error So still failing. Also as a comment, the BIOS settings descriptions, are badly out of step with what you see from the latest visual BIOS. Cheers Steve. On Wed, 8 Jan 2020 at 13:46, Liu, Fuzhong <fuzhong.liu@...> wrote:
--
Engineering Director IOTech Systems Ltd. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Problem with Industry Scenario on a NUC7i7DNH
Liu, Fuzhong
Hi Steve, Please disable Hyper thread in BIOS for workaround. This issue is fixed in v1.5; will release soon.
BR. Fuzhong
From: acrn-users@... <acrn-users@...>
On Behalf Of Steve Osselton
Sent: Wednesday, January 8, 2020 8:32 PM To: acrn-users@... Subject: [acrn-users] Problem with Industry Scenario on a NUC7i7DNH
Hi, |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Problem with Industry Scenario on a NUC7i7DNH
Steve Osselton
Hi,
Am essentially following the deployment instructions for the ACRN industry scenario using a NUC7i7DNH with a serial port connected. https://projectacrn.github.io/latest/getting-started/rt_industry.html Flashing clear-31670-live-server.iso worked fine. Then followed the "Use the pre-installed industry ACRN hypervisor" section and installed serial port support. Again this all worked fine and looked good. I then rebooted the NUC. At HDMI console get "Intel NUC" banner with the following at top LHS of screen: detected 8 processes, 8 enabled current on process 0 And on serial port: E0S0 S0 Not sure what has happened here. Am I missing something obvious ? Thanks Steve |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Cannot launch hart RT UOS when running Ubuntu as SOS
Alfonso Sanchez-Beato
Hi Liu, On Wed, Jan 8, 2020 at 12:12 PM Liu, Fuzhong <fuzhong.liu@...> wrote:
I tried with that, but no difference in the traces :-/. Actually I had already tried with 'make all BOARD=nuc7i7dnb SCENARIO=industry', which I guess i the same.
Thanks Alfonso
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: Cannot launch hart RT UOS when running Ubuntu as SOS
Liu, Fuzhong
Hi Alfonso, You are using default launch_hard_rt_vm.sh, right? Maybe, it is SDC(by default) scenario for your acrn.efi, Please refer following patch:
diff --git a/hypervisor/arch/x86/Kconfig b/hypervisor/arch/x86/Kconfig index 41a78fe7..386a074b 100644 --- a/hypervisor/arch/x86/Kconfig +++ b/hypervisor/arch/x86/Kconfig @@ -1,6 +1,6 @@ choice prompt "ACRN Scenario" - default SDC + default INDUSTRY help Select the scenario name to load corresponding VM configuration.
Then;
cd ~/acrn-hypervisor make sudo make install
And try again.
Thanks!
BR. Fuzhong
From: acrn-users@... <acrn-users@...>
On Behalf Of alfonso.sanchez-beato@...
Sent: Wednesday, January 8, 2020 5:44 PM To: acrn-users@... Subject: [acrn-users] Cannot launch hart RT UOS when running Ubuntu as SOS
Hi, $ sudo /usr/share/acrn/samples/nuc/launch_hard_rt_vm.sh cpu1 online=1 cpu2 online=1 cpu3 online=1 pm by vuart node-index = 1 SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size 0x200000 vm_create: hard_rtvm VHM api version 1.0 failed to create VM hard_rtvm
[ 1530.397790] smpboot: CPU 1 is now offline [ 1530.398653] vhm: try to offline cpu 1 with lapicid 2 [ 1530.409744] smpboot: CPU 2 is now offline [ 1530.410476] vhm: try to offline cpu 2 with lapicid 4 [ 1530.429694] smpboot: CPU 3 is now offline [ 1530.430509] vhm: try to offline cpu 3 with lapicid 6 [ 1530.575078] nvme nvme0: failed to set APST feature (-19) [ 1530.579387] pci-stub 0000:02:00.0: claimed by stub [ 1530.661794] vhm_dev_open: opening device node [ 1530.663654] vhm: failed to create VM from Hypervisor ! [ 1531.163905] vhm: failed to create VM from Hypervisor ! [ 1531.664126] vhm: failed to create VM from Hypervisor ! [ 1532.164360] vhm: failed to create VM from Hypervisor ! [ 1532.664589] vhm: failed to create VM from Hypervisor ! [ 1533.164775] vhm: failed to create VM from Hypervisor ! [ 1533.664987] vhm: failed to create VM from Hypervisor ! [ 1534.165215] vhm: failed to create VM from Hypervisor ! [ 1534.665435] vhm: failed to create VM from Hypervisor ! [ 1535.165656] vhm: failed to create VM from Hypervisor ! [ 1535.682037] vhm: freed vm
Any hint on what might be going wrong and instructions on how to debug? I followed previously the tutorial for Clear Linux and was able to launch the RT image. I am using a NUC7i7DNH device. |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Cannot launch hart RT UOS when running Ubuntu as SOS
Alfonso Sanchez-Beato
Hi,
I have set-up Ubuntu as service OS by following the instructions in https://projectacrn.github.io/latest/tutorials/using_ubuntu_as_sos.html. ACRN is recognized as hypervisor and all looks good in principle. However, after that I followed the instructions on how to start an RT UOS and things fail: $ sudo /usr/share/acrn/samples/nuc/launch_hard_rt_vm.sh
cpu1 online=1
cpu2 online=1
cpu3 online=1
pm by vuart node-index = 1
SW_LOAD: get ovmf path /usr/share/acrn/bios/OVMF.fd, size 0x200000
vm_create: hard_rtvm
VHM api version 1.0
failed to create VM hard_rtvm
The kernel output is: [ 1530.397790] smpboot: CPU 1 is now offline
[ 1530.398653] vhm: try to offline cpu 1 with lapicid 2
[ 1530.409744] smpboot: CPU 2 is now offline
[ 1530.410476] vhm: try to offline cpu 2 with lapicid 4
[ 1530.429694] smpboot: CPU 3 is now offline
[ 1530.430509] vhm: try to offline cpu 3 with lapicid 6
[ 1530.575078] nvme nvme0: failed to set APST feature (-19)
[ 1530.579387] pci-stub 0000:02:00.0: claimed by stub
[ 1530.661794] vhm_dev_open: opening device node
[ 1530.663654] vhm: failed to create VM from Hypervisor !
[ 1531.163905] vhm: failed to create VM from Hypervisor !
[ 1531.664126] vhm: failed to create VM from Hypervisor !
[ 1532.164360] vhm: failed to create VM from Hypervisor !
[ 1532.664589] vhm: failed to create VM from Hypervisor !
[ 1533.164775] vhm: failed to create VM from Hypervisor !
[ 1533.664987] vhm: failed to create VM from Hypervisor !
[ 1534.165215] vhm: failed to create VM from Hypervisor !
[ 1534.665435] vhm: failed to create VM from Hypervisor !
[ 1535.165656] vhm: failed to create VM from Hypervisor !
[ 1535.682037] vhm: freed vm
Thanks! Alfonso |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2020 ACRN Project Technical Community Meeting (2020/1~2020/7): @ Weekly Wednesday 11AM (China-Shanghai), Tuesday 7PM (US-West Coast), Wednesday 3AM (Europe-London)
<Detailed calendar will be published
1 week before meeting>
We're still in the early stages of forming this TSC, so instead we invite you to attend a weekly "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:
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Canceled: ACRN Project Technical Community Meeting (2019/7~2019/12): @ Weekly Wednesday 11AM (China-Shanghai), Tuesday 7PM (US-West Coast), Wednesday 3AM (Europe-London)
<Cancel WW52 meeting due to Christmas Holiday>
We're still in the early stages of forming this TSC, so instead we invite you to attend a weekly "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:
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
2019 ACRN Reflections: Keep Running
2019 ACRN Reflections: Keep Running
Can you believe December is almost gone? While many of us are looking forward to the holidays and time with our loved ones, December also brings a convenient occasion to look back on the year and check out what ACRN has achieved in 2019. · The first keyword in mind: Production – ACRN drives on the road!A new SUV based on ACRN, the EXEED-LX, was officially released by the Chinese car maker Chery in Q3’19. It features the eye-catching dual 12.3-inch floating LCD screen, a newly designed electronic instrument cluster, a facial recognition system that automatically adjusts the interior settings customized for the driver, and an AR-enhanced real-life navigation system that gets you where you need to go. These applications are made possible by adopting Intel’s Apollo Lake processor and the ACRN™ virtualization solution. The ACRN hypervisor builds a virtual layer on top of the underlying hardware processor, achieving multi-OS workload consolidation to ensure isolation and non-interference between the electronic instrument cluster and the infotainment system. ACRN supports fast start-up, enabling the rapid display of cluster dashboards. ACRN also supports the underlying hardware resource sharing, where a single, physical graphics card can simultaneously display the UI of the instrument cluster dashboard and the IVI system. It similarly supports shared storage devices, shared network interface controllers, and shared sound cards. Congratulations to Chery*, Neusoft* and Intel teams for making this happen. The ACRN project really appreciates your seamless collaboration! · ACRN targets two main scenarios: SDC and Industrial Workload ConsolidationACRN 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 and implemented in less than 40K lines of code. Now that the Software Defined Cockpit (SDC) scenario is complete, ACRN is devoting its resources in a more challenging realm: Industrial Workload Consolidation. These features are still in development but show great promise:
· With contributions from the community, ACRN hosted an IoT seminar in ShanghaiThe 1st Open Source IoT Projects Seminar was held on June in Shanghai. This was the first time that the ACRN project ran a community seminar with a focus on promoting open source projects in the IoT arena. Themed ‘Open Source Drives IoT, From Device to Edge’, the seminar was sponsored through collaboration between ACRN, Celadon, AliOS, Clear Linux, ROS 2, StarlingX and Zephyr projects. The seminar covered a wide spectrum of technologies, from virtualization, real-time, security and safely, to industrial real-time workload consolidation, IVI, automotive, drones, robotic, retail and other technologies which enable numerous IoT innovations. The seminar featured 30 technical speeches, 13 demos and 4 hands-on/workshops. It was attended by 161 community developers, software engineers, and technical managers from key partners and customers. The ACRN community is becoming stronger
About the ACRN™ Project 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. To learn more, please visit https://projectacrn.org/. About the Linux Foundation Founded in 2000, the Linux Foundation is supported by more than 1,000 members and is the world’s leading home for collaboration on open source software, open standards, open data, and open hardware. Linux Foundation’s projects are critical to the world’s infrastructure including Linux, Kubernetes, Node.js, and more. The Linux Foundation’s methodology focuses on leveraging best practices and addressing the needs of contributors, users and solution providers to create sustainable models for open collaboration. For more information, please visit us at linuxfoundation.org.
Best regards. Hongbo Tel: +86-21-6116 7445 MP: +86-1364 1793 689 Mail: hongbo.wang@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACRN Project Technical Community Meeting Minutes - 12/18/2019
ACRN Project TCM – 18Th Dec 2019
Meeting Achieves:
Agenda
The online meeting will switch back to Zoom.
Download foil from ACRN Presentation->ACRN_TCM->WW51’19
Short description: In this talk, we introduced TLB invalidation, paging structure caches, kernel page table isolation, Linux KPTI implementation, lazy TLB mode, address mapping types
when EPT in use, how to enable PCID virtualization in order to support Linux KPTI and improve the system performance
Marketing/Events
Resources
=======================
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACRN Project Technical Community Meeting (2019/7~2019/12): @ Weekly Wednesday 11AM (China-Shanghai), Tuesday 7PM (US-West Coast), Wednesday 3AM (Europe-London)
<Back to Zoom Online meeting from this week, find the Zoom URL at the bottom of calendar >
Date: 12/18
Topic: Process-Context Identifier Virtualization support in ACRN
Description: N/A
We're still in the early stages of forming this TSC, so instead we invite you to attend a weekly "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:
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACRN Project Technical Community Meeting Minutes - 12/11/2019
ACRN Project TCM – 11Th Dec 2019
Location
Agenda
Download foil from ACRN Presentation->ACRN_TCM->WW50’19
Short description: We will present and demo how to set up ACRN Hypervisor from the metal bare, and use ACRN Configuration tool to configure and build/deploy ACRN for a new platform.
Marketing/Events
Resources
=======================
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACRN Project Technical Community Meeting (2019/7~2019/12): @ Weekly Wednesday 11AM (China-Shanghai), Tuesday 7PM (US-West Coast), Wednesday 3AM (Europe-London)
<Back to Zoom Online meeting from this week, find the Zoom URL at the bottom of calendar >
Date: 12/11
Topic: How to use configuration tool to deploy ACRN on new platform
Description: We will present and demo how to set up ACRN Hypervisor from the metal bare, and use ACRN Configuration tool to configure and
build/deploy ACRN for a new platform..
We're still in the early stages of forming this TSC, so instead we invite you to attend a weekly "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:
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACRN Project Technical Community Meeting Minutes - 12/4/2019
Meeting Minutes archive: https://drive.google.com/drive/u/2/folders/111m6iU3PjSZebOOKzLagYPUWMvseGLeU
Meeting foils archive: https://drive.google.com/drive/u/1/folders/1_XTGu6re3BOQAjtPx636Mz1T5lOy2UWC
ACRN Project TCM - 4th Dec 2019
Location
Agenda
Download foil from ACRN Presentation->ACRN_TCM->WW49’19
Short description: In order to meet Functional Safety certification, ACRN source codes need to be MISRA-C compliant. In this talk, we'll introduce ACRN's coding guideline, how to maintain each patch
set to follow the guideline and what you need to do if there's deviation. Guide and issues reported from community.
Marketing/Events
Resources
=======================
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
ACRN Project Technical Community Meeting (2019/7~2019/12): @ Weekly Wednesday 11AM (China-Shanghai), Tuesday 7PM (US-West Coast), Wednesday 3AM (Europe-London)
Date: 12/4
Topic: ACRN Coding Guideline Deviation
Description: In order to meet Functional Safety certification, ACRN source codes need to be MISRA-C compliant. In this talk, we'll introduce
ACRN's coding guideline, how to maintain each patch set to follow the guideline and what you need to do if there's deviation.
We're still in the early stages of forming this TSC, so instead we invite you to attend a weekly "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:
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
Mail: hongbo.wang@...
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: How to get the 2nd vCPU running in the Industry scenario?
Victor Sun
Agree, we should avoid maxcpus setting.
toggle quoted message
Show quoted text
Currently only SOS cmdline of hybrid scenario might need this setting as a workaround, to avoid enumerating all cpus when bootup APs. When SOS MADT table could be customized, then this workaround is valueless also. BR, Victor -----Original Message-----
From: acrn-users@... <acrn-users@...> On Behalf Of Geoffroy Van Cutsem Sent: Thursday, November 28, 2019 3:23 PM To: acrn-users@... Subject: Re: [acrn-users] How to get the 2nd vCPU running in the Industry scenario? On Thu, 2019-11-28 at 02:04 +0000, Liu, Fuzhong wrote: Hi TonnyIs there any value at all in having this maxcpus parameter *anywhere*? My thinking is that it's ACRN that determines how many vCPUs are visible to any User VM, and we'd want our User VM to always use as many as are available, regardless of whether this is an RTVM or a standard User VM, wouldn't we? Thanks, Geoffroy |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: How to get the 2nd vCPU running in the Industry scenario?
On Thu, 2019-11-28 at 02:04 +0000, Liu, Fuzhong wrote:
Hi TonnyIs there any value at all in having this maxcpus parameter *anywhere*? My thinking is that it's ACRN that determines how many vCPUs are visible to any User VM, and we'd want our User VM to always use as many as are available, regardless of whether this is an RTVM or a standard User VM, wouldn't we? Thanks, Geoffroy |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: How to get the 2nd vCPU running in the Industry scenario?
Liu, Fuzhong
Hi Tonny You should copy https://github.com/projectacrn/acrn-hypervisor/blob/master/devicemodel/samples/nuc/launch_hard_rt_vm.sh for RTVM; Not maxcpus parameter in it. Not https://github.com/projectacrn/acrn-hypervisor/blob/master/devicemodel/samples/nuc/launch_uos.sh
BR. Fuzhong From: acrn-users@... <acrn-users@...>
On Behalf Of Tzeng, Tonny
Sent: Thursday, November 28, 2019 9:21 AM To: acrn-users@... Subject: Re: [acrn-users] How to get the 2nd vCPU running in the Industry scenario?
Hi Fuzhong,
You are right! I just copied this comment line to my kernel command line without noticing it limits the vCPU to 1. Both vCPU are running now, though you may consider to remove this misleading parameter in the sample launch script. 😊
Regards, Tonny
From:
acrn-users@... <acrn-users@...>
On Behalf Of Liu, Fuzhong
Hi Tonny About the secondary vCPU is in “Init” mode after I launch user VM. The HV console indicates:
ACRN:\>vcpu_list
VM ID PCPU ID VCPU ID VCPU ROLE VCPU STATE ===== ======= ======= ========= ========== 0 0 0 PRIMARY Running 2 2 0 PRIMARY Running 2 3 1 SECONDARY Init
I think you add maxcpus=1 in your kernel comline; Could you please share the user VM kernel comline?
ACRN:\>vcpu_list(without maxcpus=1)
VM ID PCPU ID VCPU ID VCPU ROLE VCPU STATE ===== ======= ======= ========= ========== 0 0 0 PRIMARY Running 2 2 0 PRIMARY Running 2 3 1 SECONDARY Running
ACRN:\>vcpu_list(with maxcpus=1)
VM ID PCPU ID VCPU ID VCPU ROLE VCPU STATE ===== ======= ======= ========= ========== 0 0 0 PRIMARY Running 2 2 0 PRIMARY Running 2 3 1 SECONDARY Init
BR. Fuzhong From:
acrn-users@... <acrn-users@...>
On Behalf Of Victor Sun
Hi Tonny, This is a known issue. In current implementation, SOS will offline all vcpus except BSP before launch any user VM(i.e. offline pCPU1/2/3 in your case), and your launched user VM2 only init pCPU2/3 to run, this cause pCPU1 always be offlined until you launch user VM1. In our new implementation, acrn-config tool will do a modification in launch script, that only pCPUs belong to the launched VM could be offlined, then it will resolve your issue. or you can modify the launch script by manual: for i in `ls -d /sys/devices/system/cpu/cpu[1-99]`; do + # do not offline the CPU which not belong to the UOS + if [ "i" = "/sys/devices/system/cpu/cpu1" ]; then continue; fi online=`cat $i/online` BR, Victor
On 11/27/2019 5:15 PM, Tzeng, Tonny wrote:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Re: How to get the 2nd vCPU running in the Industry scenario?
Victor Sun
Thanks Fuzhong to correct my misunderstanding!
BR, Victor
From: acrn-users@... <acrn-users@...>
On Behalf Of Tzeng, Tonny
Sent: Thursday, November 28, 2019 9:21 AM To: acrn-users@... Subject: Re: [acrn-users] How to get the 2nd vCPU running in the Industry scenario?
Hi Fuzhong,
You are right! I just copied this comment line to my kernel command line without noticing it limits the vCPU to 1. Both vCPU are running now, though you may consider to remove this misleading parameter in the sample launch script. 😊
Regards, Tonny
From:
acrn-users@... <acrn-users@...>
On Behalf Of Liu, Fuzhong
Hi Tonny About the secondary vCPU is in “Init” mode after I launch user VM. The HV console indicates:
ACRN:\>vcpu_list
VM ID PCPU ID VCPU ID VCPU ROLE VCPU STATE ===== ======= ======= ========= ========== 0 0 0 PRIMARY Running 2 2 0 PRIMARY Running 2 3 1 SECONDARY Init
I think you add maxcpus=1 in your kernel comline; Could you please share the user VM kernel comline?
ACRN:\>vcpu_list(without maxcpus=1)
VM ID PCPU ID VCPU ID VCPU ROLE VCPU STATE ===== ======= ======= ========= ========== 0 0 0 PRIMARY Running 2 2 0 PRIMARY Running 2 3 1 SECONDARY Running
ACRN:\>vcpu_list(with maxcpus=1)
VM ID PCPU ID VCPU ID VCPU ROLE VCPU STATE ===== ======= ======= ========= ========== 0 0 0 PRIMARY Running 2 2 0 PRIMARY Running 2 3 1 SECONDARY Init
BR. Fuzhong From:
acrn-users@... <acrn-users@...>
On Behalf Of Victor Sun
Hi Tonny, This is a known issue. In current implementation, SOS will offline all vcpus except BSP before launch any user VM(i.e. offline pCPU1/2/3 in your case), and your launched user VM2 only init pCPU2/3 to run, this cause pCPU1 always be offlined until you launch user VM1. In our new implementation, acrn-config tool will do a modification in launch script, that only pCPUs belong to the launched VM could be offlined, then it will resolve your issue. or you can modify the launch script by manual: for i in `ls -d /sys/devices/system/cpu/cpu[1-99]`; do + # do not offline the CPU which not belong to the UOS + if [ "i" = "/sys/devices/system/cpu/cpu1" ]; then continue; fi online=`cat $i/online` BR, Victor
On 11/27/2019 5:15 PM, Tzeng, Tonny wrote:
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|