OS-VM configuration mismatch

A guest may fail to start or not perform as expected if the VM in which it is running is not configured with the virtual devices the guest OS expects to find.

Just as an OS running on a non-virtualized system expects certain physical devices to be present on the board, a guest OS expects certain vdevs to be present in its VM.

For example, a QNX Neutrino OS 7.0 on an x86-64 platformm expects its VM to include the standard devices (as vdevs) that it would expect to find on a physical board. These include:

Either hpet or timer8254; if hpet is used, its options override any conflicting timer8254 parameters
ioapic
pckeyboard; if this vdev is missing, you can start the guest, but you won't be able to return to the host after a guest shutdown
ser8250

Similarly, just as in a non-virtualized system the device driver in an OS must match the hardware device on the physical board, in a virtualized system the device driver in the guest must match the vdev. If your guest's device driver doesn't match the vdev, it won't be able to use the vdev.

For more information, see “Devices” in the “QNX Virtual Environments” chapter.