1. acrn-users@lists.projectacrn.org
  2. Messages
   Date   
QEMU base image/config for reference?

matthew.e.hiltner@...
 

Hello -

I notice in the 2.0 release notes that QEMU support is improved. Does the project periodically maintain a QCOW2+config that can be used for reference or regression? Not finding anything, but forgive if I've missed a pointer somewhere...

if not, is there a BKM for QEMU bringup?

-Matt
2020 ACRN Project Technical Community Meeting Minutes - WW28'20

Zou, Terry
 

ACRN Project TCM - 8th Jul 2020
Location
  1. Online by Zoom: https://zoom.com.cn/j/320664063   
    2.
Attendees (Total 20, 8/7)
 
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
  1. ACRN project update
    2.
 
  1. “WW28’20 Inter-VM communication Introduction (DM land)“ by LIU, Yuan
    2.
Download foil from ACRN Presentation->WW28’20
Description: Inter-VM communication Introduction (DM land), we will talk about shared memory based inter-vm communication solution on ACRN to meet high throughput and low latency requirements.
 
  1. All: Community open discussion.
    2.
Q&A: Q1 could Ivshmen solution support windows guest communication: Yes.
 
  1. Next meeting agenda proposal:
    2.
WW Topic Presenter Status
WW28 Inter-VM communication Introduction (DM land) Liu, Yuan1 7/8/2020
WW30 PTM virtualization Introduction Wang, Qian 7/22/2020
WW32 TSN pass through Introduction Wu, Binbin 8/5/2020
WW34 Safety VM introduction Mao Junjie 8/19/2020
WW36 TCC feature introduction-split lock Li Fei/Tao Yuhong 9/2/2020
WW38 Inter-VM communication Introduction (HV land) Liu, Yuan1 9/16/2020
Marketing/Events
  1. N/A
    2.
Resources
  1. Project URL: 
    2.
  1. Portal: https://projectacrn.org   
  2. Source code: https://github.com/projectacrn   
  3. email: info@... 
  4. Technical Mailing list: acrn-dev@... 
    5.
 
========================
 
 

PDF
WW28'20 Inter-VM communication Introduction (DM land).pdf

Re: ACRN + Kata Containers (and 'acrnctl')

Geoffroy Van Cutsem
 

Thanks for your explanation Vijay. It would make a lot of sense to me to build and install `acrnctl` even for a RELEASE=1 build. I'd like to hear from the engineering team if they have any objection to that. If not, I can prepare a patch to remove the conditional statements in the Makefiles.

[note: also adding the acrn-dev mailing list to make sure the developers see this thread]

Thanks,
Geoffroy

-----Original Message-----
From: Dhanraj, Vijay <vijay.dhanraj@...>
Sent: Tuesday, June 30, 2020 6:55 PM
To: VanCutsem, Geoffroy <geoffroy.vancutsem@...>; acrn-
users@...
Subject: RE: ACRN + Kata Containers (and 'acrnctl')

Hi Geoffroy,

Thanks for bring up this issue.

"acrnctl" binary is critical for kata containers when using ACRN hypervisor.
Kata uses this binary to add container rootfs. Using acrnctl blkrescan feature,
kata can add virtio-blk devices with dummy backend during VM launch and
later replace the dummy backend with the actual file (the container rootfs).

My suggestion would be to build and install acrnctl for RELEASE=1 build as
well.

Thanks,
-Vijay

-----Original Message-----
From: VanCutsem, Geoffroy <geoffroy.vancutsem@...>
Sent: Tuesday, June 30, 2020 2:29 AM
To: acrn-users@...; Dhanraj, Vijay
<vijay.dhanraj@...>
Subject: ACRN + Kata Containers (and 'acrnctl')

Hi folks, Vijay,

The ACRN + Kata Containers configuration (described here [1]) includes a
definition for 'ctlpath' that points at the 'acrnctl' binary. That binary is only
built and installed for the debug version of ACRN (see also [2] for more
details), which means you cannot run Kata Containers with a released version
of ACRN today. I think we need to solve this and I can see two ways:
* Kata Containers does not really use that binary (and we can get rid of its
definition) OR
* We make sure 'acrnctl' is also built and installed for a RELEASE=1 build

What would be the right way to fix this?

[1] https://projectacrn.github.io/latest/tutorials/run_kata_containers.html
[2] https://github.com/projectacrn/acrn-hypervisor/issues/4940

Thanks!
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
Re: Debugging the UOS

Geoffroy Van Cutsem
 

Thanks Tomasz, I think such feature makes sense so thanks for filing the request!!

Geoffroy

-----Original Message-----
From: acrn-users@... <acrn-users@...>
On Behalf Of Tomasz Bursztyka
Sent: Tuesday, June 30, 2020 11:09 AM
To: acrn-users@...
Subject: Re: [acrn-users] Debugging the UOS

Hello,

About this gdb server missing feature, I just opened a github issue:
https://github.com/projectacrn/acrn-hypervisor/issues/4997


Tomasz


