NI Real-Time Hypervisor 1.0, 2.0, 2.1, and 3.0 Known Issues

Overview

This document contains the NI Real-Time Hypervisor 1.0-3.0 known issues that were discovered before and since the release of the NI Real-Time Hypervisor 1.0-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.

Known Issues

The following items are known issues in the NI Real-Time Hypervisor 1.0-3.0.

NI Real-Time Hypervisor 3.0

  1.  Real-Time Hypervisor systems do not support the NI-IEEE 1394 Driver (CAR 346635 )
    • Installing the NI-IEE 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.

NI Real-Time Hypervisor 2.1

  1.  Real-Time Hypervisor systems hang at boot when certain USB devices are attached (CAR 253522)
    • An issue has been reported where using certain USB peripherals, including keyboards and USB hubs, with Real-Time Hypervisor systems may cause the system to hang at boot time. If you are experiencing this issue, please report it to National Instruments support and try the following workaround:
      • Unplug all USB devices after selecting Real-Time Hypervisor from the boot menu
      • If the system boots properly after unplugging devices, attempt to isolate the problem USB peripheral and replace it with an equivalent device.
  2.  Hypervisor controller repeatedly reboots at or before Windows splash screen during hypervisor boot (possible Blue Screen of Death)
    • An issue has been reported where performing certain actions on the Windows side of Real-Time Hypervisor systems may cause an uncontrolled reboot when subsequently booting into the Hypervisor (note that this happens only when the BIOS SATA mode is set to IDE compatibility mode). If you are experiencing this:
      • Open the command prompt and type sc delete vlx
      • Browse to <National Instruments>/Real-Time Hypervisor/SystemFiles/BlockDriver/ and find the inf file in that directory
      • Right-click on the inf file and select install
    • Symantec Antivirus released after May 2011 has also been known to cause this problem. Symantec Antivirus must be uninstalled to fix the problem.
  3.  Cannot connect to Virtual Console /dev/ttyS3 from minicom on Linux Hypervisor.
    • After installing NI Real-Time Hypervisor for Linux, an issue has been reported where it may not be possible to connect to the Virtual console /dev/ttyS3 from minicom. To resolve this issue, do the following:
      • Open a terminal window, and type "setserial /dev/ttyS3 uart 16650".
  4.  Error -312505 When Using Shared Memory on a Non-Administrator Account
    • When using the Ni Real-Time Hypervisor Shared Memory API with a non-administrator Windows account, error -312505 will occur. This error usually means that Shared Memory has not been configured in the NI Real-Time Hypervisor Manager. However, in the case where the Shared Memory API works with an administrator account but not a non-administrator account, the problem is not that the Shared Memory is not configured.
  5.  Real-Time Hypervisor systems do not support the NI-IEEE 1394 Driver (CAR 346635 )
    • Installing the NI-IEE 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.

