Just like QNX OS systems built to run directly on hardware, a QNX OS system built to run as a guest in a QNX hypervisor environment uses a BSP, which supplies the architecture-specific components.
The qvm configuration sets up the VM in which a guest will run. In most cases, building a QNX guest requires only building a bootable image, as you would for a non-virtualized environment.
When building QNX guests:
- Remember that the VM in which a guest will run must match the guest's expectations: architecture, board-specifics, memory and CPUs, devices, etc. (see “Assembling and configuring VMs” in the “Configuration” chapter).
- Be sure to use the architecture-specific guest BSP for your guest's OS version (e.g., QNX Neutrino 7.1) and your board's architecture, not the board-specific board BSP.
- If you add pass-through devices to your guest and these devices require drivers from the board-specific BSP, copy these drivers into the appropriate locations in the guest BSP's prebuilt/ directory.
Downloading QNX guest BSPs
Figure 1. Architecture-specific guest BSPs in the QNX Software Center.
Building the QNX guest
To build the QNX guest, assuming that you have set up your build environment on your development host system:
- Set up your environment variables so you can build a QNX OS image in your guest BSP's root directory.
- If you haven't already done so, from the QNX Software Center, download the BSP for an x86 or ARM QNX guest.
Unzip and place the QNX guest BSP in a convenient location. For example:
# unzip ~/Downloads/BSP_hypervisor-guest-x86_br-710_be-710_SVN917988_JBN3.zip -d guest_bsp
where guest_bsp is the location where you placed your guest BSP.
- If you make changes to your guest BSP, from the guest BSP root directory, run make.
You can now add the guest IFS to a bootable disk image with the host and transfer it to your target (see “Hypervisor disk images” in this chapter).