1. Currently, Zephyr does not support kgdb.
2. If you want to debug UOS with gdb server, I guess that support for
gdb server has to ben added in ACRN.
- Gdb server can be used to debug zephyr running with qemu. It is
because qemu supports gdb server. So, similarly, gdb server support
needs to be enabled in ACRN.
Re: ACRN + Kata Containers (and 'acrnctl')

Vijay Dhanraj
 

Hi Geoffroy,

Thanks for bring up this issue.

"acrnctl" binary is critical for kata containers when using ACRN hypervisor. Kata uses this binary to add container rootfs. Using acrnctl blkrescan feature, kata can add virtio-blk devices with dummy backend during VM launch and later replace the dummy backend with the actual file (the container rootfs).

My suggestion would be to build and install acrnctl for RELEASE=1 build as well.

Thanks,
-Vijay

-----Original Message-----
From: VanCutsem, Geoffroy <geoffroy.vancutsem@...>
Sent: Tuesday, June 30, 2020 2:29 AM
To: acrn-users@...; Dhanraj, Vijay <vijay.dhanraj@...>
Subject: ACRN + Kata Containers (and 'acrnctl')

Hi folks, Vijay,

The ACRN + Kata Containers configuration (described here [1]) includes a definition for 'ctlpath' that points at the 'acrnctl' binary. That binary is only built and installed for the debug version of ACRN (see also [2] for more details), which means you cannot run Kata Containers with a released version of ACRN today. I think we need to solve this and I can see two ways:
* Kata Containers does not really use that binary (and we can get rid of its definition) OR
* We make sure 'acrnctl' is also built and installed for a RELEASE=1 build

What would be the right way to fix this?

[1] https://projectacrn.github.io/latest/tutorials/run_kata_containers.html
[2] https://github.com/projectacrn/acrn-hypervisor/issues/4940

Thanks!
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
ACRN + Kata Containers (and 'acrnctl')

Geoffroy Van Cutsem
 

Hi folks, Vijay,

The ACRN + Kata Containers configuration (described here [1]) includes a definition for 'ctlpath' that points at the 'acrnctl' binary. That binary is only built and installed for the debug version of ACRN (see also [2] for more details), which means you cannot run Kata Containers with a released version of ACRN today. I think we need to solve this and I can see two ways:
* Kata Containers does not really use that binary (and we can get rid of its definition) OR
* We make sure 'acrnctl' is also built and installed for a RELEASE=1 build

What would be the right way to fix this?

[1] https://projectacrn.github.io/latest/tutorials/run_kata_containers.html
[2] https://github.com/projectacrn/acrn-hypervisor/issues/4940

Thanks!
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
Re: Debugging the UOS

Tomasz Bursztyka
 

Hello,

About this gdb server missing feature, I just opened a github issue:
https://github.com/projectacrn/acrn-hypervisor/issues/4997


Tomasz

1. Currently, Zephyr does not support kgdb.
2. If you want to debug UOS with gdb server, I guess that support for
gdb server has to ben added in ACRN.
- Gdb server can be used to debug zephyr running with qemu. It is
because qemu supports gdb server. So, similarly, gdb server support
needs to be enabled in ACRN.

2020 ACRN Project Technical Community Meeting (2020/7~2020/12): @ Weekly 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:

WW

Topic

Presenter

Status

WW28

Inter-VM communication Introduction (DM land)

Liu, Yuan1

7/8/2020

WW30

PTM virtualization Introduction

Wang, Qian

7/22/2020

WW32

TSN pass through Introduction

Wu, Binbin

8/5/2020

WW34

Safety VM introduction

Mao Junjie

8/19/2020

WW36

TCC feature introduction-split lock

Li Fei/Tao Yuhong

9/2/2020

WW38

Inter-VM communication Introduction (DM land)

Liu, Yuan1

9/16/2020

 

Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices

https://projectacrn.org  ||  https://github.com/projectacrn  ||  info@...

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:

  • Meets every Wednesday, Starting Nov 07, 2018: 11AM-12AM (China-Shanghai), 7PM-8PM (US-West Coast), 3AM-4AM (Europe-London)
  • Chairperson: Hongbo Wang, hongbo.wang@... (Intel)
  • Online conference link: https://zoom.com.cn/j/320664063
  • Zoom Meeting ID: 320 664 063
  • Special Notes: If you have Zoom connection issue by using web browser, please launch Zoom application, manually input the meeting ID (320664063) to join the Zoom meeting.
  • Online conference phone:
    • China: +86 010 87833177  or 400 669 9381 (Toll Free)
    • Germany: +49 (0) 30 3080 6188  or +49 800 724 3138 (Toll Free)
    • US: +1 669 900 6833  or +1 646 558 8656   or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
    • Additional international phone numbers
  • Meeting Notes:

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

Calendar

Canceled: 2020 ACRN Project Technical Community Meeting (2020/1~2020/7): @ Weekly Wednesday 4PM (China-Shanghai), Wednesday 9AM (Europe-London), Tuesday 0AM (US-West Coast),

