Booting the hypervisor

These instructions explain how to boot the hypervisor on supported boards.

After the hypervisor has booted, you will be able to have a look at its activity (see “Viewing hypervisor activity”), then boot the guests (see “Starting and using guests”).

Note: If you have more than one disk connected to your target, the disk partitions for your hypervisor system may not mount. For information on how to resolve this issue, see “Problems mounting a disk image or partitions” in the “Monitoring, Troubleshooting, and Tuning” chapter.

Broadwell NUC 5i5

For more information about booting the Broadwell NUC 5i5, see the board manufacturer's documentation.

In its default configuration, the Broadwell NUC boots from a BIOS (rather than a UEFI or ABL). The QNX Hypervisor expects that the board will have booted from its BIOS.

To boot the hypervisor on the Broadwell NUC:

If you haven't done so already, connect a terminal on your host system to the Broadwell NUC's serial port, and start your terminal program.
With the board power supply disconnected, insert the USB key with the bootable image into the USB slot closest to the top of the board.
Connect the board power supply. We recommend that you use a power bar.
Press the board's ON/OFF button to power it on.

Note: On this board, the system shell is active only on the serial port. It isn't active on the VGA console. Make sure that you connect your development host to your target board via the serial port. If you connect via the VGA console, you'll see a logo, and it will seem like the board is stalled somewhere in its boot process.

The hypervisor should boot on the board, and you should soon see the following on the board display:

▒▒▒▒▒No low memory for AP startup; using bootloader
apstart_init(0000000000000600,000000000401552f) [size=0x000000ac]
MMFLAGS=1
Welcome to QNX Hypervisor 2.0 on x86_64!!
Starting serial driver.....
Starting PCI server...
Starting network...
Start USB services...
Starting some common servers...
Start USB mass storage class services...
Adding host ethernet interface to the bridge
Creating example disks in shmem for guests to use
Starting DHCP...
Starting DHCP
# Kicking off /disk-dos/hv_setup.sh...
hv_setup.sh called!
Starting qconn service...
Starting network service...
Could not load host key: /etc/ssh/ssh_host_dsa_key
Could not load host key: /etc/ssh/ssh_host_ecdsa_key
Could not load host key: /etc/ssh/ssh_host_ed25519_key
131072+0 records in
131072+0 records out
131072+0 records in
131072+0 records out

If the hypervisor doesn't boot from the USB key on your target, and instead the boot menu appears on the board's display, try reformatting the USB key's partition table to GPT format, and booting again.

Gordon Ridge MRB

These instructions are for booting from a micro SD card. If you haven't done so already:

Set your target's DIP switches to disable boot from Linux, and allow access to the ABL shell (see “Disabling booting from Linux” in this chapter).
Copy the IFS file to the micro SD card, then insert the card in your target (see “Transferring the disk image”).

When you have completed the above tasks, you are ready to boot the board:

If you haven't done so already, connect a terminal on your host system to the target's serial port, and start your terminal program.
See the instructions in “Boot the board” in the QNX BSP User's Guide for the Intel Gordon Ridge MRB.
At the prompt from the ABL, type the following to load the image file:
```
boot sdc1:/hypervisor-ifs-x86_64-abl-gordon_peak.bin
```

The hypervisor should boot on the board. Your serial console on your host should display output from the QNX Hypervisor boot process.

When the hypervisor has finished booting, you should see “QNX Hypervisor 2.0 boot successful” on your serial console.

Note: If you use a USB cable to connect to the board, in the terminal program on your host, connect to the fourth serial device that appears when you plug the cable into your host. The other devices are reserved and can't be used for the terminal console (see the Intel documentation for more information).

R-Car H3

The Renesas R-Car H3 Salvator-X has two micro SD card readers. You can use either one to transfer the reference image to your target. The R-Car H3 Starter Kit has only one micro SD card reader.

To get a hypervisor reference image onto your Renesas R-Car H3 target:

Confirm that your target's DIP switches are set to put your board in 64-bit mode, and to boot in HyperFlash mode (see “Set the DIP switches”).
Copy the disk image to the micro SD card, then insert the card in your target (see “Transferring the disk image”).

With the micro SD card in your target, you can boot the board:

If you haven't done so already, connect a terminal on your host system to your board's serial port, and start your terminal program.
The disk image for the R-Car H3 includes two IFSs. To see what IFSs are available in the disk image, in the command line run:
```
fatls mmc 0
```
To have the boot use the appropriate IFS, you must set the bootcmd environment variable accordingly and save it. If your board is a Starter Kit, use the IFS with a ulcb in its name. For the Salvator-X board, use the other IFS:
- For a Starter Kit, set bootcmd as follows:
```
setenv bootcmd \
	'fatload mmc 0 0x40100000 hypervisor-ifs-rcar_h3ulcb.bin; \
	go 0x40100000'
```
- For a Salvator-X board, set bootcmd as follows:
```
setenv bootcmd \
	'fatload mmc 0 0x40100000 hypervisor-ifs-rcar_h3.bin; \
	go 0x40100000'
```
When you have set the bootcmd environment variable, save it:
```
saveenv
```
See the instructions in “Transfer image and boot the board” in the QNX BSP User's Guide for the Renesas R-Car H3.

The hypervisor should boot on the board. Your serial console on your host should display output from the QNX Hypervisor boot process.

When the hypervisor has finished booting, you should see “QNX Hypervisor 2.0 boot successful” on your serial console.