After you have downloaded the QHS product package and configured your build environment, all the components that you will need to build your host should be on your development host system at $QNX_TARGET.
As needed, modify your BSP buildfile to include the files you need. For example:
the libmod_qvm.a kernel module, by adding a [module=qvm] prefix to the buildfile line that includes procnto*. For example, change:
LD_LIBRARY_PATH=/usr/lib:/lib:/lib/dll procnto-smp-instr
to:
[module=qvm] LD_LIBRARY_PATH=/usr/lib:/lib:/lib/dll procnto-smp-instr
the hypervisor files: qvm and, optionally for x86: the qvm-checkutility. For example:
/sbin/qvm = qvm /bin/qvm-check = qvm-check
the vdev-*.so file for every vdev you want to make available for your guests. For example:
vdev-8259.so vdev-hpet.so vdev-ioapic.so ... vdev-virtio-console.so vdev-virtio-input.so vdev-virtio-net.so
the smmuman service, architecture and board support libraries, and configuration files. For example, for a QHS system on a supported Renesas R-Car H3 board:
/bin/smmuman-safety = smmuman-safety /bin/smmu-rcar3-safety.so = smmu-rcar3-safety.so /etc/smmuman/rcar-h3-safety.smmu = ./smmuman-config/rcar-h3-safety.smmu
If you are using the QHS, you must specify that you want the safety variants of the kernel module and the vdevs:
For more information, see the QNX Hypervisor for Safety 2.0 Safety Manual for your QHS release.
You should now be ready to build the guests (i.e., IFSs for QNX guests; kernels, initrd files, disks, etc. for Linux; see Building guests), then assemble the host and its guests into a disk image you can transfer to your target.