Wang, Hongbo
 

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:
WW Topic Presenter Status
WW03 Expose and pass through platform hidden PCIs devices to SOS LI, Fei 1/15
WW08 EtherCAT 101 MAO, Junjie 2/19
WW09 How to build a Yocto based SOS on ACRN LIU, Fuzhong 2/26
WW10 CPU Sharing - BVT scheduler in ACRN Hypervisor CHEN, Conghui 3/4
WW11 ACRN Hypervisor Introduction CHEN, Jason 3/11
WW12 ACRN Configuration: scenarios and config tool SUN, Victor 3/18
WW13 ACRN Device Model Architecture Introduction LIU, Yuan 3/25
WW11 SR-IOV on ACRN LIU, Yuan 4/8
WW14 CSME virtualization Tomas 4/1
WW15 ACRN device passthrough overall introduction WU, Binbin 4/8
WW16 ACRN Debug Tool YIN, Fengwei 4/15
WW17 CPU Virtualization WU, Binbin 4/22
WW18 I2C mediator introduction CHEN, Conghui 4/29
WW19 USB Meditator LIU, Long 5/6
WW20 Meta-ACRN project introduction Saini, Naveen Kumar 5/13
WW21 GVT-d Overview ZHAO, Yakui 5/20
WW22 GPIO mediator introduction LIU, Long 5/27
WW23 CPU sharing – framework LIU, Shuo 6/3
WW24 ACRN v2.0 architecture introduction CHEN, Jason 6/10
WW25 ACRN secure boot WU, Binbin 6/17
WW26 ACRN and VMs Sx sates handling YIN, Fengwei 6/23
 
 
 
 
 
Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices
 
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:
  • Meets every Wednesday, Starting Nov 07, 2018: 11AM-12AM (China-Shanghai), 7PM-8PM (US-West Coast), 3AM-4AM (Europe-London)
  • Chairperson: Hongbo Wang, hongbo.wang@... (Intel)
  • Online conference link: https://zoom.com.cn/j/320664063
  • Zoom Meeting ID: 320 664 063
  • Special Notes: If you have Zoom connection issue by using web browser, please launch Zoom application, manually input the meeting ID (320664063) to join the Zoom meeting.
  • Online conference phone:
    •
  • China: +86 010 87833177  or 400 669 9381 (Toll Free)
  • Germany: +49 (0) 30 3080 6188  or +49 800 724 3138 (Toll Free)
  • US: +1 669 900 6833  or +1 646 558 8656   or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
  • Additional international phone numbers
    •
  • Meeting Notes:
    •
 
 
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
 

Calendar

Canceled: 2020 ACRN Project Technical Community Meeting (2020/1~2020/7): @ Weekly Wednesday 4PM (China-Shanghai), Wednesday 9AM (Europe-London), Tuesday 0AM (US-West Coast),

Wang, Hongbo
 

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:
WW Topic Presenter Status
WW03 Expose and pass through platform hidden PCIs devices to SOS LI, Fei 1/15
WW08 EtherCAT 101 MAO, Junjie 2/19
WW09 How to build a Yocto based SOS on ACRN LIU, Fuzhong 2/26
WW10 CPU Sharing - BVT scheduler in ACRN Hypervisor CHEN, Conghui 3/4
WW11 ACRN Hypervisor Introduction CHEN, Jason 3/11
WW12 ACRN Configuration: scenarios and config tool SUN, Victor 3/18
WW13 ACRN Device Model Architecture Introduction LIU, Yuan 3/25
WW11 SR-IOV on ACRN LIU, Yuan 4/8
WW14 CSME virtualization Tomas 4/1
WW15 ACRN device passthrough overall introduction WU, Binbin 4/8
WW16 ACRN Debug Tool YIN, Fengwei 4/15
WW17 CPU Virtualization WU, Binbin 4/22
WW18 I2C mediator introduction CHEN, Conghui 4/29
WW19 USB Meditator LIU, Long 5/6
WW20 Meta-ACRN project introduction Saini, Naveen Kumar 5/13
WW21 GVT-d Overview ZHAO, Yakui 5/20
WW22 GPIO mediator introduction LIU, Long 5/27
WW23 CPU sharing – framework LIU, Shuo 6/3
WW24 ACRN v2.0 architecture introduction CHEN, Jason 6/10
WW25 ACRN secure boot WU, Binbin 6/17
WW26 ACRN and VMs Sx sates handling YIN, Fengwei 6/23
 
 
 
 
 
Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices
 
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:
  • Meets every Wednesday, Starting Nov 07, 2018: 11AM-12AM (China-Shanghai), 7PM-8PM (US-West Coast), 3AM-4AM (Europe-London)
  • Chairperson: Hongbo Wang, hongbo.wang@... (Intel)
  • Online conference link: https://zoom.com.cn/j/320664063
  • Zoom Meeting ID: 320 664 063
  • Special Notes: If you have Zoom connection issue by using web browser, please launch Zoom application, manually input the meeting ID (320664063) to join the Zoom meeting.
  • Online conference phone:
    •
  • China: +86 010 87833177  or 400 669 9381 (Toll Free)
  • Germany: +49 (0) 30 3080 6188  or +49 800 724 3138 (Toll Free)
  • US: +1 669 900 6833  or +1 646 558 8656   or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
  • Additional international phone numbers
    •
  • Meeting Notes:
    •
 
 
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
 

