1. Acrn-Users
  2. Messages

Expanded

Topics Messages Polls
   Date   
Re: HPET and IRQs

Geoffroy Van Cutsem
 

-----Original Message-----
From: acrn-users@... <acrn-users@...>
On Behalf Of Yan, Like
Sent: Wednesday, April 29, 2020 5:24 PM
To: acrn-users@...
Subject: Re: [acrn-users] HPET and IRQs

Hi Tomasz,

If you launched VM with --lapic_pt, then it's a RT VM.
An RT VM is only allowed to be powered-off/reset when initiated inside the
RT VM. The design principle here is that the other VMs (even the SOS VM)
should not interfere RT VM to guarantee the RT performance.
And there are some limitations as to RT VM, legacy devices are not
supported, such as vHPET.
Here are 2 documents for RT VM:
https://projectacrn.github.io/latest/tutorials/rtvm_workload_design_guideli
ne.html
https://projectacrn.github.io/latest/tutorials/rtvm_performance_tips.html
Thanks for the information Like. I was suspecting this but couldn't find a good reference about this in our documentation. The couple of documents you referenced above provide some good background information and useful tips on how to run RTVMs on ACRN. It does not really talk about what this limitation for example. It would be great to have some High-Level Design Guide that talk more extensively about the different types of User VMs: i.e. pre-launched, post-launched and RTVM vs. "normal" User VMs.

Is this something we can plan to add?

Thanks,
Geoffroy



Thanks,
Like

-----Original Message-----
From: acrn-users@...
<acrn-users@...> On Behalf Of Tomasz Bursztyka
Sent: Wednesday, April 29, 2020 2:37 PM
To: acrn-users@...
Subject: Re: [acrn-users] HPET and IRQs

Hi Like,

VM or RT VM, I don't know. It did not occur to me there was an actual
difference, I just used the launcher script for zephyr. I'll check.

I could get LAPIC (which we indeed call LOAPIC) to work using --
lapic_pt option to acrn-dm. But then I am unable to stop/reset/delete
the VM for some reason (even with --force on stop, it always returns -1).

I'll still investigate about HPET. It "should" work, and if Zephyr is
missing some support - runtime calibration that is - then it will be worth
adding it.

Thanks for the inputs,

Tomasz
Re: HPET and IRQs

Yan, Like
 

Hi Tomasz,

If you launched VM with --lapic_pt, then it's a RT VM.
An RT VM is only allowed to be powered-off/reset when initiated inside the RT VM. The design principle here is that the other VMs (even the SOS VM) should not interfere RT VM to guarantee the RT performance.
And there are some limitations as to RT VM, legacy devices are not supported, such as vHPET.
Here are 2 documents for RT VM:
https://projectacrn.github.io/latest/tutorials/rtvm_workload_design_guideline.html
https://projectacrn.github.io/latest/tutorials/rtvm_performance_tips.html

Thanks,
Like

-----Original Message-----
From: acrn-users@... <acrn-users@...> On
Behalf Of Tomasz Bursztyka
Sent: Wednesday, April 29, 2020 2:37 PM
To: acrn-users@...
Subject: Re: [acrn-users] HPET and IRQs

Hi Like,

VM or RT VM, I don't know. It did not occur to me there was an actual
difference, I just used the launcher script for zephyr. I'll check.

I could get LAPIC (which we indeed call LOAPIC) to work using -- lapic_pt
option to acrn-dm. But then I am unable to stop/reset/delete the VM for
some reason (even with --force on stop, it always returns -1).

I'll still investigate about HPET. It "should" work, and if Zephyr is missing
some support - runtime calibration that is - then it will be worth adding it.

Thanks for the inputs,

Tomasz
2020 ACRN Project Technical Community Meeting Minutes - WW18'20

Zou, Terry
 

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.
Zoom connection is not stable recently, sorry for the network issue during today’s meeting. If anybody have similar Zoom connection issue or good suggestion for alternative tools, feel free to discuss in mailing list, thanks.
ACRN Project TCM - 29th Apr 2020
Location
Attendees (Total 30, 29/4)
Note: If 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 
N/A
 
  1. “I2C Mediator Introduction” by CHEN, Conghui
    2.
