Why is File I/O slower from the Real-Time OS?
The controller hard drive is owned by Windows, but the Real-Time Hypervisor allows the Real-Time OS read and write access to the disk. This additional access path adds overhead to the read and write process, slowing file I/O operations.
What happens to the Real-Time OS if Windows crashes?
The controller hard drive is owned by Windows, so a Windows crash prevents the Real-Time OS from accessing the hard drive. Any program running at the time of the crash will continue running but return errors when accessing the hard drive. National Instruments recommends monitoring disk access in real-time code and safely shutting down the real-time application if a Windows failure occurs.
Why do I have to assign a device to a specific operating system?
PXI devices are partitioned to improve performance and maintain the determinism of the Real-Time OS. Shared or hosted devices compromise determinism and exhibit decreased performance due to resource management issues.
Can I assign the number of processor cores allocated to Windows XP and LabVIEW Real-Time?
With Real-Time Hypervisor 1.0, the Real-Time Hypervisor Manager statically assigns the first processor core to Windows and the remaining cores to LabVIEW Real-Time. With Real-Time Hypervisor 2.0, each processor core can be assigned to either operating system with the Real-Time Hypervisor Manager.
Why does Windows have only one CPU when I boot into Windows?
With Real-Time Hypervisor 1.0, Windows operates in Standard Mode, which does not support multiple processors or multiple cores. However with Real-Time Hypervisor 2.0, Windows can be configured to use multiple processors or multiple cores. Use the Real-Time Hypervisor Manager to configure which CPU cores are assigned to each operating system.
NOTE: Microsoft does not recommend switching between ACPI (mulit-core enabled) and Standard hardware abstraction layer modes. For more information please review Microsoft's HAL options after Windows XP or Windows Server 2003 Setup.
How much RAM does a Real-Time Hypervisor system support?
For Real-Time Hypervisor 1.0, there is a minimum requirement of 1 GB of RAM with a maximum of 2 GB. Using more than 2 GB of RAM on a Real-Time Hypervisor 1.0 system can cause the system to crash unexpectedly or not allow the Real-Time operating system to boot.
For Real-Time Hypervisor 2.0 and later, there is a minimum requirement of 1 GB of RAM with a maximum of 4 GB.
Can I use the NI-Watchdog timer on the Real-Time OS?
As of Real-Time Hypervisor 2.0, there is no way to assign the NI-Watchdog timer to any OS. Therefore, watchdog timer functionality defaults to Windows and is unavailable to the Real-Time OS.