Calendar

[Announce] ACRN Open Source Ver2.0 Release Notes

Zou, Terry
 

Hi all,

 

We are very pleased to announce Version 2.0 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.0.html

 

ACRN v2.0 offers new and improved scenario definitions, with a focus on industrial IoT and edge device use cases. ACRN supports these uses with their demanding and varying workloads including Functional Safety certification, real-time characteristics, device and CPU sharing, and general computing power needs, while honoring required isolation and resource partitioning. A wide range of User VM OSs (such as Windows 10, Ubuntu, Android, and VxWorks) can run on ACRN, running different workloads and applications on the same hardware platform.

 

A new hybrid-mode architecture adds flexibility to simultaneously support both traditional resource sharing among VMs and complete VM resource partitioning required for functional safety requirements.

 

Workload management and orchestration, rather standard and mature in cloud environments, are enabled now in ACRN, allowing open source orchestrators such as OpenStack to manage ACRN virtual machines. Kata Containers, a secure container runtime, has also been enabled on ACRN and can be orchestrated via Docker or Kubernetes.

 

Rounding things out, we’ve also made significant improvements in configuration tools, added many new tutorial documents, and enabled ACRN on the QEMU machine emulator making it easier to try out and develop with ACRN.

 

Version 1.6.1 features (comparing with v1.0):

 

Documentation Updates: many new and updated reference documents are available, including:

-          General

-          Getting Started

o   Getting Started Guide for ACRN Industry Scenario with Ubuntu Service VM

o   Getting Started Guide for ACRN logical partition mode

-          Configuration and Tools

o   ACRN Configuration Tool

-          Service VM Tutorials

o   Run Debian as the Service VM

-          User VM Tutorials

o   Run Zephyr as the User VM

o   Run Debian as the User VM

o   Run Celadon as the User VM

o   Launch Windows as the Guest VM on ACRN

o   Run VxWorks as the User VM

o   Run Xenomai as the User VM OS (Real-Time VM)

-          Enable ACRN Features

o   Enable OVS in ACRN

o   Enable RDT Configuration

o   Enable SR-IOV Virtualization

o   Enable CPU Sharing in ACRN

o   Run Kata Containers on a Service VM

o   Enable Secure Boot in Windows

o   Enable S5 in ACRN

o   Enable vUART Configurations

o   Enable SGX Virtualization

o   Enable QoS based on runC Containers

o   Configure ACRN using OpenStack and libvirt

o   Enable ACRN over QEMU/KVM

o   Enable GVT-d in ACRN

o   Using GRUB to boot ACRN

-          Debug

o   ACRN Real-Time (RT) Performance Analysis

o   ACRN Real-Time VM Performance Tips

-          High-Level Design Guides

o   Virtio-i2c

o   Split Device Model

o   Device Passthrough

o   VT-d Interrupt-remapping

 

ACRN is a flexible, lightweight reference hypervisor that is built with real-time and safety-criticality in mind. It is optimized to streamline embedded development through an open source platform. Check out What is ACRN for more information. All project ACRN source code is maintained in the https://github.com/projectacrn/acrn-hypervisor repository and includes folders for the ACRN hypervisor, the ACRN device model, tools, and documentation. You can either download this source code as a zip or tar.gz file (see the ACRN v2.0 GitHub release page) or use Git clone and checkout commands:

 

git clone https://github.com/projectacrn/acrn-hypervisor
cd acrn-hypervisor
git checkout v2.0

 

The project’s online technical documentation is also tagged to correspond with a specific release: generated v2.0 documents can be found at https://projectacrn.github.io/2.0/. Documentation for the latest (master) branch is found at https://projectacrn.github.io/latest/. Follow the instructions in the Getting Started Guide for ACRN Industry Scenario with Ubuntu Service VM to get started with ACRN.

 

We recommend that all developers upgrade to ACRN release v2.0.

 

Best & Regards

Terry
2020 ACRN Project Technical Community Meeting Minutes - WW26'20

Zou, Terry
 

ACRN Project TCM - 24th Jun 2020
Location
  1. Online by Zoom: https://zoom.com.cn/j/320664063   
    2.
Attendees (Total 28, 24/6)
 
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
  1. ACRN project update
    2.
ACRN Online Meet-up(Asia session) is planned in July, welcome to join and submit topics.
 
  1. “WW26‘20 ACRN Secure Boot Introduction” by WU, Binbin
    2.
Download foil from ACRN Presentation->WW26’20
Description: ACRN secure boot introduction, we will talk about the process of secure boot on ACRN using SBL/UEFI BIOS.
 
  1. All: Community open discussion.
    2.
Q&A: Q1 OVMF stands for ‘Open Virtual Machine Firmware’
 
  1. Next meeting agenda proposal:
    2.