Download foil from ACRN Presentation->ACRN_TCM->WW18’20
Description: ACRN virtio-i2c introduction, we will talk about the background and architecture of virtio-i2c. Give brief introduce to virtio-i2c FE and BE implementation. Talk about the virtqueue used by virtio-i2c.
 
  1. All: Community open discussion.
Q&A: 
Q1: Guest can only dump i2c resources assigned to this guest.
 
  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 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 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.
 
========================
 

WW18‘20 ACRN I2C Mediator Introduction.pdf

WW18‘20 ACRN I2C Mediator Introduction.pdf

Re: Issue on latest Clear Linux and ACRN on UP2 board

Geoffroy Van Cutsem
 

-----Original Message-----
From: acrn-users@... <acrn-users@...>
On Behalf Of Tomasz Bursztyka
Sent: Tuesday, April 28, 2020 1:33 PM
To: acrn-users@...
Subject: Re: [acrn-users] Issue on latest Clear Linux and ACRN on UP2 board

Hi,

I think this has to do with the UP2 UEFI firmware, it gives me problem
on my UP2 board. I could never figure out what sequence of commands
would reliably set the boot order correctly but I also very often see
that setting a new entry with efibootmgr looks alright, until you
reboot and the boot order was changed (I suspect by the firmware
itself). It seems that I have had better luck with adding a new boot
entry *and* changing the boot order (efibootmgr -o).

Net net, your installation is most likely just fine but you're dealing
with a capricious EFI firmware.
Good to know I am not the only one who got this issue.

Maybe it would be worth mentioning it in the up2 doc section of acrn then.
I agree, I thought it was mainly my board up until now but I have had similar reports from others since then. I've added a note (PR still pending): https://github.com/projectacrn/acrn-hypervisor/pull/4747

Geoffroy


Tomasz
Re: HPET and IRQs

Chen, Zide
 

Hi Tomasz,

Additional to Like's comments, to calibrate the timer, if you have serial HV console, you can get the TSC frequency from the log. For example:
calibrate_tsc, tsc_khz=1593600

Then you need to change the Zephyr code accordingly. In this example, set CONFIG_SYS_CLOCK_HW_CYCLES_PER_SEC=1593600000
https://github.com/zephyrproject-rtos/zephyr/blob/master/boards/x86/acrn/acrn_defconfig#L13

Best Regards,
Zide

-----Original Message-----
From: acrn-users@... <acrn-users@...> On Behalf Of Tomasz Bursztyka
Sent: Tuesday, April 28, 2020 5:19 AM
To: acrn-users@...
Subject: [acrn-users] HPET and IRQs

Hi,

I am currently trying to fix an issue with Zephyr running as UOS.

The default configuration of Zephyr for acrn enables the LOAPIC timer,
but there does not seem to be any mention of such timer in acrn. Unless
I am missing something.
When running zephyr with such timer, the timing get all bogus. 60
seconds looks like 5 seconds, etc... Timings are all off.

As HPET is supported by acrn, I switched the timer to HPET. But now I
have a new issue, acrn-dm displays:

hpet t0 configured invalid irq 2, allowed_irqs 0xff000000

And nothing proceeds, since acrn defaults to 0, zephyr isr for hpet is
never called.

Indeed Zephyr sets HPET IRQ to 2, which seems to be wrong then for acrn
.

Which IRQ should HPET timer be configured to use on UOS side then?


Thanks,

Tomasz
Re: HPET and IRQs

Tomasz Bursztyka
 

Hi Like,

VM or RT VM, I don't know. It did not occur to me there was an actual
difference, I just used the launcher script for zephyr. I'll check.

I could get LAPIC (which we indeed call LOAPIC) to work using --
lapic_pt option to acrn-dm. But then I am unable to stop/reset/delete
the VM for some reason (even with --force on stop, it always returns
-1).

