ACRN-Hypervisor build fail


shibi590268@...
 
Edited

Hello,
          I am facing the build failure when trying to build acrn-hypervisor. I have generated the board.xml and scenario.xml file as given in the procedure.
I am using kontron board which belongs to intel apollo lake APL0. I am attaching the board.xml file and scenaio xml file.

Previously, i have removed those lines to suppress the warnings and built the acrn and kernel. User vm is able to launch and worked perfectly. 
My question is are these configurations mandatory for running the user vm without any problem in future. If not, how to fix them.

Traceback (most recent call last):
  File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/main.py", line 41, in
    main(args)
  File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/main.py", line 31, in main
    module.fn(board_etree, scenario_etree, allocation_etree)
  File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/bdf.py", line 149, in fn
    native_used = get_devs_bdf_native(board_etree)
  File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/bdf.py", line 89, in get_devs_bdf_native
    dev_list.append(lib.lib.BusDevFunc(bus = bus, dev = dev, func = func))
  File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/lib/lib.py", line 46, in __init__
    raise ValueError(f"Invalid function number (0 ~ 7): {self.func:#x}")
ValueError: Invalid function number (0 ~ 7): 0xff
cp acrnlog.service /home/shibi/acrn-work/acrn-hypervisor/build/misc/debug_tools/acrnlog.service
make[2]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/misc/debug_tools/acrn_log'
make[2]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/misc/debug_tools/acrn_trace'
make[1]: *** No rule to make target '/home/shibi/acrn-work/acrn-hypervisor/build/hypervisor/configs/allocation.xml', needed by '/home/shibi/acrn-work/acrn-hypervisor/build/hypervisor/configs/unified.xml'.  Stop.
make[1]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/hypervisor'
Makefile:116: recipe for target 'hvdefconfig' failed
make: *** [hvdefconfig] Error 2
make: *** Waiting for unfinished jobs....
make[3]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/misc/debug_tools/acrn_crashlog/common'
 


shibi590268@...
 

Attaching the xml files


Liu, Fuzhong
 

Hi
Could you please share the codebase info about the build fail?

 

Thanks!

 

BR.

Fuzhong

 

From: acrn-users@... <acrn-users@...> On Behalf Of shibi590268@...
Sent: Tuesday, March 8, 2022 3:53 PM
To: acrn-users@...
Subject: [acrn-users] ACRN-Hypervisor build fail

 

[Edited Message Follows]

Hello,
          I am facing the build failure when trying to build acrn-hypervisor. I have generated the board.xml and scenario.xml file as given in the procedure.
I am using kontron board which belongs to intel apollo lake APL0. I am attaching the board.xml file and scenaio xml file.

Previously, i have removed those lines to suppress the warnings and built the acrn and kernel. User vm is able to launch and worked perfectly. 
My question is are these configurations mandatory for running the user vm without any problem in future. If not, how to fix them.

Traceback (most recent call last):

  File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/main.py", line 41, in

    main(args)

  File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/main.py", line 31, in main

    module.fn(board_etree, scenario_etree, allocation_etree)

  File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/bdf.py", line 149, in fn

    native_used = get_devs_bdf_native(board_etree)

  File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/bdf.py", line 89, in get_devs_bdf_native

    dev_list.append(lib.lib.BusDevFunc(bus = bus, dev = dev, func = func))

  File "/home/shibi/acrn-work/acrn-hypervisor/misc/config_tools/static_allocators/lib/lib.py", line 46, in __init__

    raise ValueError(f"Invalid function number (0 ~ 7): {self.func:#x}")

ValueError: Invalid function number (0 ~ 7): 0xff

cp acrnlog.service /home/shibi/acrn-work/acrn-hypervisor/build/misc/debug_tools/acrnlog.service

make[2]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/misc/debug_tools/acrn_log'

make[2]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/misc/debug_tools/acrn_trace'

make[1]: *** No rule to make target '/home/shibi/acrn-work/acrn-hypervisor/build/hypervisor/configs/allocation.xml', needed by '/home/shibi/acrn-work/acrn-hypervisor/build/hypervisor/configs/unified.xml'.  Stop.

make[1]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/hypervisor'

Makefile:116: recipe for target 'hvdefconfig' failed

make: *** [hvdefconfig] Error 2

make: *** Waiting for unfinished jobs....

make[3]: Leaving directory '/home/shibi/acrn-work/acrn-hypervisor/misc/debug_tools/acrn_crashlog/common'

 


shibi590268@...
 

Hi Liu,
   acrn-2022w03.2-180000p is the acrn-hypervisor tag I am using to build. 


Liu, Fuzhong
 

Hi Shibi

Your board.xml is generated with acrn-2022w03.2-180000p; but it is a little old for your scenario.xml.

It is preferred to generate board.xml and scenario.xml with the same codebase.

 

With the updated shared.xml; the build is passed with the latest codebase on my side.

 

 

ACRN Configuration Summary:

Build directory: /home/acrn/acrn-hypervisor/build/hypervisor

This build directory is configured with the settings below.

- BOARD = zingtron

- SCENARIO = shared

- RELEASE = n

ACRN debian package acrn-zingtron-shared-3.0-unstable.deb was successfully created in the /home/acrn/acrn-hypervisor/build.

 

 

BR.

Fuzhong

From: acrn-users@... <acrn-users@...> On Behalf Of shibi590268@...
Sent: Tuesday, March 8, 2022 5:47 PM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN-Hypervisor build fail

 

Hi Liu,
   acrn-2022w03.2-180000p is the acrn-hypervisor tag I am using to build. 


shibi590268@...
 

Hello,
     Thanks. I used acrn-2022w03.5-180000p to build ACRN and launch scripts. It builds without error. If I use the latest tag I am seeing some error while running acrn_configurator. It is from 40_acpi in extractor. 

How would be the performance of rt patched ubuntu in shared scenario? I tested with cyclic test. I am seeing max time around 10 ms with average around 30 us for a loop of 50000 cycles. 

Should it be run under partitioned mode for better performance?. 
Does partition mode must need separate storage devices (passthru)?

My service vm crashes and gets powered off when trying to passthru GPU to user vm. 

Is GPU passthru working in this tag. I am using Apollo lake intel board.


Liu, Fuzhong
 

Hi,

 

Do you refer following guide to setup rtvm?

https://projectacrn.github.io/latest/tutorials/rtvm_performance_tips.html#

 

The main usage of partitioned mode is for safety; not necessary for rt performance.

Apollo lake isn’t the  ACRN supported platform for GPU passthru; please try GPU passthru with Kaby lake/ Whiskey Lake/ Tiger Lake

 

Thanks!

 

BR.

Fuzhong

 

From: acrn-users@... <acrn-users@...> On Behalf Of shibi590268@...
Sent: Friday, March 11, 2022 12:16 AM
To: acrn-users@...
Subject: Re: [acrn-users] ACRN-Hypervisor build fail

 

Hello,
     Thanks. I used acrn-2022w03.5-180000p to build ACRN and launch scripts. It builds without error. If I use the latest tag I am seeing some error while running acrn_configurator. It is from 40_acpi in extractor. 

How would be the performance of rt patched ubuntu in shared scenario? I tested with cyclic test. I am seeing max time around 10 ms with average around 30 us for a loop of 50000 cycles. 

Should it be run under partitioned mode for better performance?. 
Does partition mode must need separate storage devices (passthru)?

My service vm crashes and gets powered off when trying to passthru GPU to user vm. 

Is GPU passthru working in this tag. I am using Apollo lake intel board.