WW Topic Presenter Status
WW03 Expose and pass through platform hidden PCIs devices to SOS LI, Fei 1/15
WW08 EtherCAT 101 MAO, Junjie 2/18
WW09 How to build a Yocto based SOS on ACRN LIU, Fuzhong 2/26
WW10 CPU Sharing - BVT scheduler in ACRN Hypervisor CHEN, Conghui 3/4
WW11 ACRN Hypervisor Introduction CHEN, Jason 3/11
WW12 ACRN Configuration: scenarios and config tool SUN, Victor 3/18
WW13 ACRN Device Model Architecture Introduction LIU, Yuan 3/25
WW14 SR-IOV on ACRN LIU, Yuan 4/1
WW15 CSME virtualization Tomas 4/8
WW16 ACRN device passthrough overall introduction WU, Binbin 4/15
WW17 ACRN Debug Tool YIN, Fengwei 4/22
WW18 I2C mediator introduction CHEN, Conghui 4/29
WW19 USB mediator Introduction LIU, Long 5/6
WW20 Meta-ACRN project introduction Saini, Naveen Kumar 5/13
WW21 GVT-d Overview ZHAO, Yakui 5/20
WW22 GPIO mediator introduction LIU, Long 5/27
WW23 CPU sharing – framework LIU, Shuo 6/3
WW24 ACRN 2.0 architecture introduction CHEN, Jason 6/10
WW25 ACRN 2.0 power management introduction Yin, Fengwei 6/17
WW26 ACRN secure boot Wu, Binbin 6/24
Marketing/Events
  1. N/A
    2.
Resources
  1. Project URL: 
    2.
  1. Portal: https://projectacrn.org   
  2. Source code: https://github.com/projectacrn   
  3. email: info@... 
  4. Technical Mailing list: acrn-dev@... 
    5.
========================
 

PDF
WW26‘20 ACRN Secure Boot Introduction.pdf

2020 ACRN Project Technical Community Meeting Minutes - WW25'20

Zou, Terry
 

ACRN Project TCM - 17th Jun 2020
Location
  1. Online by Zoom: https://zoom.com.cn/j/320664063   
    2.
Attendees (Total 30, 17/6)
 
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
  1. ACRN project update
    2.
N/A 
 
  1. “ACRN Power Management Introduction” by YIN, Fengwei
    2.
Download foil from ACRN Presentation->WW25’20
Description: We will refresh power management in ACRN 2.0 design. In ACRN 2.0, the power management was re-designed to fit Industrial use case requirement, both for CPU sharing and C/P status management need be updated.
 
  1. All: Community open discussion.
    2.
Q&A: 
Q1: Could User OS reject the system shutdown request from SOS:  NO, only one exception of RTVM may still run, then hypervisor will decide and maybe not full system shutdown.
Q2: CPU governor is in hypervisor to control CPU sharing case: vCPU C/P is disabled in VM. But for CPU partition mode, the governor is owned by guest OS totally. 
  1. Next meeting agenda proposal:
    2.
WW Topic Presenter Status
WW03 Expose and pass through platform hidden PCIs devices to SOS LI, Fei 1/15
WW08 EtherCAT 101 MAO, Junjie 2/18
WW09 How to build a Yocto based SOS on ACRN LIU, Fuzhong 2/26
WW10 CPU Sharing - BVT scheduler in ACRN Hypervisor CHEN, Conghui 3/4
WW11 ACRN Hypervisor Introduction CHEN, Jason 3/11
WW12 ACRN Configuration: scenarios and config tool SUN, Victor 3/18
WW13 ACRN Device Model Architecture Introduction LIU, Yuan 3/25
WW14 SR-IOV on ACRN LIU, Yuan 4/1
WW15 CSME virtualization Tomas 4/8
WW16 ACRN device passthrough overall introduction WU, Binbin 4/15
WW17 ACRN Debug Tool YIN, Fengwei 4/22
WW18 I2C mediator introduction CHEN, Conghui 4/29
WW19 USB mediator Introduction LIU, Long 5/6
WW20 Meta-ACRN project introduction Saini, Naveen Kumar 5/13
WW21 GVT-d Overview ZHAO, Yakui 5/20
WW22 GPIO mediator introduction LIU, Long 5/27
WW23 CPU sharing – framework LIU, Shuo 6/3
WW24 ACRN 2.0 architecture introduction CHEN, Jason 6/10
WW25 ACRN 2.0 power management introduction Yin, Fengwei 6/17
WW26 ACRN secure boot Wu, Binbin 6/23
Marketing/Events
  1. N/A
    2.
Resources
  1. Project URL: 
    2.
  1. Portal: https://projectacrn.org   
  2. Source code: https://github.com/projectacrn   
  3. email: info@... 
  4. Technical Mailing list: acrn-dev@... 
    5.
========================
 

PDF
WW25‘20 ACRN2.0 Power Management.pdf

2020 ACRN Project Technical Community Meeting (2020/1~2020/7): @ Weekly Wednesday 4PM (China-Shanghai), Wednesday 9AM (Europe-London), Tuesday 0AM (US-West Coast),