I'll still investigate about HPET. It "should" work, and if Zephyr is
missing some support - runtime calibration that is - then it will be
worth adding it.

Thanks for the inputs,

Tomasz
Re: HPET and IRQs

Yan, Like
 

Hi Tomasz,

Please find my response inline.
One question, are you running Zephyr on standard VM or RT VM?

Thanks,
Like

-----Original Message-----
From: acrn-users@... <acrn-users@...> On
Behalf Of Tomasz Bursztyka
Sent: Tuesday, April 28, 2020 8:19 PM
To: acrn-users@...
Subject: [acrn-users] HPET and IRQs

Hi,

I am currently trying to fix an issue with Zephyr running as UOS.

The default configuration of Zephyr for acrn enables the LOAPIC timer, but
there does not seem to be any mention of such timer in acrn. Unless I am
missing something.
[Like] LOAPIC is short for local APIC, right? In ACRN, we use LAPIC instead.

When running zephyr with such timer, the timing get all bogus. 60 seconds
looks like 5 seconds, etc... Timings are all off.
[Like] As I know, zephyr won't do runtime timer calibration. You may need to do the calibration manually, and update the code to the correct timer frequency.


As HPET is supported by acrn, I switched the timer to HPET. But now I have a
new issue, acrn-dm displays:

hpet t0 configured invalid irq 2, allowed_irqs 0xff000000

And nothing proceeds, since acrn defaults to 0, zephyr isr for hpet is never
called.

Indeed Zephyr sets HPET IRQ to 2, which seems to be wrong then for acrn .

Which IRQ should HPET timer be configured to use on UOS side then?
[Like] HPET may use IRQ 24~31. As well, HPET calibration is needed, so we recommend you to use the LAPIC timer.




Thanks,

Tomasz
HPET and IRQs

Tomasz Bursztyka
 

Hi,

I am currently trying to fix an issue with Zephyr running as UOS.

The default configuration of Zephyr for acrn enables the LOAPIC timer,
but there does not seem to be any mention of such timer in acrn. Unless
I am missing something.
When running zephyr with such timer, the timing get all bogus. 60
seconds looks like 5 seconds, etc... Timings are all off.

As HPET is supported by acrn, I switched the timer to HPET. But now I
have a new issue, acrn-dm displays:

hpet t0 configured invalid irq 2, allowed_irqs 0xff000000

And nothing proceeds, since acrn defaults to 0, zephyr isr for hpet is
never called.

Indeed Zephyr sets HPET IRQ to 2, which seems to be wrong then for acrn
.

Which IRQ should HPET timer be configured to use on UOS side then?


Thanks,

Tomasz
Re: Issue on latest Clear Linux and ACRN on UP2 board

Tomasz Bursztyka
 

Hi,

I think this has to do with the UP2 UEFI firmware, it gives me
problem on my UP2 board. I could never figure out what sequence of
commands would reliably set the boot order correctly but I also very
often see that setting a new entry with efibootmgr looks alright,
until you reboot and the boot order was changed (I suspect by the
firmware itself). It seems that I have had better luck with adding a
new boot entry *and* changing the boot order (efibootmgr -o).

Net net, your installation is most likely just fine but you're
dealing with a capricious EFI firmware.
Good to know I am not the only one who got this issue.

Maybe it would be worth mentioning it in the up2 doc section of acrn
then.

Tomasz
Re: Issue on latest Clear Linux and ACRN on UP2 board

Tomasz Bursztyka
 

Hi Tonny,


Your `efibootmgr -v` output indicates the #3 entry will be picked up
first, which is the fall back boot entry for Systemd-boot. Please
change the order with `efibootmgr -o` option. You should also enter
the UP2 BIOS to make sure the ACRN boot entry is the first option.
I did that already and did not work (see my original post), the working
trick was to disable the boot entry 0003.

Tomasz
Re: Issue on latest Clear Linux and ACRN on UP2 board

Geoffroy Van Cutsem
 

