Hi Alfonso Please share your acrn.efi and acrn-dm, will reproduce this issue on our side. Thanks! BR. Fuzhong

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

Hi Steve, Please disable Hyper thread in BIOS for workaround. This issue is fixed in v1.5; will release soon. BR. Fuzhong

Hi, Am essentially following the deployment instructions for the ACRN industry scenario using a NUC7i7DNH with a serial port

Hi Liu, 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

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

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

<Detailed calendar will be published1 week before meeting> Project ACRN: A flexible, light-weight, opensource reference hypervisor for IoT devices https://projectacrn.org ||

<Cancel WW52 meeting due to Christmas Holiday> Project ACRN: A flexible, light-weight, opensource reference hypervisor for IoT devices https://projectacrn.org || https://github.com/projectacrn ||

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

ACRN Project TCM – 18Th Dec 2019 Meeting Achieves: Google doc: https://drive.google.com/drive/u/2/folders/111m6iU3PjSZebOOKzLagYPUWMvseGLeU Agenda ACRN project update The online meeting

<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

ACRN Project TCM – 11Th Dec 2019 Location Zoom: https://zoom.us/j/457171121 Agenda ACRN project update “How to use configuration tool to deploy ACRN on new platform” by ZHENG, Shuang Download

<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

Meeting Minutes archive: https://drive.google.com/drive/u/2/folders/111m6iU3PjSZebOOKzLagYPUWMvseGLeU Meeting foils archive:

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 introduceACRN's

Agree, we should avoid maxcpus setting. 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

Is 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

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

Thanks Fuzhong to correct my misunderstanding! BR, Victor