Wang, Hongbo
 

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:
WW Topic Presenter Status
WW03 Expose and pass through platform hidden PCIs devices to SOS LI, Fei 1/15
WW08 EtherCAT 101 MAO, Junjie 2/19
WW09 How to build a Yocto based SOS on ACRN LIU, Fuzhong 2/26
WW10 CPU Sharing - BVT scheduler in ACRN Hypervisor CHEN, Conghui 3/4
WW11 ACRN Hypervisor Introduction CHEN, Jason 3/11
WW12 ACRN Configuration: scenarios and config tool SUN, Victor 3/18
WW13 ACRN Device Model Architecture Introduction LIU, Yuan 3/25
WW11 SR-IOV on ACRN LIU, Yuan 4/8
WW14 CSME virtualization Tomas 4/1
WW15 ACRN device passthrough overall introduction WU, Binbin 4/8
WW16 ACRN Debug Tool YIN, Fengwei 4/15
WW17 CPU Virtualization WU, Binbin 4/22
WW18 I2C mediator introduction CHEN, Conghui 4/29
WW19 USB Meditator LIU, Long 5/6
WW20 Meta-ACRN project introduction Saini, Naveen Kumar 5/13
WW21 GVT-d Overview ZHAO, Yakui 5/20
WW22 GPIO mediator introduction LIU, Long 5/27
WW23 CPU sharing – framework LIU, Shuo 6/3
WW24 ACRN v2.0 architecture introduction CHEN, Jason 6/10
WW25 ACRN secure boot WU, Binbin 6/17
WW26 ACRN and VMs Sx sates handling YIN, Fengwei 6/23
 
 
 
 
 
Project ACRN: A flexible, light-weight, open source reference hypervisor for IoT devices
 
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:
  • Meets every Wednesday, Starting Nov 07, 2018: 11AM-12AM (China-Shanghai), 7PM-8PM (US-West Coast), 3AM-4AM (Europe-London)
  • Chairperson: Hongbo Wang, hongbo.wang@... (Intel)
  • Online conference link: https://zoom.com.cn/j/320664063
  • Zoom Meeting ID: 320 664 063
  • Special Notes: If you have Zoom connection issue by using web browser, please launch Zoom application, manually input the meeting ID (320664063) to join the Zoom meeting.
  • Online conference phone:
    •
  • China: +86 010 87833177  or 400 669 9381 (Toll Free)
  • Germany: +49 (0) 30 3080 6188  or +49 800 724 3138 (Toll Free)
  • US: +1 669 900 6833  or +1 646 558 8656   or +1 877 369 0926 (Toll Free) or +1 855 880 1246 (Toll Free)
  • Additional international phone numbers
    •
  • Meeting Notes:
    •
 
 
Best regards.
Hongbo
Tel: +86-21-6116 7445
MP: +86-1364 1793 689
 

Calendar

2020 ACRN Project Technical Community Meeting Minutes - WW24'20

Zou, Terry
 

ACRN Project TCM - 10rd Jun 2020
Location
  1. Online by Zoom: https://zoom.com.cn/j/320664063   
    2.
Attendees (Total 39, 10/6)
 
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
  1. ACRN project update
    2.
N/A 
 
  1. ““ACRN 2.0 Architecture Introduction” by CHEN, Jason
    2.
Download foil from ACRN Presentation->WW24’20
Description: ACRN 2.0 quick introduction, we will give a quick go through for ACRN 2.0 architecture and basic knowledge.
 
  1. All: Community open discussion.
    2.
Q&A: 
Q1:  Both ACRN 1.0/2.0, there is a default assignment/config of CPU cores for each VM. 
Q2: Is it possible to launch 2 pre-launched VM: there are 2 pre-launched VMs(Safety WM and QM Linux VM) in partition mode, 2 pre-launched RT VM is under discussion.
Q3: The ratio of high severity VM to reboot low severity VM: if high severity VM e.g., RTVM observes some HW issues, may reboot low severity VM also.
Q4: By introducing Pre-launch Safety VM, is there any interaction between safety OS and SOS/UOS for monitoring purposes for example ? I understand that pre-launch and post launch are isolated in regards to boot flows and device assignment. But Is there interaction between pre-launch and SOS other than that ? 
A: vUART is an example stack to communicate between safety OS and SOS->UOS. Safety VM(high severity VM) wants to shutdown/reboot other(low severity) VMs.
Q5: How do we deny SOS access to RTVM (post launch) when SOS owns the DM ?In regards to memory.
A: Yes, SOS is not allowed to access RTVM’s memory when RTVM is running, but only one exception: shared queue buffer for virtio device.
 
  1. Next meeting agenda proposal:
    2.
