Home
QNX Hypervisor
The QNX Hypervisor allows 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.
QNX Hypervisor for Safety Virtual Device Developer's API Reference
vdev-core.h
Definitions for vdevs
vdev_s
Virtual device (vdev) information

QNX Momentics IDE User's Guide
This User's Guide describes version 7.1 of the Integrated Development Environment (IDE) that's part of the QNX Momentics 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 QNX Neutrino 7.1.
QNX Hypervisor
The QNX Hypervisor allows 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.
- QNX Hypervisor for Safety User's Guide
- QNX Hypervisor for Safety Virtual Device Developer's Guide
- QNX Hypervisor for Safety Virtual Device Developer's API Reference
  - Function Safety
    This section provides an overview of the restrictions that may apply when using the functions in this API.
  - aarch64/vmid.h
    Definitions to access a guest's VMID (ARM)
  - abi.h
    Application binary interface (ABI) version of the vdev API
  - cdev.h
    Functions to create virtual character devices for guests
  - firmware.h
    Functions for working with the firmware components of the VM presented to the guest
  - gasp.h
    Functions for working in guest address spaces
  - guest.h
    Definitions for manipulating a guest system
  - hpci.h
    Host PCI interface for vdevs
  - hw_pci.h
    PCI support for vdevs
  - outpipe.h
    Definitions for the output pipe (outpipe)
  - types.h
    vdev API base types
  - utils.h
    Miscellaneous utility functions
  - vdev.h
    Source compatibility header file
  - vdev-core.h
    Definitions for vdevs
    - Definitions in vdev-core.h
      Preprocessor macro definitions for the vdev-core.h header file
    - guest_cpu_to_vrs()
      Convert an error from a vCPU read or a vCPU write into a status value
    - vdev_ctrl_assign_flags
      Flags for the VDEV_CTRL_ASSIGN operation
    - vdev_factory
      Data structure used for creating new vdev instances
    - vdev_factory_flags
      Flags controlling vdev creation
    - vdev_get_vdevpeer()
      Retrieve or create the vdevpeer object associated with a vdev
    - vdev_path()
      Fill in a PATH_MAX-sized buffer with a path identifying a vdev
    - vdev_pic_functions
      Extra information for PIC vdevs
    - vdev_pulse()
      Fill in a sigevent structure to invoke a vdev pulse routine on event delivery
    - vdev_ref_status
      Return status from the vdev_factory vread and vwrite functions, and with guest_instr_callback_func_t
    - vdev_register_factory()
      Add a virtual device (vdev) factory to the list of available vdev factories
    - vdev_register_for_system_pulse()
      Register a virtual device (vdev) to receive the specified pulse
    - vdev_s
      Virtual device (vdev) information
    - VDEV_SAFETY_* enum
      Specify if the vdev is a safety variant, and if so the safety variant version
    - vdev_string()
      Build a human-readable name for a vdev
    - vdev_thread_create()
      Create a thread for a vdev
    - vdev_thread_setname()
      Set the name of a thread associated to a vdev
    - vdev_verify_unique()
      Check whether a vdev of the same type already exists
  - vio.h
    Definitions for VIRTIO vdevs
  - vpci.h
    Definitions for virtual PCI devices
  - wdog.h
    Definitions to support virtual watchdog devices
  - x86_64/apic.h
    Definitions for the virtual APIC bus (x86)
- QNX Hypervisor User's Guide
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 Advanced Virtualization Frameworks User's Guide
This User's Guide is aimed at all systems integrators and developers who want to design and build embedded systems using the QNX Advanced Virtualization Frameworks.
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation and explains how to obtain technical support.

vdev_s

Virtual device (vdev) information

Synopsis:

#include <qvm/vdev-core.h>

struct vdev_s {
    void* v_device;
    struct vdev_factory* v_factory;
    struct guest_system* v_gsp;
    struct qvm_state_block v_block;
    struct guest_intr v_intr;
    pthread_mutex_t v_mtx;
    struct qvm_sched_info v_sched;
} ;

Data:

void* v_device: A pointer to device-specific state information.
struct vdev_factory* v_factory: A pointer to the device factory for the vdev.
struct guest_system* v_gsp: A pointer to the guest system in which the vdev is defined (the hosting qvm process instance).
struct qvm_state_block v_block: The location of the vdev in the guest system.
struct guest_intr v_intr: The guest interrupt the vdev uses to request service.
pthread_mutex_t v_mtx: A mutex for the vdev's own use. Use the flags specified by vdev_factory_flags to intitialize this member: VFF_MUTEX (and, optionally, VFF_MUTEX_RECURSIVE).
struct qvm_sched_info v_sched: Scheduler information for the vdev threads.

Description:

The vdev_s structure stores vdev information and provides the definition for the vdev_t data type, which is passed into vdev configuration functions.

Page updated: March 12, 2026