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 User's Guide
Monitoring and Troubleshooting
This chapter describes some tools and techniques you can use to monitor and troubleshoot your hypervisor system.

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
- QNX Hypervisor User's Guide
  - Understanding QNX Virtual Environments
    QNX hypervisors are designed to meet the expectations of a hypervisor specified by the Popek/Goldberg Theorem.
  - QNX Hypervisor: Protection Features
    This chapter explains the main features used by the QNX Hypervisor to protect itself and its guests. Many of these features are part of the design, while others are configurable.
  - Configuration
    A QNX hypervisor, its qvm processes that create the VMs in which guests run, and these guests must be configured to work together.
  - Building a QNX Hypervisor system
    This chapter explains how to build (assemble) a QNX Hypervisor system and transfer a bootable image to a supported target platform.
  - Booting and Shutting Down
    This chapter describes how to boot and shut down a QNX hypervisor system.
  - Using Virtual Devices, Networking, and Memory Sharing
    This chapter describes how guests can discover and connect to vdevs and how they can use important hypervisor capabilities, such as networking and memory sharing.
  - Monitoring and Troubleshooting
    This chapter describes some tools and techniques you can use to monitor and troubleshoot your hypervisor system.
    - Using the GNU debugger (GDB)
      You can use GDB to better understand and debug a guest OS's activities inside its hypervisor VM (qvm process instance).
    - Viewing hypervisor activity
      After the hypervisor guest has booted, you can use QNX Momentics IDE to open a command terminal to either the host or a guest and then view its resource usage and activity.
    - Getting hypervisor trace information
      You can use the tracelogger utility and the QNX Momentics IDE System Profiler to capture and examine trace events from a VM.
    - Gathering information about a virtual machine
      QNX Hypervisor provides ways for gathering information about the VM running inside of a qvm process.
    - 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 vdevs the guest OS expects to find.
    - Finding the current time drift
      You can retrieve information about a guest's current time drift by sending a SIGUSR1 to the qvm process hosting the guest.
    - Getting a guest dump during a crash
      You can configure your guest and the watchdog vdev in its VM to dump the guest's state in the event of a crash.
    - qvm process exit codes
      When a qvm process exits, the shell exit status indicates the reason for the exit.
  - Performance Tuning
    This chapter describes common sources of overhead in a QNX hypervisor system, and strategies for reducing this overhead and optimizing system performance.
  - VM Configuration Reference
    When you specify options to configure a qvm process, you are assembling and configuring the components of a virtual machine (VM) in which a guest will run.
  - Virtual Device Reference
    This chapter presents the virtual devices (vdevs) delivered with QNX hypervisors, and describes how to configure these vdevs.
  - Utilities and Drivers Reference
    This chapter describes the utilities and drivers delivered with the QNX hypervisor.
  - Terminology
    The following terms are used throughout the QNX hypervisor documentation.
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.

Monitoring and Troubleshooting

This chapter describes some tools and techniques you can use to monitor and troubleshoot your hypervisor system.

The QNX Hypervisor is a QNX Neutrino microkernel plus a virtualization extension. This means that this hypervisor product has the same debugging, monitoring, and troubleshooting capabilities as this QNX OS variant. Thus, all tools—QNX Momentics IDE, command line, and third-party—and techniques available for working with the QNX OS are also available for working with the hypervisor host or QNX guests. For Linux guests, use your Linux tools (GDB TraceCompass, etc.).

Troubleshooting strategies

There are numerous ways to get information about the different parts of your hypervisor system. For guests, use the same debugging tools you would use for the OS and its applications in a non-virtualized system, by connecting to a TCP/IP stack running within the guest. For example, if you run a QNX guest and it starts such a stack along with the qconn service, the QNX Momentics IDE can connect to the guest through TCP/IP and do application-level debugging. For information about debugging with the IDE, see the Debugging Applications chapter in the IDE User's Guide.

For hosts, the troubleshooting ways include:

Add the logger to the qvm configuration (see logger in the VM Configuration Reference chapter) to log certain message types.
Use GDB (see Using the GNU debugger (GDB)) to understand a guest's activities in its qvm process instance.
Use tracelogging (see Getting hypervisor trace information) to examine trace events from a VM.

A typical approach to troubleshooting would be to use the qvm logger option to gather general information about what a qvm process is doing (and, by indirection, what a guest is doing), then to use GDB and tracelogging for more detailed analysis.

If you need to keep more than the default 4K of slog information kept by the hypervisor, you can use the set option to set the slog-buffer variable to the right buffer size (see slog-buffer in the VM Configuration Reference chapter). You can also send the output to your console.

Page updated: March 12, 2026