Copy the contents of a file into the guest system address space
Synopsis:
[blob_type] load [address,]filepath
Options:
- address
- The location in the guest where file is to be loaded.
This address is the guest-physical address (the address as seen by the
guest, not the host).
- If address isn't specified, and the
qvm process recognizes the file content type
(blob_type), the qvm process loads
the file content to the location indicated by this type. If the
qvm processes can't identify the type of content, it
loads the contents of file to the first available
location it finds.
- The only requirement for the address is that it be in the guest's allocated
guest-physical memory (see “Memory” in the Understanding QNX Virtual Environments)
chapter.
- blob_type
- The type of content (see below). If blob_type isn't specified, the
qvm process attempts to identify the type of file
content and load it appropriately (e.g., if it sees an ELF or Linux image
format, it will load the data at the locations indicated by the file
contents and configure the guest bootstrap CPU to begin execution at the
entry point specified by the file).
- If the first file being loaded doesn't have a recognized file format (again,
with blob_type not specified), the qvm
process configures the guest bootstrap CPU to begin execution at the first
byte of the file.
- If blob_type precedes a pass option, the
qvm process passes the data of the specifed type to
the guest (see “pass” in this
chapter).
- filepath
- The path and name of the file to load.
Description:
The qvm process recognizes the following file content
types (blob_type) specified before a load
option:
- acpi
acpi load [addr,]filepath
- Available only for x86. The contents of filepath are
loaded into guest memory and provided as an additional ACPI table. If
addr is specified, the table is placed at the
specified guest-physical address (see “ACPI tables and FDTs” in the “Configuration” chapter).
- data
data load [addr,]filepath
- The qvm process loads the contents of
filepath into guest memory. If
addr is specified, the data is placed at that address
in guest-physical memory.
- The file isn't considered to be a bootable image; the qvm
process won't configure the bootstrap guest CPU to begin execution at the
entry point indicated by the file contents. If the qvm
process recognizes the file format, it will perform normal load processing
for that file format (e.g., if the file is an ELF file, the
qvm process places the contents according to the ELF
segment table).
- fdt
fdt load filepath
- Available only for ARM. The file contains a flattened device tree (FDT)
binary blob; the qvm process will add its automatically
generated information to this FDT blob, write it all into the guest memory,
and pass the location of this information to the guest OS during its boot up
(see “ACPI tables and FDTs” in the “Configuration” chapter).
- guest
guest load [addr,]filepath
- The qvm process will load the contents of
filepath into guest memory. These contents will be
interpreted as being the guest OS boot image.
- initrd
initrd load [addr,]filepath
- The qvm process loads the contents of
filepath in guest memory and makes them available to
a Linux guest as the initial RAM disk filesystem. If addr
is specified, the contents of the file are placed at the specified
guest-physical address.
- raw load
raw load [addr,]filepath
- The qvm process copies the file byte for byte into the
guest, even if its format would normally be handled by the
qvm process. It performs no processing of the file
contents.
Example:
The following loads a QNX IFS into the address space for the guest that will run in
the VM defined by the current qvm configuration file:
load /vm/images/qnx7.ifs
Since only the filepath and name are specified, the qvm process
creating the VM will examine the blob and place it in the location specified in the
ELF headers.