Monitoring, Troubleshooting, and Tuning

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

A QNX Hypervisor is a QNX Neutrino OS microkernel plus a virtualization extension. This means that it has all that OS's debugging, monitoring, and troubleshooting capabilities. This means that all the tools (QNX Momentics IDE, command line, third-party), and techniques available for working with the QNX Neutrino OS are also available to you when you are working with the QNX Hypervisor host or QNX Neutrino OS 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. These include:

For guests, use the same debugging tools you would use for the OS and its applications in a non-virtualized system (running directly on the hardware).
Use the qvm debug option (see debug in the “Configuration” chapter).
Add the logger to the qvm configuration (see logger in the “Configuration” chapter).
Use GDB (see “Using a GNU debugger (GDB)”).
Use tracelogging (see “Getting hypervisor trace information”).

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.