2ce914428c
1. for virtio console, reference to the document https://projectacrn.github.io/latest/developer-guides/hld/virtio-console.html, the generated launch script will look like this: `virtio-console,[@]stdio|tty|pty|file:portname[=portpath]\ [,[@]stdio|tty|pty|file:portname[=portpath][:socket_type]]` *receding with @ marks the port as a console port, otherwise it is a normal virtio-serial port *The portpath can be omitted when backend is stdio or pty. 2. for virtio input, the generated launch script as below. `<name>:<phys>,id=<anyString>` The launch script will automatically find the specific /dev/input/eventX according to the event name and phys got from board.xml. Tracked-On: #6690 Signed-off-by: Kunhui-Li <kunhuix.li@intel.com> Reviewed-by: Junjie Mao <junjie.mao@intel.com> |
||
|---|---|---|
| .. | ||
| README | ||
| launch_cfg_gen.py | ||
| launch_script_template.sh | ||
README
Please run launch_cfg_gen.py to generate board related configuration files. usage: python3 launch_cfg_gen.py [h] --board <board_info_file> --scenario <scenario_info_file> --launch <launch_info_file> positional arguments: board_info_file : file name of the board info XML scenario_info_file : file name of the scenario info XML launch_info_file : file name of the launch info uosid : this is the relateive id for post launch vm in scenario info XML:[1..max post launch vm]