This document contains the Real-Time Hypervisor known issues that were discovered before and since the release of Real-Time Hypervisor 3.0. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.
The LabVIEW 2013 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
The Known Issues Document is divided into two separate tables. The section linked below displays the issues by category.
Please refer to Developer Zone Article: LabVIEW Known Issues Categories Defined for a detailed explanation of categories and the types of issues listed in each category.
For those who wish to locate newly reported issues or issues by date, the section linked below displays the issues sorted by date the issue was reported.
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email or the discussion forums. Visit the NI website to contact us. Also, consider contacting us if you find a workaround for an issue that isn't listed in the document so that we may update the document.
The following items are known issues in Real-Time Hypervisor 3.0 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Compatibility | ||||||
| 253522 Return | Real-Time Hypervisor systems hang at boot when certain USB devices are connected Certain models of USB devices (keyboards, mice, USB hubs, etc) cause Real-Time Hypervisor systems to hang at boot. Workaround: Do not use Hypervisor systems with USB hubs, try replacing offending keyboard/mice with different makes/models.
| |||||
| 346635 Return | Hypervisor systems do not support the NI-IEEE 1394 driver Installing the NI-IEEE 1394 driver on the Real-Time side of a Real-Time Hypervisor system is not supported and may cause the system to hang on boot. Workaround: Do not install NI-IEEE 1394 drivers on a Real-Time Hypervisor system.
| |||||
| 408140 Return | Acronis® True Image software does not run properly on Hypervisor 3.0 Previous versions of Hypervisor were compatible with the Acronis® True Image recovery software, however there is a problem with Hypervisor 3.0 that prevents the software from imaging properly. Workaround: Do not use Acronis® True Image software on Hypervisor 3.0 systems.
| |||||
| Functions, VIs, and Express VIs | ||||||
| 367469 Return | Hypervisor system crashes when RT Debug String.vi is repeatedly called in a loop Hypervisor 3.0 systems may crash when repeatedly calling RT Debug String.vi inside a loop that runs for an extended period of time Workaround: Be selective when calling the VI based on the string it would output and / or decimate the number of calls to the VI within the loop
| |||||
| Miscellaneous | ||||||
| 391482 Return | Unable to open Hypervisor shared memory blocks with long names When a shared memory block is created on one operating system and given a name longer than 61 characters, it will fail to open on the other operating system, though it can be opened on the operating system that created the block. Workaround: Use names for shared memory blocks less than 61 characters in length.
| |||||
| 426984 Return | Hypervisor configuration manager incorrectly routes interrupt lines for NI-8234 When the NI-8234 is set to run in RT with Hypervisor 3.0, the configuration manager incorrectly routes the interrupt lines in the chassis Workaround: Manually configure the cards in the chassis to route the triggers correctly to use the NI-8234 in RT
| |||||
| NI Services | ||||||
| 385227 Return | Hypervisor shared memory service does not start automatically on first boot after software installation There is an intermittent problem with Hypervisor 3.0 that causes the shared memory service to fail to startup on the first boot after installing Hypervisor software. This problem occurs relatively infrequently but is easily resolved. Workaround: Reboot into Windows, reapply settings and boot back into Hypervisor.
| |||||
The following items are known issues in Real-Time Hypervisor 3.0 sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 253522 Return | Real-Time Hypervisor systems hang at boot when certain USB devices are connected Certain models of USB devices (keyboards, mice, USB hubs, etc) cause Real-Time Hypervisor systems to hang at boot. Workaround: Do not use Hypervisor systems with USB hubs, try replacing offending keyboard/mice with different makes/models.
| |||||
| 346635 Return | Hypervisor systems do not support the NI-IEEE 1394 driver Installing the NI-IEEE 1394 driver on the Real-Time side of a Real-Time Hypervisor system is not supported and may cause the system to hang on boot. Workaround: Do not install NI-IEEE 1394 drivers on a Real-Time Hypervisor system.
| |||||
| 391482 Return | Unable to open Hypervisor shared memory blocks with long names When a shared memory block is created on one operating system and given a name longer than 61 characters, it will fail to open on the other operating system, though it can be opened on the operating system that created the block. Workaround: Use names for shared memory blocks less than 61 characters in length.
| |||||
| 408140 Return | Acronis® True Image software does not run properly on Hypervisor 3.0 Previous versions of Hypervisor were compatible with the Acronis® True Image recovery software, however there is a problem with Hypervisor 3.0 that prevents the software from imaging properly. Workaround: Do not use Acronis® True Image software on Hypervisor 3.0 systems.
| |||||
| 385227 Return | Hypervisor shared memory service does not start automatically on first boot after software installation There is an intermittent problem with Hypervisor 3.0 that causes the shared memory service to fail to startup on the first boot after installing Hypervisor software. This problem occurs relatively infrequently but is easily resolved. Workaround: Reboot into Windows, reapply settings and boot back into Hypervisor.
| |||||
| 367469 Return | Hypervisor system crashes when RT Debug String.vi is repeatedly called in a loop Hypervisor 3.0 systems may crash when repeatedly calling RT Debug String.vi inside a loop that runs for an extended period of time Workaround: Be selective when calling the VI based on the string it would output and / or decimate the number of calls to the VI within the loop
| |||||
| 426984 Return | Hypervisor configuration manager incorrectly routes interrupt lines for NI-8234 When the NI-8234 is set to run in RT with Hypervisor 3.0, the configuration manager incorrectly routes the interrupt lines in the chassis Workaround: Manually configure the cards in the chassis to route the triggers correctly to use the NI-8234 in RT
|
Document last updated on 11/7/2014