Troubleshooting the NI Real-Time Hypervisor

The following table summarizes troubleshooting techniques you can use to resolve problems with your NI Real-Time Hypervisor system.

Issue	Resolution
Undetected Chassis	Identify the chassis using NI Measurement & Automation Explorer, then restart the NI Real-Time Hypervisor Manager.
Undetected Devices	Ensure that the device is properly connected. Restart the controller. Select File»Re-Run Setup in the NI Real-Time Hypervisor Manager. Refer to the documentation for the specific device for additional troubleshooting steps.
Generic Device Names Displayed in the Manager	Use the Device Manager dialog box in Windows to install the appropriate device driver(s), then restart the NI Real-Time Hypervisor Manager.
Dimmed Apply button	The Apply button appears dimmed and when the current device partition settings do not meet the NI Real-Time Hypervisor partitioning requirements. You can resolve this issue in one of the following ways: Use the Advanced tab to look for PIRQ conflicts. A PIRQ conflict occurs when two devices share a PCI interrupt request line (PIRQ) and you attempt to assign those two devices to different operating systems. If the system includes any devices that do not need to be assigned to a particular OS, try moving one or more of these devices to a different OS. For each device that does not use interrupts, place a checkmark in the configure without interrupts? checkbox on the Device Properties dialog box corresponding to the device. If you have a multi-chassis system, try moving one or more MXI cards to a different PCI interrupt request line (PIRQ) on the Advanced tab. If the system includes any devices that you do not plan to use, remove those devices from the system. If all else fails, you might need to use either a larger chassis or use MXI to add a secondary chassis to the system. Note  When you resolve this issue, the NI Real-Time Hypervisor Manager automatically restores the Apply button.
The Windows partition is not configured as the system partition	Refer to the National Instruments Web site for system recovery instructions.
Crashes, Hangs, and Miscellaneous Problems	Performing a software restart of the RT target restarts the NI ETS real-time OS independently of Windows, which can leave devices controlled by unsupported drivers in an undefined state. All RT drivers must implement a callback function to support independent restarts of the NI ETS real-time OS. If you have access to the source code for the unsupported driver, you can implement the callback function yourself. If you do not have access to the source code, you must add the unsupported driver(s) to a blacklist through an INI token to disable the independent RT restart operation. Refer to the National Instruments Web site for information about implementing the independent restart callback function and updating the blacklist.

If you encounter problems that you cannot resolve using these troubleshooting techniques, refer to the National Instruments Web site for system recovery instructions.