I think this has to do with the UP2 UEFI firmware, it gives me problem on my UP2 board. I could never figure out what sequence of commands would reliably set the boot order correctly but I also very often see that setting a new entry with efibootmgr looks alright, until you reboot and the boot order was changed (I suspect by the firmware itself). It seems that I have had better luck with adding a new boot entry *and* changing the boot order (efibootmgr -o).

Net net, your installation is most likely just fine but you're dealing with a capricious EFI firmware.

Geoffroy

-----Original Message-----
From: acrn-users@... <acrn-users@...>
On Behalf Of Tzeng, Tonny
Sent: Tuesday, April 28, 2020 11:34 AM
To: acrn-users@...
Subject: Re: [acrn-users] Issue on latest Clear Linux and ACRN on UP2 board

Hi Tomasz,

Your `efibootmgr -v` output indicates the #3 entry will be picked up first,
which is the fall back boot entry for Systemd-boot. Please change the order
with `efibootmgr -o` option. You should also enter the UP2 BIOS to make
sure the ACRN boot entry is the first option.

Regards,
Tonny

-----Original Message-----
From: acrn-users@... <acrn-users@...>
On Behalf Of Tomasz Bursztyka
Sent: Tuesday, April 28, 2020 3:14 PM
To: acrn-users@...
Subject: [acrn-users] Issue on latest Clear Linux and ACRN on UP2 board

Hi,

I cannot get ACRN hypervisor running on my setup:
- UP² board (Celeron N3350)
- Clear Linux, fresh install, version 32910

I followed the documentation here:
- https://projectacrn.github.io/latest/tutorials/up2.html
- https://projectacrn.github.io/latest/tutorials/kbl-nuc-sdc.html


However, once I rebooted I did not get the kernel message
[ 0.000000] Hypervisor detected: ACRN

I only get these:
[ 5.759483] ACRNTrace: acrn_trace: not support acrn hypervisor!
[ 5.766132] ACRN HVLog: acrn_hvlog: not running under acrn
hypervisor!

So the hypervisor is not running.
There is no acrn related devices in /dev, I cannot start any VM obviously etc..

Here is the kernel cmd line:

[ 0.000000] Command line: initrd=\EFI\org.clearlinux\freestanding-
00-intel-ucode.cpio initrd=\EFI\org.clearlinux\freestanding-i915-
firmware.cpio.xz root=PARTUUID=05e27678-99d6-4bed-bbbe-d28cb026566a
quiet console=tty0 console=ttyS0,115200n8 consoleblank=0
cryptomgr.notests hvlog=2M@0x1FE00000
i915.avail_planes_per_pipe=0x01010F
i915.domain_plane_owners=0x011111110000 i915.enable_guc=0
i915.enable_gvt=1 i915.nuclear_pageflip=1 ignore_loglevel
init=/usr/lib/systemd/systemd-bootchart intel_iommu=igfx_off
memmap=2M$0x1FE00000 no_timer_check no_timer_check noreplace-smp
rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs
rootwait tsc=reliable rw


The EFI configuration seems legit, however:

# efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0005,0001
Boot0001 UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-
a648-bd47664c8012)..BO
Boot0003* UEFI OS HD(1,GPT,f2d8aada-01a9-4c9c-86fe-
61ccb217e678,0x800,0x47000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0005* ACRN Hypervisor HD(1,GPT,f2d8aada-01a9-4c9c-86fe-
61ccb217e678,0x800,0x47000)/File(\EFI\ACRN\ACRN.EFI)b.o.o.t.l.o.a.d.e.r
.=.\.E.F.I.\.o.r.g...c.l.e.a.r.l.i.n.u.x.\.b.o.o.t.l.o.a.d.e.r.x.6.4...
e.f.i. .u.a.r.t.=.b.d.f.@.0.:.1.8...1.


I switched the order to 0005,0003,0001 but it made no difference, and once I
did: the bootorder had automaticaly changed back to 0003,0005,0001. Is this
nominal?

The acrn.efi is from acrn_quick_setup.sh, which requested to do:

cp /usr/lib/acrn/acrn.nuc7i7dnb.industry.efi /usr/lib/acrn/acrn.up-
apl01.industry.efi

So I did. (and installation seemed to go well.)


Any idea where the problem could be?
Re: Issue on latest Clear Linux and ACRN on UP2 board

Tzeng, Tonny <tonny.tzeng@...>
 

Hi Tomasz,

Your `efibootmgr -v` output indicates the #3 entry will be picked up first, which is the fall back boot entry for Systemd-boot. Please change the order with `efibootmgr -o` option. You should also enter the UP2 BIOS to make sure the ACRN boot entry is the first option.

Regards,
Tonny

-----Original Message-----
From: acrn-users@... <acrn-users@...> On Behalf Of Tomasz Bursztyka
Sent: Tuesday, April 28, 2020 3:14 PM
To: acrn-users@...
Subject: [acrn-users] Issue on latest Clear Linux and ACRN on UP2 board

Hi,

I cannot get ACRN hypervisor running on my setup:
- UP² board (Celeron N3350)
- Clear Linux, fresh install, version 32910

I followed the documentation here:
- https://projectacrn.github.io/latest/tutorials/up2.html
- https://projectacrn.github.io/latest/tutorials/kbl-nuc-sdc.html


However, once I rebooted I did not get the kernel message
[ 0.000000] Hypervisor detected: ACRN

I only get these:
[ 5.759483] ACRNTrace: acrn_trace: not support acrn hypervisor!
[ 5.766132] ACRN HVLog: acrn_hvlog: not running under acrn
hypervisor!

So the hypervisor is not running.
There is no acrn related devices in /dev, I cannot start any VM obviously etc..

Here is the kernel cmd line:

[ 0.000000] Command line: initrd=\EFI\org.clearlinux\freestanding-
00-intel-ucode.cpio initrd=\EFI\org.clearlinux\freestanding-i915-
firmware.cpio.xz root=PARTUUID=05e27678-99d6-4bed-bbbe-d28cb026566a
quiet console=tty0 console=ttyS0,115200n8 consoleblank=0 cryptomgr.notests hvlog=2M@0x1FE00000 i915.avail_planes_per_pipe=0x01010F
i915.domain_plane_owners=0x011111110000 i915.enable_guc=0
i915.enable_gvt=1 i915.nuclear_pageflip=1 ignore_loglevel init=/usr/lib/systemd/systemd-bootchart intel_iommu=igfx_off
memmap=2M$0x1FE00000 no_timer_check no_timer_check noreplace-smp
rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs rootwait tsc=reliable rw


The EFI configuration seems legit, however:

# efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0005,0001
Boot0001 UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-
a648-bd47664c8012)..BO
Boot0003* UEFI OS HD(1,GPT,f2d8aada-01a9-4c9c-86fe-
61ccb217e678,0x800,0x47000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0005* ACRN Hypervisor HD(1,GPT,f2d8aada-01a9-4c9c-86fe-
61ccb217e678,0x800,0x47000)/File(\EFI\ACRN\ACRN.EFI)b.o.o.t.l.o.a.d.e.r
.=.\.E.F.I.\.o.r.g...c.l.e.a.r.l.i.n.u.x.\.b.o.o.t.l.o.a.d.e.r.x.6.4...
e.f.i. .u.a.r.t.=.b.d.f.@.0.:.1.8...1.


I switched the order to 0005,0003,0001 but it made no difference, and once I did: the bootorder had automaticaly changed back to 0003,0005,0001. Is this nominal?

The acrn.efi is from acrn_quick_setup.sh, which requested to do:

cp /usr/lib/acrn/acrn.nuc7i7dnb.industry.efi /usr/lib/acrn/acrn.up- apl01.industry.efi

So I did. (and installation seemed to go well.)


Any idea where the problem could be?
Re: Issue on latest Clear Linux and ACRN on UP2 board

Liu, Fuzhong
 

Hi Tomasz,

After UP2 boot up with native, Could you please try following command with uart disabled first?

sudo efibootmgr -c -l "\EFI\acrn\acrn.efi" -d /dev/mmcblk0-p 1 -L "ACRN Hypervisor UP2" -u "bootloader=\EFI\org.clearlinux\bootloaderx64.efi uart=disabled "

 

Thanks!

 

BR.

Fuzhong

 

From: acrn-users@... <acrn-users@...> On Behalf Of Yin, Fengwei
Sent: Tuesday, April 28, 2020 3:45 PM
To: acrn-users@...
Subject: Re: [acrn-users] Issue on latest Clear Linux and ACRN on UP2 board

 

Hi Tomasz,

On 4/28/20 3:40 PM, Tomasz Bursztyka wrote:

Hi,
 
 
However, once I rebooted I did not get the kernel message
[    0.000000] Hypervisor detected: ACRN
 
I only get these:
[    5.759483] ACRNTrace: acrn_trace: not support acrn hypervisor!
[    5.766132] ACRN HVLog: acrn_hvlog: not running under acrn
hypervisor!
 
    
 
    
This means you boot sos kernel directly without ACRN.
 
That I figured out already yes.
 
But why? (installer did not show any issue, the only thing which seems
suspicious is the EFI bootorder as I described)
And how to fix this?

Not sure whether you are familiar with EFI shell. If yes, can you

try to load acrn.efi from EFI shell? That make sure the ACRN is

loaded.

 

Regards

Yin, Fengwei

 

 
 
Thanks,
 
Tomasz
 
 
 
 
Re: Issue on latest Clear Linux and ACRN on UP2 board

Tomasz Bursztyka
 

Hi,

suspicious is the EFI bootorder as I described)
And how to fix this?
Not sure whether you are familiar with EFI shell. If yes, can you

try to load acrn.efi from EFI shell? That make sure the ACRN is

loaded.
Thanks for the hint.

I had no re-enable the UEFI shell boot entry. There I could try to load
acrn.efi: and it loaded well.

So that gave me an idea: I disabled the boot 0003 entirely (namely UEFI
OS, I guess it's the one installed by clear linux). Reordered to get
the entry 0005 to be the first and now it works:

[ 0.000000] Hypervisor detected: ACRN
[ 2.052220] ACRNTrace: Initialized acrn trace module with 2 cpu
[ 2.053849] ACRN HVLog: Failed to init last hvlog devs, errno -19
[ 2.054223] ACRN HVLog: Initialized hvlog module with 2 cpu


Thanks,

Tomasz
Re: Issue on latest Clear Linux and ACRN on UP2 board

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

Hi Tomasz,

On 4/28/20 3:40 PM, Tomasz Bursztyka wrote:
Hi,



However, once I rebooted I did not get the kernel message
[    0.000000] Hypervisor detected: ACRN

I only get these:
[    5.759483] ACRNTrace: acrn_trace: not support acrn hypervisor!
[    5.766132] ACRN HVLog: acrn_hvlog: not running under acrn
hypervisor!

    

    
This means you boot sos kernel directly without ACRN.

That I figured out already yes.

But why? (installer did not show any issue, the only thing which seems
suspicious is the EFI bootorder as I described)
And how to fix this?

Not sure whether you are familiar with EFI shell. If yes, can you

try to load acrn.efi from EFI shell? That make sure the ACRN is

loaded.


Regards

Yin, Fengwei



Thanks,

Tomasz

Re: Issue on latest Clear Linux and ACRN on UP2 board

Tomasz Bursztyka
 

Hi,


However, once I rebooted I did not get the kernel message
[ 0.000000] Hypervisor detected: ACRN

I only get these:
[ 5.759483] ACRNTrace: acrn_trace: not support acrn hypervisor!
[ 5.766132] ACRN HVLog: acrn_hvlog: not running under acrn
hypervisor!


This means you boot sos kernel directly without ACRN.
That I figured out already yes.

But why? (installer did not show any issue, the only thing which seems
suspicious is the EFI bootorder as I described)
And how to fix this?

Thanks,

Tomasz
Re: Issue on latest Clear Linux and ACRN on UP2 board

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


On 4/28/20 3:13 PM, Tomasz Bursztyka wrote:
Hi,

I cannot get ACRN hypervisor running on my setup: 
- UP² board (Celeron N3350)
- Clear Linux, fresh install, version 32910

I followed the documentation here: 
- https://projectacrn.github.io/latest/tutorials/up2.html
- https://projectacrn.github.io/latest/tutorials/kbl-nuc-sdc.html


However, once I rebooted I did not get the kernel message
[    0.000000] Hypervisor detected: ACRN

I only get these:
[    5.759483] ACRNTrace: acrn_trace: not support acrn hypervisor!
[    5.766132] ACRN HVLog: acrn_hvlog: not running under acrn
hypervisor!

This means you boot sos kernel directly without ACRN.


Regards

Yin, Fengwei



So the hypervisor is not running.
There is no acrn related devices in /dev, I cannot start any VM
obviously etc..

Here is the kernel cmd line:

[    0.000000] Command line: initrd=\EFI\org.clearlinux\freestanding-
00-intel-ucode.cpio initrd=\EFI\org.clearlinux\freestanding-i915-
firmware.cpio.xz root=PARTUUID=05e27678-99d6-4bed-bbbe-d28cb026566a
quiet console=tty0 console=ttyS0,115200n8 consoleblank=0
cryptomgr.notests hvlog=2M@0x1FE00000
i915.avail_planes_per_pipe=0x01010F
i915.domain_plane_owners=0x011111110000 i915.enable_guc=0
i915.enable_gvt=1 i915.nuclear_pageflip=1 ignore_loglevel
init=/usr/lib/systemd/systemd-bootchart intel_iommu=igfx_off
memmap=2M$0x1FE00000 no_timer_check no_timer_check noreplace-smp
rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs
rootwait tsc=reliable rw


The EFI configuration seems legit, however:

 # efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0005,0001
Boot0001  UEFI: Built-in EFI Shell	VenMedia(5023b95c-db26-429b-
a648-bd47664c8012)..BO
Boot0003* UEFI OS	HD(1,GPT,f2d8aada-01a9-4c9c-86fe-
61ccb217e678,0x800,0x47000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0005* ACRN Hypervisor	HD(1,GPT,f2d8aada-01a9-4c9c-86fe-
61ccb217e678,0x800,0x47000)/File(\EFI\ACRN\ACRN.EFI)b.o.o.t.l.o.a.d.e.r
.=.\.E.F.I.\.o.r.g...c.l.e.a.r.l.i.n.u.x.\.b.o.o.t.l.o.a.d.e.r.x.6.4...
e.f.i. .u.a.r.t.=.b.d.f.@.0.:.1.8...1.


I switched the order to 0005,0003,0001 but it made no difference, and
once I did: the bootorder had automaticaly changed back to
0003,0005,0001. Is this nominal? 

The acrn.efi is from acrn_quick_setup.sh, which requested to do:

cp /usr/lib/acrn/acrn.nuc7i7dnb.industry.efi /usr/lib/acrn/acrn.up-
apl01.industry.efi

So I did. (and installation seemed to go well.)


Any idea where the problem could be?

Issue on latest Clear Linux and ACRN on UP2 board

Tomasz Bursztyka
 

Hi,

I cannot get ACRN hypervisor running on my setup:
- UP² board (Celeron N3350)
- Clear Linux, fresh install, version 32910

I followed the documentation here:
- https://projectacrn.github.io/latest/tutorials/up2.html
- https://projectacrn.github.io/latest/tutorials/kbl-nuc-sdc.html


However, once I rebooted I did not get the kernel message
[ 0.000000] Hypervisor detected: ACRN

I only get these:
[ 5.759483] ACRNTrace: acrn_trace: not support acrn hypervisor!
[ 5.766132] ACRN HVLog: acrn_hvlog: not running under acrn
hypervisor!

So the hypervisor is not running.
There is no acrn related devices in /dev, I cannot start any VM
obviously etc..

Here is the kernel cmd line:

[ 0.000000] Command line: initrd=\EFI\org.clearlinux\freestanding-
00-intel-ucode.cpio initrd=\EFI\org.clearlinux\freestanding-i915-
firmware.cpio.xz root=PARTUUID=05e27678-99d6-4bed-bbbe-d28cb026566a
quiet console=tty0 console=ttyS0,115200n8 consoleblank=0
cryptomgr.notests hvlog=2M@0x1FE00000
i915.avail_planes_per_pipe=0x01010F
i915.domain_plane_owners=0x011111110000 i915.enable_guc=0
i915.enable_gvt=1 i915.nuclear_pageflip=1 ignore_loglevel
init=/usr/lib/systemd/systemd-bootchart intel_iommu=igfx_off
memmap=2M$0x1FE00000 no_timer_check no_timer_check noreplace-smp
rcu_nocbs=0-64 rcupdate.rcu_expedited=1 rootfstype=ext4,btrfs,xfs
rootwait tsc=reliable rw


The EFI configuration seems legit, however:

# efibootmgr -v
BootCurrent: 0003
Timeout: 1 seconds
BootOrder: 0003,0005,0001
Boot0001 UEFI: Built-in EFI Shell VenMedia(5023b95c-db26-429b-
a648-bd47664c8012)..BO
Boot0003* UEFI OS HD(1,GPT,f2d8aada-01a9-4c9c-86fe-
61ccb217e678,0x800,0x47000)/File(\EFI\BOOT\BOOTX64.EFI)..BO
Boot0005* ACRN Hypervisor HD(1,GPT,f2d8aada-01a9-4c9c-86fe-
61ccb217e678,0x800,0x47000)/File(\EFI\ACRN\ACRN.EFI)b.o.o.t.l.o.a.d.e.r
.=.\.E.F.I.\.o.r.g...c.l.e.a.r.l.i.n.u.x.\.b.o.o.t.l.o.a.d.e.r.x.6.4...
e.f.i. .u.a.r.t.=.b.d.f.@.0.:.1.8...1.


I switched the order to 0005,0003,0001 but it made no difference, and
once I did: the bootorder had automaticaly changed back to
0003,0005,0001. Is this nominal?

The acrn.efi is from acrn_quick_setup.sh, which requested to do:

cp /usr/lib/acrn/acrn.nuc7i7dnb.industry.efi /usr/lib/acrn/acrn.up-
apl01.industry.efi

So I did. (and installation seemed to go well.)


Any idea where the problem could be?
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 security related features and roadmap 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
 

2020 ACRN Project Technical Community Meeting Minutes - WW17'20

Zou, Terry
 

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.
ACRN Project TCM - 22th Apr 2020
Location
Attendees (Total 33, 22/4)
 
Note: If 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 
N/A
 
  1. “ACRN Debug Tool” by Yin, Fengwei
Download foil from ACRN Presentation->ACRN_TCM->WW17’20
Description: ACRN Debug Tool Introduction, we will talk about debugging methods which could be used with ACRN, and different tools, including acrn platform tracing tool, JTAG tool, Top/hotp and Valgrind tools.
  1. All: Community open discussion.
Q&A: 
Q1: RIP is the absolute address, “acrn.out” to map with relative address.
Q2: set log level in launch_uos.sh:  logger_setting= console,level=4;kmsg, level3;disck, level=5
 
  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 CPU Virtualization WU, Binbin 4/29
WW19 CPU sharing – framework LIU, Shuo 5/6
WW20 USB Mediator LIU, Long 5/13
WW21 ACRN security related features and roadmap CHEN, Jason 5/20
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.
 
========================
 

WW17‘20 ACRN System Debug.pdf

WW17‘20 ACRN System Debug.pdf

581 - 600 of 1257