qvm process exit codes
When a qvm process exits, the shell exit status indicates the reason for the exit.
The codes indicating the reason a qvm process exited include:
- No error
- 0 – the qvm process ran as designed, and terminated in response to a request to shut down or restart that is part of normal operations
- VM- and vdev-related errors
-
- 3 – the guest was terminated by an action analogous to its power being cut (e.g., its hosting qvm process instance received a SIGQUIT signal)
- 4 – watchdog-triggered termination
- 5 – unsupported operation
- 6 – unexpected vdev error
- 7 – unexpected error
- 32 to 63 – the exit code is set by the user; for example, to indicate that a specific vdev caused the exit (see the Virtual Device Developer's Guide)
- Fatal errors
-
- 64 – fatal error before the guest started (e.g., out of memory)
- 65 – fatal configuration error
- 96 – fatal error after guest started
More information
Exit/error codes for qvm are defined in the guest.h public header file.
For information about:
- DSSs –
Design Safe States
in theQNX Hypervisor: Protection Features
chapter - qvm process exit and error codes – the guest.h chapter in the Virtual Device Developer's API Reference
- filtering messages from qvm process instances –
logger
in theVM Configuration Reference
chapter - getting a dump – dump
in the
VM Configuration Reference
chapter - the hypervisor while it is running and after it has quit – pidin and slog2info in the QNX OS Utilities Reference
Page updated: