Home
QNX Hypervisor and QNX Hypervisor for Safety
The QNX Hypervisor and QNX Hypervisor for Safety products allow you to run multiple OSs on a target system so you can separate critical and non-critical functions, support a wide variety of applications, and reduce hardware costs.
Virtual Device Developer's API Reference
The Virtual Device Developer's API Reference presents the QNX hypervisor public virtual device (vdev) API. It is intended for use by developers writing virtual devices (vdevs) in a QNX hypervisor system.
firmware.h
Functions for working with the firmware components of the VM presented to the guest
gfdt_add_symbol()
Add a symbol to the FDT symbol table (ARM)

QNX Momentics IDE User's Guide
This User's Guide describes version 8.0 of the Integrated Development Environment (IDE) that's part of the QNX Tool Suite.
QNX Software Development Platform
QNX SDP is a cross-compiling and debugging environment, including an IDE and command-line tools, for building binary images and programs for target boards running the QNX OS 8.0.
QNX Software in the Cloud
QNX Software in the Cloud enables developers to use the QNX software in Amazon Web Services (AWS) and Microsoft Azure (Azure).
QNX Toolkit for Visual Studio Code
This User's Guide describes the QNX^® Toolkit for Visual Studio Code. The guide introduces you to the QNX Toolkit by explaining the QNX development environment and how to build, run, and debug your QNX^® Operating System (OS) applications and systems.
QNX Hypervisor and QNX Hypervisor for Safety
The QNX Hypervisor and QNX Hypervisor for Safety products allow you to run multiple OSs on a target system so you can separate critical and non-critical functions, support a wide variety of applications, and reduce hardware costs.
- User's Guide
  This User's Guide explains the QNX hypervisor architecture and provides instructions for installing and running a QNX hypervisor system, changing system components and configuration, and using hypervisor features such as virtual devices (vdevs).
- Virtual Device Developer's Guide
  The Virtual Device Developer's Guide is intended for use by developers writing virtual devices (vdevs) in a QNX hypervisor system.
- Virtual Device Developer's API Reference
  The Virtual Device Developer's API Reference presents the QNX hypervisor public virtual device (vdev) API. It is intended for use by developers writing virtual devices (vdevs) in a QNX hypervisor system.
  - Function Safety
    This section provides an overview of the restrictions that may apply when using the functions in this API.
  - aarch64/vmid.h
    Functions to access a guest's VMID (ARM)
  - abi.h
    Application binary interface (ABI) information
  - cdev.h
    Support routines for virtual character devices
  - firmware.h
    Functions for working with the firmware components of the VM presented to the guest
    - gacpi_add_table()
      Format and add an ACPI table to the guest (x86)
    - gacpi_register_ioapic()
      Add an IO-APIC vdev to the MADT (x86)
    - gfdt_add_interrupts()
      Generate interrupts and interrupt-parent properties (ARM)
    - gfdt_add_node()
      Create an FDT node (ARM)
    - gfdt_add_phandle()
      Add a phandle (parent handle) property to a node (ARM)
    - gfdt_add_prop_cells()
      Add a property with uint32_t cells (ARM)
    - gfdt_add_prop_string()
      Add a property with a string value (ARM)
    - gfdt_add_prop_strings()
      Add a property with a list of string values (ARM)
    - gfdt_add_property()
      Add a property to a node (ARM)
    - gfdt_add_reg()
      Generate a reg property (ARM)
    - gfdt_add_symbol()
      Add a symbol to the FDT symbol table (ARM)
    - gfdt_add_vdev()
      Add a vdev node to the FDT (ARM)
    - gfdt_get_clock()
      Get the phandle for the clock node in the FDT (ARM)
    - gfdt_get_phandle()
      Get the phandle (parent handle) for a vdev (ARM)
    - gfdt_intr_spec()
      Get the FDT data representing an interrupt (ARM)
  - gasp.h
    Definitions and functions for working in guest address spaces
  - guest.h
    Controls for manipulating a guest system
  - hpci.h
    Host PCI interface for vdevs
  - hw_pci.h
    PCI support for vdevs
  - log.h
    Controls for logging messages
  - types.h
    vdev API base types
  - utils.h
    Miscellaneous utility functions
  - vdev-core.h
    Definitions and functions that support vdev control functions and callbacks
  - vio.h
    Definitions and functions for working with VIRTIO vdevs
  - vpci.h
    Controls for virtual PCI (vPCI) devices
  - wdog.h
    Constants, data types, and functions to support virtual watchdog devices
  - x86_64/apic.h
    Definitions for the virtual APIC bus (x86)
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation, explains how to obtain technical support, and provides some information about licensing.

gfdt_add_symbol()

Add a symbol to the FDT symbol table (ARM)

Synopsis:

#include <qvm/firmware.h>

void gfdt_add_symbol(int node,
                    const char *fmt,
                    ...)

Arguments:

node: The offset of the symbol value.
fmt: The symbol name, as a printf()-like formatted string.
...: Optional arguments for the formatted string above.

Description:

This function associates a symbol name to a given node so it can be referenced by an overlay given in a VM configuration.

Page updated: March 14, 2026