WW Topic Presenter Status
WW03 Expose and pass through platform hidden PCIs devices to SOS LI, Fei 1/15
WW08 EtherCAT 101 MAO, Junjie 2/18
WW09 How to build a Yocto based SOS on ACRN LIU, Fuzhong 2/26
WW10 CPU Sharing - BVT scheduler in ACRN Hypervisor CHEN, Conghui 3/4
WW11 ACRN Hypervisor Introduction CHEN, Jason 3/11
WW12 ACRN Configuration: scenarios and config tool SUN, Victor 3/18
WW13 ACRN Device Model Architecture Introduction LIU, Yuan 3/25
WW14 SR-IOV on ACRN LIU, Yuan 4/1
WW15 CSME virtualization Tomas 4/8
WW16 ACRN device passthrough overall introduction WU, Binbin 4/15
WW17 ACRN Debug Tool YIN, Fengwei 4/22
WW18 I2C mediator introduction CHEN, Conghui 4/29
WW19 USB mediator Introduction LIU, Long 5/6
WW20 Meta-ACRN project introduction Saini, Naveen Kumar 5/13
WW21 GVT-d Overview ZHAO, Yakui 5/20
WW22 GPIO mediator introduction LIU, Long 5/27
WW23 CPU sharing – framework LIU, Shuo 6/3
WW24 ACRN 2.0 architecture introduction CHEN, Jason 6/10
WW25 ACRN secure boot WU, Binbin 6/17
WW26 ACRN and VMs Sx states handling YIN, Fengwei 6/23
Marketing/Events
  1. N/A
    2.
Resources
  1. Project URL: 
    2.
  1. Portal: https://projectacrn.org   
  2. Source code: https://github.com/projectacrn   
  3. email: info@... 
  4. Technical Mailing list: acrn-dev@... 
    5.
 
========================
 
 

PDF
WW24‘20 ACRN 2.0 Architecture Introduction.pdf

2020 ACRN Project Technical Community Meeting Minutes - WW23'20

Zou, Terry
 

ACRN Project TCM - 3rd Jun 2020
Location
  1. Online by Zoom: https://zoom.com.cn/j/320664063   
    2.
Attendees (Total 30, 3/6)
 
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
  1. ACRN project update
    2.
N/A 
 
  1. “ACRN CPU Sharing Scheduler Framework Introduction” by LIU, Shuo
    2.
Download foil from ACRN Presentation->WW23’20
Description: ACRN scheduler framework introduction. We will talk about the goal of CPU sharing and architecture of scheduling system in the ACRN hypervisor. And also have a discussion about physical CPU assignment for each VM.
 
  1. All: Community open discussion.
    2.
Q&A: 
Q1:  Pre-defined CPU affinity for VM1(waag) and VM2(RT linux), and could be changed in launch script.
Q2:  For priority of pCPU0/1 for SOS+waag, there is weight to set priority with BVT scheduler.
 
  1. Next meeting agenda proposal:
    2.
WW Topic Presenter Status
WW03 Expose and pass through platform hidden PCIs devices to SOS LI, Fei 1/15
WW08 EtherCAT 101 MAO, Junjie 2/18
WW09 How to build a Yocto based SOS on ACRN LIU, Fuzhong 2/26
WW10 CPU Sharing - BVT scheduler in ACRN Hypervisor CHEN, Conghui 3/4
WW11 ACRN Hypervisor Introduction CHEN, Jason 3/11
WW12 ACRN Configuration: scenarios and config tool SUN, Victor 3/18
WW13 ACRN Device Model Architecture Introduction LIU, Yuan 3/25
WW14 SR-IOV on ACRN LIU, Yuan 4/1
WW15 CSME virtualization Tomas 4/8
WW16 ACRN device passthrough overall introduction WU, Binbin 4/15
WW17 ACRN Debug Tool YIN, Fengwei 4/22
WW18 I2C mediator introduction CHEN, Conghui 4/29
WW19 USB mediator Introduction LIU, Long 5/6
WW20 Meta-ACRN project introduction Saini, Naveen Kumar 5/13
WW21 GVT-d Overview ZHAO, Yakui 5/20
WW22 GPIO mediator introduction LIU, Long 5/27
WW23 CPU sharing – framework LIU, Shuo 6/3
WW24 ACRN security related features and roadmap CHEN, Jason 6/10
WW25 ACRN secure boot WU, Binbin 6/17
WW26 ACRN and VMs Sx states handling YIN, Fengwei 6/23
Marketing/Events
  1. N/A
    2.
Resources
  1. Project URL: 
    2.
  1. Portal: https://projectacrn.org   
  2. Source code: https://github.com/projectacrn   
  3. email: info@... 
  4. Technical Mailing list: acrn-dev@... 
    5.
 
========================
 
 

PDF
WW23‘20 ACRN Scheduler Framework Introduction.pdf

Re: Debugging the UOS

steven.l.wang@...
 

1. Currently, Zephyr does not support kgdb.
2. If you want to debug UOS with gdb server, I guess that support for gdb server has to ben added in ACRN. 
    - Gdb server can be used to debug zephyr running with qemu. It is because qemu supports gdb server. So, similarly,  gdb server support needs to be enabled in ACRN. 
2020 ACRN Project Technical Community Meeting Minutes - WW22'20

Zou, Terry
 

ACRN Project TCM - 27th May 2020
Location
  1. Online by Zoom: https://zoom.com.cn/j/320664063   
    2.
Attendees (Total 33, 20/5)
 
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
  1. ACRN project update
    2.
N/A 
 
  1. “ACRN GPIO Meditator Introduction” by LIU, Long
    2.
Download foil from ACRN Presentation->ACRN_TCM->WW22’20
Description: ACRN GPIO Meditator Introduction, we will introduce GPIO virtualization on ACRN, including GPIO concept, GPIO virtualization design, architecture and GPIO IRQ virtualization implementation.
 
  1. All: Community open discussion.
    2.