NI Real-Time Hypervisor 2.0
Note that all new Real-Time Hypervisor systems shipped by NI use version 2.1 of the software. When installing Real-Time Hypervisor software manually, it is recommended that you use the 2.1 version. This reference information is provided for Real-Time Hypervisor 2.0 customers.

  1.  LabVIEW Real-Time side fails to boot in hypervisor mode when 3 cores are assigned to a quad-core hypervisor controller
    • Fixed by the NI Real-Time Hypervisor 2.0 f2 patch and in NI Real-Time Hypervisor 2.1 release.
    • This issue occurs due to the underlying hypervisor (VLX) running out of memory during booting. Workaround:
      • Boot into Windows only
      • Open NIHypervisorManager.ini located at <National Instruments>\Real-Time Hypervisor\Configuration Utility
      • On the second line of the file, change vram=160m to vram=170m
      • Save and close the file
      • Open up the Hypervisor Configuration Manager, make a configuration change and apply it. Note: you must make a change to the configuration for the ini file to be inspected again.
      • Now boot into Hypervisor and you will have access to the RT partition. Note: If you have the RT OS configured to wait on console input to boot, you will need to open HyperTerminal to start the RT OS.

  2.  Virtual Ethernet MAC addresses change on Real-Time Hypervisor systems 
    • Fixed in the NI Real-Time Hypervisor 2.1 release.
    • This issue occurs due to the way that Virtual NICs pull their MAC address dynamically from other physical NICs in the system. Please contact National Instruments support if you need to ensure that the MAC addresses are fixed (for example when assigning an IP address based on MAC address).

  3.  Startup EXE deployed to Real-Time Hypervisor system intermittently errors out on boot
    • An issue has been reported where certain LabVIEW Real-Time startup EXEs may intermittently fail to boot on Real-Time Hypervisor systems. Please contact National Instruments support if you are experiencing this problem.

  4.  Hypervisor controller repeatedly reboots at or before Windows splash screen during hypervisor boot (possible Blue Screen of Death)
    • An issue has been reported where performing certain actions on the Windows side of Real-Time Hypervisor systems may cause an uncontrolled reboot when subsequently booting into the Hypervisor. If you are experiencing this:
      • Open the command prompt and type sc delete vlx
      • Browse to <National Instruments>/Real-Time Hypervisor/SystemFiles/BlockDriver/ and find the inf file in that directory
      • Right-click on the inf file and select install
    • Symantec Antivirus released after May 2011 has also been known to cause this problem. Symantec Antivirus must be uninstalled to fix the problem.

  5.  Real-Time Hypervisor systems hang at boot when certain USB devices are attached (CAR 253522)
    • An issue has been reported where using certain USB peripherals, including keyboards and USB hubs, with Real-Time Hypervisor systems may cause the system to hang at boot time. If you are experiencing this issue, please report it to National Instruments support and try the following workaround:
    • Unplug all USB devices after selecting Real-Time Hypervisor from the boot menu
    • If the system boots properly after unplugging devices, attempt to isolate the problem USB peripheral and replace it with an equivalent device

  6.  The baud rate of the serial port onboard Hypervisor controllers is fixed to 9600 bps
    • Fixed in the NI Real-Time Hypervisor 2.1 release.
    • The baud rate of the serial port onboard Hypervisor controllers is fixed to 9600 bps. The buffer size is also restricted. It is recommended that you use an additional Serial module when using a Hypervisor system for applications that depend on Serial communication.
  7.  Cannot connect to Virtual Console /dev/ttyS3 from minicom on Linux Hypervisor.
    • After installing NI Real-Time Hypervisor for Linux, an issue has been reported where it may not be possible to connect to the Virtual console /dev/ttyS3 from minicom. To resolve this issue, do the following:
    • Open a terminal window, and type "setserial /dev/ttyS3 uart 16650".
  8.  Communications Problems with Bridged NICs after Hypervisor Reboot
    • Fixed in the NI Real-Time Hypervisor 2.1 release.
    • Bridging the virtual ethernet with the physical ethernet port in Windows allows the RT OS to be accessed through the physical NIC assigned to Windows. This will work when first set up, however, after one or more reboots the RT OS will become unreachable.
      •  To fix this problem, delete and re-add the bridged connection every time you reboot in to the Hypervisor, or upgrade to NI Real-Time Hypervisor 2.1.
  9.  Error -312622 when using Hypervisor Configuration Managerwhen using a RAID drive
    • Fixed in the NI Real-Time Hypervisor 2.1 f1 Patch.
    • Workaround provided in the following KnowledgeBase article: Why Does My Hypervisor Configuration Manager Fail To Run When Using A RAID Drive?
  10.  Real-Time Hypervisor systems do not support the NI-IEEE 1394 Driver (CAR 346635 )
    • Installing the NI-IEE 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.


  11. NI Real-Time Hypervisor 1.0
    Note that all new Real-Time Hypervisor systems shipped by NI use version 2.1 of the software. When installing Real-Time Hypervisor software manually, it is recommended that you use the 2.1 version. This reference information is provided for Real-Time Hypervisor 1.0 customers.
    1.  2 GB RAM Limitation
      • Installing more than 2 GB of RAM causes LabVIEW RT to boot on Hypervisor systems. This issue was fixed in the Real-Time Hypervisor 2.0 release.

    2.  The baud rate of the serial port onboard Hypervisor controllers is fixed to 9600 bps
      • The baud rate of the serial port onboard Hypervisor controllers is fixed to 9600 bps. The buffer size is also restricted. It is recommended that you use an additional Serial module when using a Hypervisor system for applications that depend on Serial communication.

    3.  Real-Time Hypervisor systems do not support the NI-IEEE 1394 Driver (CAR 346635 )
      • Installing the NI-IEE 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.

 

Additional Resources

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).