CONFIG_SCENARIO

ACRN scenario

Type: string

Help

By specifying SCENARIO name, ACRN will load corresponding VM configurations to build the hypervisor. Currently ACRN provides below reference scenarios: sdc: Typical scenario for automotive Software Defined Cockpit system. sdc will have one pre-launched SOS VM and one post-launched VM; industry: Typical scenario for industry usage with 8 VMs: one pre-launched SOS VM, one post-launched KATA VM, one post-launched RT VM for real-time control, and up to five post-launched Standard VMs; hybrid: Typical scenario for hybrid usage with 3 VMs: one pre-launched VM, one pre-launched SOS VM and one post-launched Standard VM; logical_partition: Typical scenario that run two isolated pre-launched VMs;

Defaults

  • “sdc”

Kconfig definition

At arch/x86/Kconfig:1

Included via Kconfig:3

Menu path: (top menu)

config SCENARIO
    string
    prompt "ACRN scenario"
    default "sdc"
    help
      By specifying SCENARIO name, ACRN will load corresponding VM configurations
      to build the hypervisor. Currently ACRN provides below reference scenarios:
      sdc: Typical scenario for automotive Software Defined Cockpit system.
      sdc will have one pre-launched SOS VM and one post-launched VM;
      industry: Typical scenario for industry usage with 8 VMs: one pre-launched SOS VM,
      one post-launched KATA VM, one post-launched RT VM for real-time control,
      and up to five post-launched Standard VMs;
      hybrid: Typical scenario for hybrid usage with 3 VMs: one pre-launched VM,
      one pre-launched SOS VM and one post-launched Standard VM;
      logical_partition: Typical scenario that run two isolated pre-launched VMs;

(Definitions include propagated dependencies, including from if’s and menus.)