Q&A: 
Q1: There is a virtual ACPI table in each User OS, which was created by ACRN device model. ARCN device model will also host physical GPIO and Virtual GPIO mapping table.
 
  1. Next meeting agenda proposal:
    2.
 
WW Topic Presenter Status
WW03 Expose and pass through platform hidden PCIs devices to SOS LI, Fei 1/15
WW08 EtherCAT 101 MAO, Junjie 2/18
WW09 How to build a Yocto based SOS on ACRN LIU, Fuzhong 2/26
WW10 CPU Sharing - BVT scheduler in ACRN Hypervisor CHEN, Conghui 3/4
WW11 ACRN Hypervisor Introduction CHEN, Jason 3/11
WW12 ACRN Configuration: scenarios and config tool SUN, Victor 3/18
WW13 ACRN Device Model Architecture Introduction LIU, Yuan 3/25
WW14 SR-IOV on ACRN LIU, Yuan 4/1
WW15 CSME virtualization Tomas 4/8
WW16 ACRN device passthrough overall introduction WU, Binbin 4/15
WW17 ACRN Debug Tool YIN, Fengwei 4/22
WW18 I2C mediator introduction CHEN, Conghui 4/29
WW19 USB mediator Introduction LIU, Long 5/6
WW20 Meta-ACRN project introduction Saini, Naveen Kumar 5/13
WW21 GVT-d Overview ZHAO, Yakui 5/20
WW22 GPIO mediator introduction LIU, Long 5/27
WW23 CPU sharing – framework LIU, Shuo 6/3
WW24 ACRN security related features and roadmap CHEN, Jason 6/10
WW25 ACRN secure boot WU, Binbin 6/17
WW26 ACRN and VMs Sx states handling YIN, Fengwei 6/23
Marketing/Events
  1. N/A
    2.
Resources
  1. Project URL: 
    2.
  1. Portal: https://projectacrn.org   
  2. Source code: https://github.com/projectacrn   
  3. email: info@...g 
  4. Technical Mailing list: acrn-dev@...g 
    5.
 
========================
 
 

PDF
WW22‘20 ACRN GPIO Mediator Introduction.pdf

Re: Debugging the UOS

Tomasz Bursztyka
 

Hi Fengwei,

Zephyr does not support kgdb no.

About the RT, I need it because currently only LOAPIC timer works
properly in Zephyr on top of ACRN and thus requires the loapic pass-
through.

Best regards,

Tomasz

Hi Tomasz,

On Tue, 26 May 2020 09:09:20 +0200
Tomasz Bursztyka <tomasz.bursztyka@...> wrote:

Hi,

So as the title says I am bit stuck on how to debug a UOS
efficiently.

I could not find a way to get a gdb server available for the
UOS, besides for linux which requires to be built with kgdb support
if
I understood well(?).

But I am running zephyr as UOS.
And using only printk() is a no go, not because it's the poor man's
solution but because when the vm crashes, I will not be able to
stop
it with acrn-dm (even with -f). The only way to recover is to
reboot
the entire setup (acrn runs on up squared). It takes then a lot of
time, too much time in fact.

What would be a better method?
My understanding is that you want to debug UOS (which is zephyr)
itself.
There are two thing need check:
1. Whether zephyr could support kgdb like debug methodology?
2. If it could, because the limitation that ACRN doesn't support
hardware debugging register, only software breakpoint could be
used.

Talking about UOS can't be stopped, if you doesn't care real time
performance (I suppose this is likely true), you can start zephyr as
standard guest. Then you could try to kill acrn-dm to restart UOS.
If you want to shutdown it. a minor change to acrn-dm could achieve
that.


Regards
Yin, Fengwei

Br,

Tomasz
Re: Debugging the UOS

Yin, Fengwei <fengwei.yin@...>
 

Hi Tomasz,

On Tue, 26 May 2020 09:09:20 +0200
Tomasz Bursztyka <tomasz.bursztyka@...> wrote:

Hi,

So as the title says I am bit stuck on how to debug a UOS efficiently.

I could not find a way to get a gdb server available for the
UOS, besides for linux which requires to be built with kgdb support if
I understood well(?).

But I am running zephyr as UOS.
And using only printk() is a no go, not because it's the poor man's
solution but because when the vm crashes, I will not be able to stop
it with acrn-dm (even with -f). The only way to recover is to reboot
the entire setup (acrn runs on up squared). It takes then a lot of
time, too much time in fact.

What would be a better method?
My understanding is that you want to debug UOS (which is zephyr) itself.
There are two thing need check:
1. Whether zephyr could support kgdb like debug methodology?
2. If it could, because the limitation that ACRN doesn't support
hardware debugging register, only software breakpoint could be used.

Talking about UOS can't be stopped, if you doesn't care real time
performance (I suppose this is likely true), you can start zephyr as
standard guest. Then you could try to kill acrn-dm to restart UOS.
If you want to shutdown it. a minor change to acrn-dm could achieve
that.


Regards
Yin, Fengwei


Br,

Tomasz
501 - 520 of 1205