Home
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.
Input Sharing
The Shared Input framework allows guests and the hypervisor host to share access to input devices. Specifically, it provides a virtual device that lets guests access input from physical devices connected to the hypervisor host.
Required components
To support shared input in a QNX Hypervisor system, you must add components to your guest and host images, and configure the virtio-input vdev in the guest's VM.

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 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.
- QNX Advanced Virtualization Frameworks Architecture
  The QNX Advanced Virtualization Frameworks allow you to build systems that share resources such as graphics, audio, and input devices among multiple OSs, while separating the management of critical services and non-critical services to mitigate the effects of faults.
- Audio Sharing
  The Shared Audio framework allows guests to capture and output audio on devices connected to the hypervisor host. It does this by providing an audio virtual device through which guests can start and stop these operations and configure parameters such as sampling rate.
- Camera Sharing
  The Shared Video and Camera framework allows the host and guests to share the same camera.
- Filesystem Sharing
  The Shared Filesystem framework allows guests to access directories on the host through mountpoints of their choosing. The framework does this by providing a virtual filesystem device through which guests can interact with files in shared host directories as though they were local files.
- Graphics Sharing
  Graphics sharing is supported by the Shared GPU and Display framework. This framework supports sharing graphical content between the host and guests, and includes a virtual device, virtual rendering libraries, and other services.
- Input Sharing
  The Shared Input framework allows guests and the hypervisor host to share access to input devices. Specifically, it provides a virtual device that lets guests access input from physical devices connected to the hypervisor host.
  - Framework architecture
    The Shared Input framework enables guests running in virtual machines (VMs) to access input from devices connected to a QNX Hypervisor host.
  - Required components
    To support shared input in a QNX Hypervisor system, you must add components to your guest and host images, and configure the virtio-input vdev in the guest's VM.
  - vdev virtio-input
    Create an interface for input devices
- Sensor Sharing
  The Sensor Sharing framework allows guests to read data from sensors connected to the hypervisor host. Sensor support will vary. Presently, the framework allows guests to access Inertial Measurement Unit (IMU) sensors on the hypervisor host.
- USB Sharing
  The Shared USB framework allows guest and host applications to share access to USB devices. Specifically, it provides a virtual device that lets guests access USB devices connected to the hypervisor host.
- Virtual Socket
  The Virtual Socket framework provides a simple mechanism for passing data between the host and a guest, or between guests, independently of network protocols.
- VPU Sharing
  The Shared Video and Camera framework allows guests to use the video processing unit (VPU) on the host system to decode video. The framework does so by providing a virtual video device that provides media codec and video control functionality to client guest applications and uses the host system's VPU to do the required codec operations.
- Integration Support for Android
  The QNX Advanced Virtualization Frameworks support integrating Android into a QNX Hypervisor system with minimal changes to the Android Operating System. This is possible by supporting common Android OS versions and services, adhering to industry standards for virtualization, and allowing existing components to be reused unmodified. There's also a demonstration system that shows how applications in an Android guest can use the virtualization frameworks.
Typographical Conventions, Support, and Licensing
This section describes the typographical conventions used throughout the documentation and explains how to obtain technical support.

Required components

To support shared input in a QNX Hypervisor system, you must add components to your guest and host images, and configure the virtio-input vdev in the guest's VM.

Host components

To enable input sharing, you must ensure that:

The vdev shared object, vdev-virtio-input.so, is included in the hypervisor host image by your host buildfile.
For each VM that hosts a guest that needs access to input devices, the virtio-input vdev is configured. For information on how to do this, see vdev virtio-input.
The path to the configuration file (*.qvmconf file) for each guest that's running in a VM is included in your host buildfile.
The Screen Graphics Subsystem and related input drivers, such as mtouch and io-hid, are included in the host image. See the Screen Developer's Guide for details on using and configuring Screen.
At least one physical input device is connected to your host system. The vdev expects to find an input device; if it doesn't, the vdev prevents the qvm process from starting.
The USB stack (io-usb-otg) and any USB device drivers (devu-*) needed for the USB keyboards or pointers connected to your host system are included in the host image. See the io-usb-otg entry in the QNX Neutrino Utilities Reference for details on the USB stack.

For information on how to configure your hypervisor host, see the Configuration section of the QNX Hypervisor User's Guide.

Guest components

The virtio-input vdev is a para-virtualized device. It runs in a hypervisor VM, but it doesn't emulate a specific hardware device. Instead, it provides the functionality that one or more physical devices (keyboard, mouse, touchscreen) might provide in a conventional, nonvirtualized environment.

Because the vdev is a para-virtualized device, the guest must know that it is running in a virtualized environment and add the VirtIO input kernel driver (e.g., virtio_input.ko for an Android or Linux guest) to its image. See Building guests in the QNX Hypervisor User's Guide for more guidelines.

Page updated: March 12, 2026