The Virtual Device Developer's Guide is intended for use by developers writing virtual devices (vdevs) in a QNX Hypervisor (non-safety) or QNX Hypervisor for Safety system.
It should be used in conjunction with the following documents:
QNX hypervisors are available in two variants: QNX Hypervisor and QNX Hypervisor for Safety. For simplicity, we may use the terms QNX hypervisor and hypervisor to refer to both variants.
For information about which QNX SDP version is compatible with your QNX hypervisor release, meaning you can use that QNX SDP version as a development platform, see your hypervisor Release Notes.
The source code for the vdevs discussed in this guide is available on GitHub at github.com/qnx.
The discussion presented with each example in this guide builds on the information presented with previous examples. Thus, the discussion of vdev wdt-sp805 builds on vdev trace. We don't repeat information already presented with a previous example; for instance, in the discussion of vdev wdt-sp805 we don't explain a vdev's startup stage because that topic is already covered with vdev trace.
The QNX virtual device toolkit does not automatically produce safety-certified vdevs. It is your responsibility to develop your vdevs in an appropriate environment and to see them through safety certification.
If you require assistance, please contact your QNX technical support representative.
| To find out about: | See: |
|---|---|
| General information about writing a vdev in a QNX hypervisor system | About Writing Vdevs |
| A simple vdev example | The Basics: vdev trace |
| Vdevs that emulate hardware | Advanced Topics |
| Para-virtualized devices that use VIRTIO | Para-virtualized devices (virtio-entropy) |