A general-purpose virtualization platform for systems using a hardware abstraction software layer

A proxy virtual machine emulating hardware components with a hardware abstraction layer addresses the challenge of limited hardware access, enabling early development, cost-effective testing, and high-fidelity training.

CN111123736BActive Publication Date: 2024-12-03THE BOEING CO
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN201910962065.7
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2018-10-31
Filing Date
2019-10-11
Publication Date
2024-12-03
Estimated Expiration
2039-10-11

AI Technical Summary

Technical Problem

Developers of complex electronic systems face challenges due to limited access to physical hardware during development, as hardware vendors often restrict hardware details due to intellectual property concerns or contractual obligations, leading to delayed and costly integration of hardware specifications.

Method used

A method and system for testing and training using a proxy virtual machine that emulates hardware components, allowing execution of application software without direct hardware access, utilizing a hardware abstraction software layer like ARINC 653 to create a common virtualization platform.

Benefits of technology

Enables early development and testing, reduces costs by avoiding multiple virtual platform constructions, and allows early detection of design defects, providing significant cost savings and facilitating high-fidelity trainers.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN111123736B_ABST
    Figure CN111123736B_ABST
Patent Text Reader

Abstract

A general virtualization platform for systems using a hardware abstraction software layer. Techniques for testing a physical hardware system by executing hardware system application software on a corresponding simulated proxy physical hardware system in a proxy virtual machine are presented. The techniques include: obtaining a proxy physical hardware system that matches aspects of the physical hardware system; constructing a proxy virtual machine in a virtualization system; simulating hardware components of the proxy physical hardware system in the proxy virtual machine using the virtualization system; executing a hardware abstraction software layer in the proxy virtual machine; executing hardware system application software on the proxy physical hardware system in the proxy virtual machine using a memory-mapped at least one adapter by the hardware abstraction software layer of the virtualization system; and testing the physical hardware system by executing the hardware system application software in the proxy virtual machine on the proxy physical hardware system using the virtualization system.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to modeling and virtualization. Specifically, the present disclosure provides high-fidelity simulation of a dedicated hardware system by using a hardware abstraction software layer. Background Art

[0002] During the engineering, development, and testing of complex electronic systems and devices, physical hardware and its specifications can be limited resources. Therefore, developers involved in the development of these systems (e.g., scientists, engineers, software developers, and testers) may not have access to the physical hardware until very late in the development of the systems and devices. For example, there is often a significant amount of product development time between when the specifications and design of a hardware system are completed and when the first early versions of the hardware system are available for development and testing.

[0003] With knowledge of the specifications of the physical hardware, a virtualization platform, which may be an embedded computing device (e.g., an avionics computer) that executes software for the physical hardware, can sometimes be used to address the limited availability of the physical hardware itself. However, the use of such a virtualization platform requires at least knowledge of the specifications of the physical hardware, if not actual access. These physical hardware specifications may not be readily available to allow construction of the virtualization platform. Hardware vendors are sometimes reluctant to provide the necessary hardware details, for example, due to intellectual property issues, or simply because there is no contractual obligation to provide this information. Sometimes the necessary hardware information can be negotiated for publication, but this can take months and is often accompanied by restrictive costs and licensing considerations. Summary of the invention

[0004] According to various embodiments, a method for testing a physical hardware system by executing hardware system application software on a corresponding simulated proxy physical hardware system in a proxy virtual machine is proposed. The method includes: obtaining a proxy physical hardware system that matches various aspects of the physical hardware system; constructing a proxy virtual machine from the proxy physical hardware system in a virtualization system; emulating hardware components of the proxy physical hardware system in the proxy virtual machine using the virtualization system; executing a hardware abstraction software layer in the proxy virtual machine; executing the hardware system application software in the proxy virtual machine on the proxy physical hardware system using a memory map that reproduces the memory locations used by the proxy physical hardware system and using at least one adapter that maps data between the proxy virtual machine and the hardware system application software through the hardware abstraction software layer of the virtualization system; and testing the physical hardware system by executing the hardware system application software in the proxy virtual machine on the proxy physical hardware system using the virtualization system.

[0005] Various optional features of the above-described embodiments include the following. The hardware abstraction software layer may include an ARINC 653 operating system. At least one adapter may be executed in the hardware abstraction software layer. At least one adapter may be executed in a proxy virtual machine. At least one adapter may include a first adapter executed in the software abstraction layer and a second adapter executed in the proxy virtual machine. The physical hardware system may include an avionics system including a plurality of line replaceable units. The method may include: modifying the physical hardware system based on the test to generate a modified physical hardware system; and deploying the modified physical hardware system. Obtaining a proxy physical hardware system that matches the physical hardware system may include obtaining a proxy physical hardware system that has at least the same processor as the processor of the physical hardware system. Constructing a proxy virtual machine from the proxy physical hardware system in a virtualization system may include simulating at least the processor of the proxy physical hardware system. Obtaining a proxy physical hardware system that matches the physical hardware system may proceed without accessing the specifications of the physical hardware system. The method may include using a virtualization system to simulate at least one vehicle physical hardware system and a user of the training vehicle physical hardware system.

[0006] According to various embodiments, a system for testing a physical hardware system by executing hardware system application software on a corresponding emulated proxy physical hardware system in a proxy virtual machine is provided. The system includes: a proxy physical hardware system that matches aspects of the physical hardware system; and a virtualization system that includes a proxy virtual machine constructed from the proxy physical hardware system, wherein the proxy virtual machine emulates hardware components of the proxy physical hardware system and executes a hardware abstraction software layer that executes the hardware system application software in the proxy virtual machine using a memory map that reproduces memory locations used by the proxy physical hardware system and using at least one adapter that maps data between the proxy virtual machine and the hardware system application software.

[0007] Various optional features of the above-described embodiments include the following. The hardware abstraction software layer may include an ARINC 653 operating system. At least one adapter may be executed in the hardware abstraction software layer. At least one adapter may be executed in a proxy virtual machine. At least one adapter may include a first adapter executed in the software abstraction layer and a second adapter executed in the proxy virtual machine. The physical hardware system may include an avionics system including a plurality of line replaceable units. The system may include a modified physical hardware system modified based on testing the physical hardware system using a virtualization system. The proxy physical hardware system may have at least a processor that is the same as a processor of the physical hardware system. A proxy virtual machine constructed from the proxy physical hardware system may at least emulate a processor of the proxy physical hardware system.

[0008] According to various embodiments, a method for training a person to operate a physical hardware system by executing a hardware system application software on an emulated proxy physical hardware system in an agent virtual machine by training the person to operate, and the emulated proxy physical hardware system corresponds to the physical hardware system. The method includes: obtaining an agent physical hardware system that matches various aspects of the physical hardware system; constructing an agent virtual machine from the agent physical hardware system in a virtualization system; emulating hardware components of the agent physical hardware system in the agent virtual machine using the virtualization system; executing a hardware abstraction software layer in the agent virtual machine; executing the hardware system application software in the agent virtual machine on the agent physical hardware system using the hardware abstraction software layer of the virtualization system and at least one adapter that maps data between the agent virtual machine and the hardware system application software; and training a person to operate the physical hardware system using the virtualization system by executing the hardware system application software in the agent virtual machine on the agent physical hardware system by training the person to operate.

[0009] Various optional features of the above embodiments include the following: The physical hardware system may include a vehicle physical hardware system. The vehicle may include an aircraft, and the virtualization system may include a flight simulator. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate the present teachings and, together with the description, serve to explain the principles of the present disclosure.

[0011] Figure 1 A system block diagram illustrating an example of an environment for executing a physical-to-agent adapter in a hardware abstraction software layer for implementing systems and processes according to aspects of the present disclosure is shown.

[0012] Figure 2 A system block diagram illustrating an example of an environment having physical-to-proxy adapters in a proxy virtual machine layer for implementing systems and processes according to aspects of the present disclosure is shown.

[0013] Figure 3 A system block diagram illustrating an example of a physical hardware system according to aspects of the present disclosure is shown.

[0014] Figure 4 A system block diagram illustrating an example of a proxy physical hardware system according to aspects of the present disclosure is shown.

[0015] Figure 5 A system block diagram illustrating an example of a virtualization system according to aspects of the present disclosure is shown.

[0016] Figure 6 An example of memory mapping according to an embodiment of the present disclosure is shown.

[0017] Figure 7 A process flow diagram illustrating an exemplary process 700 for testing a physical hardware system by executing hardware system application software on a corresponding emulated proxy physical hardware system in a proxy virtual machine.

[0018] Figure 8 A flow chart illustrating an exemplary process for constructing a proxy virtual machine from a proxy physical hardware system in a virtualization system according to the virtual machine construction aspects of the present disclosure.

[0019] Fig. 9 A process flow diagram illustrating an exemplary process of simulating components of a proxy physical hardware device according to an embodiment of the present disclosure.

[0020] It should be noted that some details of the drawings have been simplified and are drawn to facilitate understanding of the present teachings rather than maintaining strict structural accuracy, detail, and scale. DETAILED DESCRIPTION

[0021] Reference will now be made in detail to the disclosed examples, which are illustrated in the accompanying drawings. Whenever possible, the same reference numerals will be used throughout the accompanying drawings to represent the same or similar parts. In the following description, reference is made to the accompanying drawings that form a part thereof and that illustrate specific examples as illustrations. These examples are described in sufficient detail to enable those skilled in the art to practice them, and it will be understood that other examples may be utilized and may be changed without departing from the scope of the present disclosure. Therefore, the following description is exemplary only.

[0022] In a typical virtual machine construction that emulates physical hardware and executes physical hardware software applications (e.g., executable software) on the virtual machine, many details about the hardware of a particular platform must be known: memory mapping, interrupt tables, firmware registers, etc. However, a hardware abstraction software layer, such as the Aeronautical Radio Incorporated (ARINC) 653 standard architecture (Annapolis, Maryland, USA - formerly Rockwell Collins), abstracts most of the details of the underlying hardware platform on which the software applications of the physical hardware run. Specifically, some embodiments utilize the hardware abstraction software layer provided by, for example, ARINC 653 to create a single general virtualization platform that works for many different platforms. These embodiments can be used to develop and test, for example, avionics line replaceable units (LRUs) and other specialized hardware devices. Specifically, according to some embodiments, software applications (sometimes as unmodified binary files) can be executed on the virtualization platform.

[0023] In order to avoid the need for hardware access or hardware specification access, some embodiments replace proxy physical hardware with simulated hardware. In these embodiments, the proxy hardware system to be simulated is selected to match various aspects of the actual hardware system. The use of such a proxy hardware system avoids the need for hardware access or knowledge of its specifications. This allows some embodiments, in part, to provide a general virtualization platform that allows software applications to run unmodified in a virtual machine without knowing most of the details of the physical hardware.

[0024] Embodiments provide many advantages. For example, creating a common virtualization platform allows cost savings by avoiding the construction of multiple virtual platforms. As another example, some embodiments provide virtual platforms very early in product development, thereby allowing early development and testing activities of physical platforms and their software applications. Subsequently, early use of virtualization platforms allows early discovery of design defects in product development. This early problem discovery provides significant cost savings. If the problem is detected in laboratory testing as opposed to flight testing, one order of magnitude of cost savings can be achieved. Similarly, if the problem is detected in requirements / design as opposed to laboratory testing, another order of magnitude of cost savings can be achieved. Therefore, some embodiments provide for problem discovery in the requirements / design phase of a program, which allows two orders of magnitude of cost savings to be achieved.

[0025] In addition, embodiments may be used to create high-fidelity trainers, such as aircrew trainers and maintenance trainers. These embodiments provide the same ease of construction, reuse across platforms, and eliminate the need to reverse engineer hardware (eg, for trainer construction).

[0026] In summary, some embodiments simplify the creation of general virtual machines and virtualization platforms. Some embodiments provide virtual machines for corresponding hardware platforms whose detailed hardware information is unknown, without having to resort to time-consuming reverse engineering activities. Some embodiments allow early development of these virtualization platforms in the product development cycle. These and other advantages are presented in detail herein.

[0027] Figure 1A system block diagram illustrating an example of an environment 100 for implementing systems and processes according to aspects of the present disclosure is shown, wherein physical to proxy adapter software 134 is executed in a hardware abstraction software layer 132. The environment 100 may include a physical hardware system 102, a proxy physical hardware system 105, and a virtualization system 110. The physical hardware system 102 may include one or more computer-implemented hardware components and one or more communication channels. For example, the physical hardware system 102 may be an avionics LRU, such as a mission computer, a navigation unit, a communication unit, an engine management unit, a crew interface unit, a threat detection unit, an electronic countermeasures unit, a store management unit, an industrial control unit, etc. In addition, for example, the physical hardware system 102 may be an integrated avionics unit including one or more modules that include the functionality of some or all of the above-mentioned avionics units.

[0028] Although the above description Figure 1 As an existing physical hardware system 102, it will be understood that the physical hardware system 102 may be a new system under development and, therefore, not yet fully implemented or produced. In an implementation, the physical hardware system 102 may be a pre-prototype unit that is partially implemented in software and / or hardware. For example, the physical hardware system 102 may be software executed by a temporary computing device (e.g., a breadboard system, a test bench system, and / or a commercial off-the-shelf system).

[0029] The proxy physical hardware system 105 is selected to match various aspects of the physical hardware system 102. Such a proxy physical hardware system 105 may match physical hardware systems according to various standards presented herein. The proxy physical hardware system 105 may support a software abstraction layer such as ARINC 653. In addition, the proxy physical hardware system 105 may have the same processor and input / output type as the physical hardware system 102. In addition, for a proxy physical hardware system 105 that includes ARINC 653, the proxy physical hardware system 105 may also have an easily available ARINC 653 board support package (BSP). Therefore, if it supports at least the software abstraction layer, the physical proxy hardware system 105 matches various aspects of the physical hardware system 102. Additional matching criteria may include any one or a combination of having the same processor type, having the same input / output type, and having a BSP.

[0030] As a specific example, embodiments may utilize SBC 612 provided by Abaco Systems, which is a commercial off-the-shelf (COTS) single board computer (SBC). SBC 612 has a PowerPC P4080 processor and an already built Wind River VxWorks ARINC 653 BSP similar to some embodiments of physical hardware system 102.

[0031] The virtualization system 110 may be a computing system including hardware and software that can emulate other devices. In an implementation, the virtualization system 110 may be one or more general-purpose computers (e.g., servers or desktop computers) that host one or more proxy virtual machines 130 that emulate a physical hardware system (e.g., a proxy physical hardware system 105) and its hardware and software interfaces (e.g., peripherals, data links, interrupt behaviors, and timing requirements). In addition, the proxy virtual machine 130 executes hardware system application software 136 (e.g., a software executable file running in a partition), i.e., an exact or substantially exact copy (e.g., image) of the hardware system application software executed by the physical hardware system 102. In an implementation, the virtualization system 110 may include, for example, a hypervisor or virtual machine monitoring software. For example, the virtualization system 110 may use QUICK EMULATOR ("QEMU"), which is an open source software application that performs hardware virtualization.

[0032] The proxy virtual machine 130 may be an emulation of the proxy physical hardware system 105 within the virtualization system 110. Information used to create the virtual machine 130 may be obtained from the proxy physical hardware system 105 as well as from the hardware system application software 136 and the documentation 147 describing the proxy physical hardware system 105. For example, the hardware system application software 136 may be the application code of the physical hardware system 102 (e.g., an avionics LRU). The hardware system application software 136 may also include source code (e.g., application logic), interface code (e.g., timing and formatting), and / or interrupt logic for the hardware components and communication links included in the physical hardware system 102. The proxy operating system, hardware abstraction software layer, BSP, device driver, and boot loader 145 will replace similar functions on the proxy physical hardware system. The physical-to-adapter proxy software 134 is used to implement this replacement without modifying the hardware system application software 136. The proxy hardware system documentation 147 may be information that defines the operational requirements and operational details of the hardware components and communication links of the proxy physical hardware system 105. For example, the documentation 147 may be technical specifications and basic software. Any available physical hardware system documentation 149 can also be used for proxy virtual machine construction. However, the documentation 149 is often limited in scope or not available in the proxy virtual machine scenario.

[0033] The hardware abstraction software layer 132 is the same as or similar to the hardware abstraction software layer 153 found on the proxy physical hardware system 105. Figure 1As shown, the physical-to-proxy adapter software 134 is executed in the hardware abstraction software layer 132 (which may be ARINC 653) of the proxy virtual machine 130. The physical-to-proxy adapter software 134 accommodates differences in the physical hardware system 102 compared to the proxy physical hardware system 105. Specifically, the physical-to-proxy adapter software 134 maps input / output data between the hardware system application software 136 and the proxy virtual machine 130. For implementations where the hardware abstraction software layer 132 is an ARINC 653 operating system, the physical-to-proxy adapter software 134 may map internal ARINC 653 input / output messages generated and received from the hardware system application software 136 to virtual input / outputs in the proxy virtual machine 130.

[0034] The proxy virtual machine 130 can be used for engineering, development, and testing of the physical hardware system 102 before, during, and after its production. For example, before the actual production of the physical hardware system 102, the proxy physical hardware system 105 can be simulated by the proxy virtual machine 130 to develop and debug pre-production software that is expected to be implemented in the physical hardware system 102. Therefore, the development and testing of hardware and software can be carried out in parallel. In addition, during the development of the physical hardware system 102, when several (if any) physical hardware units are available, the developer can work with the proxy virtual machine 130 instead. Since the proxy virtual machine 130 is substantially matched with the physical hardware system 102, each developer involved in the development and production of the physical hardware system 102 can implement a copy of the proxy virtual machine 130 at its corresponding workstation (e.g., the corresponding virtualization system 110). The high-fidelity simulation provided by the proxy virtual machine 130 allows early detection of problems and will provide considerable cost savings during development. The updated program code 151 implemented in the proxy virtual machine 130 can be fed back into the physical hardware system 102 (when available) to increase the development rate. Additionally, proxy virtual machines 130 may be used to support, test, and update physical hardware systems 102 after they are placed into service. For example, in an aircraft accident investigation, a specific build of software used in an aircraft may be imaged (e.g., as hardware system application software 136) and executed in proxy virtual machines 130 using virtualization system 110. Additionally, proxy virtual machines 130 may be used in trainers (e.g., in a flight simulation system).

[0035] Figure 2 1 shows a system block diagram illustrating an example of an environment 101 for implementing systems and processes according to aspects of the present disclosure, wherein physical-to-agent adapter software 135 is executed in an agent virtual machine 130 layer. Figure 1 The physical to proxy adapter software 134, compared to the proxy physical hardware system 105, Figure 2The physical-to-agent adapter software 135 accommodates differences in the physical hardware system 102. Figure 1 The proxy adapter software 135 maps input / output data between the hardware system application software 136 and the proxy virtual machine 130. Because the proxy adapter software 135 is implemented in the virtualization layer of the proxy virtual machine 130, the adapter can be used to handle differences in operating system and hardware behavior, which is not possible when the proxy adapter software 134 is in the hardware abstraction layer 132. Such differences may include message format differences (e.g., message field arrangement and / or content), replacement and marking of code portions, and rerouting of hardware device accesses to comparable emulated hardware devices (e.g., timers). This can be performed to reconcile differences between the physical hardware system 102 and the proxy hardware system 105 with physical hardware and possible hardware abstraction software layer and OS differences to allow the hardware system software application 136 to run on the proxy hardware system 105 without modification or with limited modification.

[0036] The physical to proxy adapter software 135 can take various forms. As one example, it can be a virtual hardware device in the virtualization layer that the driver software interacts with to send input / output data. As another example, it can observe the simulated instruction execution to determine when input / output is attempted, then intercept those calls and send them out of the virtual machine's virtual input / output and generate an appropriate response to satisfy the application layer software that the send / receive is successful.

[0037] Note that some embodiments may include reference to Figure 1 The physical to agent adapter software 134 executed in the hardware abstraction software layer 132 shown and described and in reference to Figure 2 In these embodiments, the physical to agent adapter software 134 executed in the hardware abstraction software layer 132 may map input / output messages, while the physical to agent adapter software 135 executed in the agent virtual machine 130 layer may convert the physical to agent adapter software 135 intended for use as described above with reference to FIG. Figure 2 Messages for different hardware abstraction layer software implementations 132 are described.

[0038] Figure 3 A system block diagram illustrating an example of a physical hardware system 102 according to aspects of the present disclosure is shown. The physical hardware system 102 can be the same or similar to that previously described.

[0039] The physical hardware system 102 may include any type of computing system, including general and / or special purpose hardware (e.g., a personal computer, a server, a dedicated computing device, etc.) capable of executing computer program instructions installed thereon. It will be understood that the physical hardware system 102 is merely representative of various possible equivalent computing devices. To this extent, in embodiments, the functionality provided by the physical hardware system 102 may be any combination of general and / or special purpose hardware and / or computer program instructions for various applications (e.g., industrial control and / or automation). In an implementation, the physical hardware system 102 may be a dedicated device such as an avionics LRU.

[0040] The physical hardware system 102 may include various components, including one or more processors 325, one or more memory devices 331, one or more storage devices 333 (e.g., memory devices or storage systems), one or more input / output devices 335 (I / O devices), and one or more network interfaces 337 (e.g., network interface devices). The processor 325 may include a microprocessor, a microchip, and / or an application-specific integrated circuit. The memory device 331 may include one or more local storage devices (e.g., random access memory (RAM) and cache memory) used during the execution of program instructions. The storage device 333 may include a computer-readable non-volatile hardware device that stores information and program instructions. For example, the storage device 333 may be one or more flash drives, non-volatile memory, and / or a hard drive. The input / output device 335 may include any device (e.g., a user interface) that enables a person to interact with the physical hardware system 102 and / or any device that enables the physical hardware system 102 to communicate with one or more other computing devices using any type of communication link. For example, the input / output device 335 may be a touch screen display, a pointing device, a keyboard, etc. The network interface 337 may include any transceiver device configured to send and receive data via a network communication link (eg, system communication bus 341).

[0041] Additionally, the physical hardware system 102 may include one or more communication channels 345 (e.g., a data bus) through which the processor 325, the memory device 331, the storage device 333, the input / output device 335, and the network interface device 337 may communicate. Furthermore, the physical hardware system 102 may include an interrupt controller 349, which may be a programmable device for managing communications of the processor 325, the memory device 331, the storage device 333, the input / output device 335, and / or the network interface device 337 over the communication channel 345, including allowing interrupts thereto to be assigned priority levels.

[0042] Processor 325 executes computer program instructions (e.g., operating system and / or application programs) that may be stored in memory device 331 and / or storage device 333. For example, one or more processors 325 may execute program instructions of boot loader 355 and hardware system application software 136. Boot loader 355 may include program instructions to initiate operation of physical hardware system 102 by loading an operating system. Hardware system application software 136 may include application specific program instructions (e.g., avionics software).

[0043] Figure 4 A system block diagram illustrating an example of a proxy physical hardware system 105 according to aspects of the present disclosure is shown. The proxy physical hardware system 105 is selected according to specified criteria to match aspects of a physical hardware system (e.g., physical hardware system 102). Such criteria may include supporting the same (or similar) hardware abstraction software layer 153, having the same processor type, having the same input / output type, and having any one or combination of a BSP, a device driver, and a boot loader. Thus, the proxy physical hardware system 105 includes one or more processors 425 (which may be the same as the processor 325 of the physical hardware system 102), one or more memory devices 431 (which may be the same as or different from the memory device 331), one or more storage devices 433 (which may be the same as or different from the storage device 333), one or more input / output devices 435 (which may be the same as or different from the input / output device 335), and one or more network interface devices 437 (which may be the same as or different from the network interface device 337). As in physical hardware system 102, proxy physical hardware system 105 may include one or more communication channels 445 (which may be the same as or different from communication channels 345), interrupt controller 449 (which may be the same as or different from interrupt controller 349), and boot loader 455 (which may be the same as or different from boot loader 355). As used herein, processor 425, memory device 431, storage device 433, input / output device 435, network interface device 437, communication channel 445, and interrupt controller 449 are examples of hardware components. With some modifications to hardware system application software 136 of physical hardware system 102, hardware system application software 136 may run on proxy physical hardware system 105. Proxy physical hardware system 105 is selected to include hardware that may be emulated by virtual hardware (e.g., proxy virtual machine 130) using a virtualization system (e.g., virtualization system 110). According to aspects of the present disclosure, proxy physical hardware system 105 selection and proxy virtual machine 130 creation are accomplished to support hardware system application software 136 execution on the proxy virtual machine 130 with little or no modification to the hardware system application software 136 .

[0044] Figure 5A system block diagram illustrating an example of a virtualization system 110 is shown, which may be used with the above-mentioned (eg, Figure 1 and / or Figure 2 The virtualization system 110 may be the same or similar to the virtualization system 110 of the present invention. The virtualization system 110 includes hardware and software that performs the processes and functions disclosed herein. The virtualization system 110 may include any type of computing system, including a combination of general and / or special-purpose hardware that is capable of executing computer program instructions installed thereon to perform the disclosed techniques.

[0045] The virtualization system 110 includes a computing device 503, an input / output (I / O) device 513, and a storage device 515. The I / O device 513 may include any device that enables a person to interact with the computing device 503 (e.g., a user interface) and / or any device that enables the computing device 503 to communicate with one or more other computing devices using any type of communication link. For example, the I / O device 513 may be a touch screen display, a pointing device, a keyboard, etc.

[0046] The storage device 515 may include a computer-readable non-volatile hardware storage device that stores information and program instructions. For example, the storage device 515 may be one or more flash drives and / or hard drives. According to aspects of the present disclosure, the storage device 515 may store hardware system program code (e.g., hardware system application software 136), one or more memory maps 519 of the proxy physical hardware system 105, interrupt logic 521, and device library 523. The hardware system application software 136 may be application software of a physical hardware system (e.g., physical hardware system 102). In an implementation, the program code substantially mirrors the program code of the physical hardware system 102. The memory map 519 describes the connection between the components of the physical hardware system from the perspective of the memory interface. In an implementation, the memory map 519 includes information defining the location of the memory blocks of the hardware components in the memory 431 of the proxy hardware system 105. For example, the memory map 519 may represent the location of the information of the memory registers of the hardware components of the proxy physical hardware system 105 as an offset relative to the starting memory address. The interrupt logic 521 may be information describing the interrupt function of the physical hardware system, as described below. Device library 523 may be a repository of computer-readable information and instructions describing a simulation of one or more physical hardware systems (eg, proxy physical hardware system 105 ) that may be pre-created and stored for future use.

[0047] In an embodiment, the computing device 503 includes one or more processors 539 (e.g., microprocessors, microchips, or application specific integrated circuits), one or more memory devices 541 (e.g., RAM, read-only memory (ROM)), one or more input / output interfaces 543, and one or more network interface devices 545. The memory device 541 may include local memory (e.g., random access memory and cache memory) used during the execution of program instructions. In addition, the computing device 503 includes at least one communication channel 544 (e.g., a data bus) for the computing device 503 to communicate with the input / output device 513 and the storage device 515. The processor 539 executes computer program instructions (e.g., an operating system and / or application programs) that may be stored in the memory device 541 and / or the storage device 515.

[0048] The processor 539 may also execute computer program instructions of a virtualization application 551 (e.g., QEMU) and a trainer, test and / or evaluation software 555. The virtualization application 551 may be the same or similar to that previously described. For example, the virtualization application 551 may include a hypervisor or virtual machine monitoring software. According to aspects of the present disclosure, the virtualization application 551 may use program code 517, memory mapping 519, interrupt logic 521, and / or device library 523 to provide a virtual machine (e.g., proxy virtual machine 130).

[0049] The trainer, test and / or evaluation software 555 may be an application or program including computer-readable instructions and information configured to test, evaluate and / or verify software. For example, the trainer, test and / or evaluation software 555 may execute a test routine that verifies that the program code of the hardware device behaves as expected in response to a predetermined scenario. In addition, the trainer, test and / or evaluation software 555 may execute a network security routine that tests the attack vectors of malware. For example, the trainer, test and / or evaluation software 555 may record the complete state of the virtual machine (registers, memory, hardware state, etc.) when the instruction is executed to allow observation and analysis of the damaged system. The trainer, test and / or evaluation software 555 may be used to provide a trainer for users of the physical system 102 (e.g., crew members or maintenance trainers).

[0050] It should be noted that computing device 503 represents various possible equivalent computing devices that can perform the processes described herein. To this extent, in embodiments, the functions provided by computing device 503 can be any combination of general and / or special purpose hardware and / or computer program instructions. In the disclosed embodiments, program instructions and hardware can be created using standard programming and engineering techniques, respectively.

[0051] Figure 6An example of a memory map 601 and an address space 602 of a virtualization system according to an implementation of the present disclosure is illustrated. The memory map 601 associates memory addresses of hardware components 603 of a physical hardware system (e.g., a proxy physical hardware system 105) with memory locations 605 (e.g., memory blocks of a memory device 541) of a virtualization system (e.g., a virtualization system 110). Information including the memory map 601 may be extracted from documentation (e.g., documentation 147) of the proxy physical hardware system 105. The address space 602 of a virtualized machine (e.g., a proxy virtual machine 130) may be a memory construct generated based on the memory map 601. For example, the address space 602 may include register memory addresses and ranges corresponding to locations of simulated components (e.g., components of the proxy physical hardware system 105) within the virtualization system. In an implementation, there may be three types of memory that are typically found in a memory map: volatile memory (e.g., RAM), non-volatile memory (e.g., flash memory), and memory mapped input / output. For example, volatile memory can be used to retrieve and store information during software execution. For example, non-volatile memory (e.g., NV memory) can be used to store software instructions and configuration information for execution. Memory-mapped input / output can be used to exchange information between hardware components, which can affect the behavior and response of the hardware components.

[0052] Figures 7 to 9 The flowcharts in illustrate examples of functionality and operation of possible implementations of systems, methods, and computer program products according to various implementations consistent with the present disclosure. Figures 7 to 9 Each block in the flowchart may represent a module, a segment or a portion of a program instruction, which includes one or more computer executable instructions for implementing the functions and operations shown. In some alternative implementations, the functions and / or operations shown in a particular block of the flowchart may not be arranged in a sequential manner. Figures 7 to 9 The blocks of the flowchart may occur in the order shown. For example, two blocks shown in succession may be executed substantially simultaneously, or the blocks may sometimes be executed in the reverse order, depending on the functions involved. It will also be noted that the individual blocks of the flowchart and combinations of blocks may be implemented by or using a special purpose hardware-based system or a combination of special purpose hardware and computer instructions that performs the specified functions or actions.

[0053] Figure 7A process flow diagram illustrating an exemplary process 700 for testing a physical hardware system by executing hardware system application software on a corresponding simulated proxy physical hardware system in a proxy virtual machine. Block 701 includes obtaining a proxy physical hardware system (e.g., proxy physical hardware system 105) that matches aspects of a physical hardware system (e.g., physical hardware system 102) to which specifications and / or access is sometimes unavailable or limited. Block 703 includes constructing a virtual machine (e.g., proxy virtual machine 130) from the proxy physical hardware system (e.g., proxy physical hardware system 105) using a virtualization system (e.g., computing device 503 executing virtualization software (e.g., virtualization application 551)), such as described below with reference to Figure 8 For example, a user (e.g., a developer) may execute program code (e.g., hardware system application software 136) from the physical hardware system 102 on the virtualization system 110. Block 705 includes emulating hardware components of the proxy physical hardware system in the virtual machine constructed at 703, such as described below with respect to Fig. 9 The virtual machine constructed at 703 and / or the hardware component simulated at 705 may be stored (e.g., in device library 523) for future reference and use in other implementations (e.g., other virtual machines including one or more hardware components). Block 707 includes executing a hardware abstraction software layer (e.g., ARINC 653) in the proxy virtual machine.

[0054] Box 709 includes executing the hardware system application software in the proxy virtual machine constructed at 703 using the hardware components simulated at 705. The execution may include using a memory map of the memory locations used by the proxy physical hardware system at 711. This may include using a memory map (e.g., memory map 601) to configure the address space of the virtualized machine (e.g., proxy virtual machine 130) to match the address space of the proxy physical hardware system and / or the simulated hardware components. The execution of 709 may also include exchanging information between the virtual machine and / or the simulated hardware components via registering the memory locations configured at 711 using the memory map. For example, the memory addresses and ranges of the memory registers of the physical hardware system and the hardware components may be registered with the virtual machine and used to implement the functions of the various memory registers found for the virtual machine and the simulated hardware components. By doing so, the virtual machine and the simulated hardware components can communicate via the memory structure of the virtual machine by reading and writing information in the same manner as the hardware components of the physical hardware system. The execution of 709 may also include using at least one adapter that maps data between the proxy virtual machine and the hardware system application software at 715. This mapping can be performed using physical-to-agent adapter software (e.g., physical-to-agent adapter software 134 and / or physical-to-agent adapter software 135). Such physical-to-agent adapter software can be executed in the hardware abstraction software layer to map input / output messages, as described above with reference to Figure 1 Alternatively, or in addition, such physical-to-proxy adapter software may be executed in a proxy virtual machine to convert messages intended for different hardware abstraction layer software, as described above with reference to Figure 2 shown and described.

[0055] Box 719 includes testing the physical hardware system using the virtualization system. More specifically, the virtualization system uses a virtual machine to perform testing (e.g., testing and evaluation) of the physical hardware system 102 and / or hardware components. Testing and evaluation may include software debugging, operational testing, integration testing, network security testing, etc. Box 723 includes the developer modifying at least one of the hardware system application software and / or the physical hardware system 102 based on the testing and evaluation performed at 719. Box 727 includes deploying modifications to the hardware system application software and / or the physical hardware system. For example, the modified software may be deployed to a production unit of the physical hardware system that is put into use. In addition, modifications to the hardware and / or software may be fed back into the design of a simulation, pre-production unit, or prototype of the physical hardware.

[0056] Figure 8A flowchart of an exemplary process of constructing 800 proxy virtual machines from proxy physical hardware systems in a virtualized system according to aspects of virtual machine construction of the present disclosure is illustrated. Block 803 includes collecting hardware information of a proxy physical hardware system (e.g., proxy physical hardware system 105) to be simulated. The information may be collected by a developer. The information collected at 803 may include specifications of hardware components and functional descriptions describing configurations of memory registers, hardware block diagrams, system architectures of physical hardware systems, memory mappings, interrupt connections, board support packages, and the like. In addition, the developer may collect information about software of the proxy physical hardware system. In some implementations, collecting software information includes decompiling or disassembling code stored on the physical hardware system.

[0057] Block 807 includes determining components of the proxy physical hardware system to emulate based on the information collected at 803. In an implementation, the developer identifies hardware components of the proxy physical hardware system that are not visible on the system memory map and therefore not directly accessible to software and do not necessarily need to be emulated. For example, cache memory or bridges that are not visible via the physical hardware system's memory map (e.g., memory map 601) may not be emulated.

[0058] Block 811 includes the developer using the method described previously herein (e.g., Figure 6 ), using the information collected at 803 to determine a memory map of the components determined at 807 in the same or similar manner as described above. The memory map indicates the components of the proxy physical hardware system and their corresponding locations in the memory of the proxy physical hardware system. Analyzing the memory map may include identifying memory devices and / or storage devices of the proxy physical hardware system, hardware devices of the proxy physical hardware system (e.g., input / output controllers, timers, bridges, interrupt controllers, block devices, control registers, etc.).

[0059] Block 815 includes generating a simulation of the component determined at 807 using virtualization software (e.g., virtualization application 551). Block 819 includes registering the simulated component in a memory location corresponding to the memory map determined at 811 (per block 815). For example, a developer may allocate a region (e.g., memory space 605) to a virtual machine (e.g., proxy virtual machine 130) representing a proxy physical hardware system and assign the simulated component to a block within the region (e.g., in address space 602), as previously described herein with respect to Figure 6 Described.

[0060] Box 823 includes that the developer uses the information collected at 803 to determine the interrupt design of the proxy physical hardware system. For example, the developer identifies the hardware component that uses the interrupt and determines the interrupt connection between the hardware component and the interrupt controller. In addition, the hardware schematic diagram showing the wiring between the input / output controller and the interrupt controller can be used to establish an interrupt connection for the virtual machine by tracing the interrupt line tracked in the schematic diagram to other hardware components. Alternatively, the board support package or the software in the device driver for the proxy physical hardware system 105 can be used to determine the interrupt connection. Doing so allows the interruption of the different components of the proxy physical hardware system to be identified. Box 827 includes that the developer links the input / output (box 815) of the virtual machine component to the simulated input / output controller. As an example, the Ethernet controller in the virtual machine can be connected to a virtual network interface card (NIC) (e.g., TAP device, etc.).

[0061] Fig. 9 900 is a flowchart of a process for emulating hardware components of a proxy physical hardware system in a proxy virtual machine using a virtualization system according to an embodiment of the present disclosure. Block 901 includes a developer collecting hardware information of a proxy physical hardware system (e.g., proxy physical hardware system 105) to be emulated. The information may be used in conjunction with the hardware components of the proxy physical hardware system (e.g., proxy physical hardware system 105) previously described herein. Figure 8 , 803). Block 903 includes the developer analyzing the proxy hardware system functionality based on the information collected at 901. For example, the developer may analyze the documentation (e.g., documentation 147) and identify hardware registers, interrupt functionality, delayed responses (e.g., using virtual machine virtual timers), and external virtual machine connections (virtual NIC, virtual ARINC 429, etc.).

[0062] Box 907 includes simulating the behavior of the hardware component in response to the memory access in the virtual machine. Such simulation may include simulating the processor of the proxy physical hardware system (for example, if the processor of the virtualized system is different from the processor of the proxy virtual machine). Box 911 includes the virtual machine simulating the interrupt behavior of the hardware component. Box 915 includes simulating the delayed response behavior of the hardware component. For example, the memory access to the hardware component register may cause the device register to be modified so that the specified behavior or interrupt can be signaled to the hardware component so that the activity occurs. In some cases of transmission through the Ethernet controller, the packet for transmission via Ethernet can be queued for transmission by writing it to a memory location. Doing so can trigger the system software to interrupt the Ethernet controller so that the Ethernet packet is sent from the virtual machine. In some cases of Ethernet reception, the packet will arrive at the virtual machine from an external device (for example, a virtual NIC), the packet will be stored in an internal queue, and then in some cases, the packet will be transferred to the system RAM using a direct memory access engine to transfer the Ethernet packet from the Ethernet controller internal memory to the system RAM, and after the transfer is completed, the interrupt will be signaled from the Ethernet controller to let the system software know that the Ethernet packet has arrived and is available in the system memory. For example, delayed response can be simulated by varying the speed of serial data to a given baud rate on the interface. Box 919 includes emulation of linking the emulated component to an external device. That is, box 919 includes linking the virtual machine to one or more emulated devices outside the proxy physical hardware system. For example, a link can be created between the external input / output of the emulated device and the emulation of the network device, and the hardware component can communicate with the proxy physical hardware system using the link. Box 921 includes comparing the behavior of the proxy virtual machine with the behavior of the physical hardware system. The successful execution of the physical hardware system application software is a good measure of the success of the proxy virtual machine and the physical to proxy adapter software located in the proxy virtual machine layer, the hardware abstraction software layer, or both.

[0063] In addition, this disclosure includes examples according to the following clauses:

[0064] Clause 1. A method for testing a physical hardware system by executing hardware system application software on a corresponding simulated proxy physical hardware system in a proxy virtual machine, the method comprising: obtaining a proxy physical hardware system that matches various aspects of the physical hardware system; constructing a proxy virtual machine from the proxy physical hardware system in a virtualization system; simulating hardware components of the proxy physical hardware system in the proxy virtual machine using the virtualization system; executing a hardware abstraction software layer in the proxy virtual machine; executing the hardware system application software in the proxy virtual machine on the proxy physical hardware system using a memory mapping that reproduces the memory locations used by the proxy physical hardware system and using at least one adapter that maps data between the proxy virtual machine and the hardware system application software by the hardware abstraction software layer of the virtualization system; and testing the physical hardware system by executing the hardware system application software in the proxy virtual machine on the proxy physical hardware system using the virtualization system.

[0065] Clause 2. The method of clause 1, wherein the hardware abstraction software layer comprises an ARINC 653 operating system.

[0066] Clause 3. The method of clause 1, wherein the at least one adapter is executed in a hardware abstraction software layer.

[0067] Clause 4. The method of Clause 1, wherein the at least one adapter is executed in a proxy virtual machine.

[0068] Clause 5. The method of Clause 1, wherein the at least one adapter comprises a first adapter executed in a software abstraction layer and a second adapter executed in a proxy virtual machine.

[0069] Clause 6. The method of clause 1, wherein the physical hardware system comprises an avionics system including a plurality of line replaceable units.

[0070] Clause 7. The method of clause 1, further comprising: modifying the physical hardware system based on the test to generate a modified physical hardware system; and deploying the modified physical hardware system.

[0071] Clause 8. The method of clause 1, wherein obtaining a proxy physical hardware system that matches the physical hardware system comprises obtaining a proxy physical hardware system having at least the same processor as a processor of the physical hardware system.

[0072] Clause 9. The method of clause 1, wherein constructing the proxy virtual machine from the proxy physical hardware system in the virtualization system comprises emulating at least a processor of the proxy physical hardware system.

[0073] Clause 10. The method of clause 1, wherein the step of obtaining a proxy physical hardware system that matches the physical hardware system is performed without access to a specification of the physical hardware system.

[0074] Clause 11. The method of clause 1, further comprising simulating at least one vehicle physical hardware system using a virtualization system to train users of the vehicle physical hardware system.

[0075] Clause 12. A system for testing a physical hardware system by executing hardware system application software on a corresponding simulated proxy physical hardware system in a proxy virtual machine, the system comprising: a proxy physical hardware system that matches aspects of the physical hardware system; and a virtualization system comprising a proxy virtual machine constructed from the proxy physical hardware system, wherein the proxy virtual machine simulates hardware components of the proxy physical hardware system and executes a hardware abstraction software layer that executes the hardware system application software in the proxy virtual machine using a memory mapping that reproduces the memory locations used by the proxy physical hardware system and using at least one adapter that maps data between the proxy virtual machine and the hardware system application software.

[0076] Clause 13. The system of clause 12, wherein the hardware abstraction software layer comprises an ARINC 653 operating system.

[0077] Clause 14. The system of Clause 12, wherein the at least one adapter is executed in a hardware abstraction software layer.

[0078] Clause 15. The system of Clause 12, wherein the at least one adapter is executed in a proxy virtual machine.

[0079] Clause 16. The system of Clause 12, wherein the at least one adapter comprises a first adapter executed in a software abstraction layer and a second adapter executed in a proxy virtual machine.

[0080] Clause 17. The system of clause 12, wherein the physical hardware system comprises an avionics system including a plurality of line replaceable units.

[0081] Clause 18. The system of Clause 12, further comprising a modified physical hardware system modified based on testing the physical hardware system using the virtualization system.

[0082] Clause 19. The system of clause 12, wherein the proxy physical hardware system has at least a processor that is the same as a processor of the physical hardware system.

[0083] Clause 20. The system of Clause 12, wherein the proxy virtual machine constructed from the proxy physical hardware system emulates at least a processor of the proxy physical hardware system.

[0084] Clause 21. A method for training a person to operate a physical hardware system by having the person operate the hardware system application software on an emulated proxy physical hardware system in a proxy virtual machine, the emulated proxy physical hardware system corresponding to the physical hardware system, the method comprising: obtaining a proxy physical hardware system that matches various aspects of the physical hardware system; constructing a proxy virtual machine from the proxy physical hardware system in a virtualization system; simulating hardware components of the proxy physical hardware system in the proxy virtual machine using the virtualization system; executing a hardware abstraction software layer in the proxy virtual machine; executing the hardware system application software in the proxy virtual machine on the proxy physical hardware system using the hardware abstraction software layer of the virtualization system using a memory mapping that reproduces the memory locations used by the proxy physical hardware system and using at least one adapter that maps data between the proxy virtual machine and the hardware system application software; and using the virtualization system to train a person to operate the physical hardware system by having the person operate the hardware system application software in the proxy virtual machine on the proxy physical hardware system.

[0085] Clause 22. The method of clause 21, wherein the physical hardware system comprises a vehicle physical hardware system.

[0086] Clause 23. The method of clause 22, wherein the vehicle comprises an aircraft, and wherein the virtualization system comprises a flight simulator.

[0087] The present disclosure is not limited to the specific embodiments described in this application, which are intended to be illustrative of various aspects. It will be apparent to those skilled in the art that many modifications and variations can be made without departing from its spirit and scope. In addition to those listed herein, methods and devices that are functionally equivalent within the scope of the present disclosure will be apparent to those skilled in the art from the above description. These modifications and variations are intended to fall within the scope of the appended claims. The present disclosure is limited only by the terms of the appended claims and the complete equivalent scope authorized to these claims. It will also be understood that the terms used herein are only for the purpose of describing specific embodiments and are not intended to be limiting.

[0088] With respect to the use of substantially any plural and / or singular terms herein, those skilled in the art may appropriately convert the plural to the singular and / or the singular to the plural, depending on the context and / or application. For the sake of clarity, various singular / plural permutations may be expressly set forth herein.

[0089] Those skilled in the art will understand that, in general, the terms used herein, particularly in the appended claims (e.g., the bodies of the appended claims), are generally intended to be "open" terms (e.g., the term "including" should be interpreted as "including but not limited to", the term "having" should be interpreted as "having at least", the term "comprising" should be interpreted as "including but not limited to", etc.). Those skilled in the art will further understand that if a specific number of an introduced claim recitation is intended, such intent will be explicitly stated in the claim, and in the absence of such a statement, such intent is not present. For example, to aid understanding, the following appended claims may contain the use of the introductory phrases "at least one" and "one or more" to introduce claim recitations. However, the use of these phrases should not be interpreted as implying that a claim recitation introduced by an indefinite article limits any particular claim containing such introduced claim recitation to embodiments containing only one such recitation, even when the same claim includes the introductory phrases "one or more" or "at least one" and an indefinite article (e.g., the indefinite article should be interpreted as meaning "at least one" or "one or more"); the same is true for the use of definite articles used to introduce claim recitations. In addition, even if a specific number of an introduced claim statement is explicitly stated, one skilled in the art will recognize that such a statement should be interpreted to mean at least the stated number (e.g., a bare statement of "two statements" without other modifiers means at least two statements or two or more statements). In addition, where phrases similar to "at least one of A, B, and C, etc." are used, generally, such construction is intended that one skilled in the art will understand the meaning of the phrase (e.g., "a system having at least one of A, B, and C" would include, but is not limited to, systems having only A, only B, only C, A and B, A and C, B and C, and / or A, B, and C, etc.). Where phrases similar to "at least one of A, B, or C, etc." are used, generally, such construction is intended that one skilled in the art will understand the meaning of the phrase (e.g., "a system having at least one of A, B, or C" would include, but is not limited to, systems having only A, only B, only C, A and B, A and C, B and C, and / or A, B, and C, etc.). Those skilled in the art will further understand that any transitional words and / or phrases that actually present two or more alternative terms, whether in the specification, claims or drawings, should be understood to contemplate the possibility of including one of the terms, any one of the terms, or both of the terms. For example, the phrase "A or B" will be understood to include the possibility of "A" or "B" or "A and B". In addition, where features or aspects of the disclosure are described in terms of Markush groups, those skilled in the art will recognize that the disclosure is also thereby described in terms of any individual member or subgroup of members of the Markush group.

[0090] While various aspects and embodiments are disclosed herein, other aspects and embodiments will be apparent to those skilled in the art. The various aspects and embodiments disclosed herein are for illustration and not intended to be limiting, with the true scope and spirit being indicated by the following claims.

Claims

1. A method for testing a physical hardware system (102) by executing hardware system application software (136) of the physical hardware system (102) on a corresponding simulated proxy physical hardware system (105) in a proxy virtual machine (130), the method comprising the following steps: Obtaining (701) a proxy physical hardware system (105) that matches aspects of the physical hardware system; constructing the proxy virtual machine from the proxy physical hardware system in a virtualization system (110); emulating hardware components of the proxy physical hardware system in the proxy virtual machine using the virtualization system; Executing a hardware abstraction software layer (132) in the proxy virtual machine; executing the hardware system application software in the proxy virtual machine using a memory map (601) by the hardware abstraction software layer of the virtualization system and using at least one adapter, the adapter accommodating differences in the physical hardware system compared to the proxy physical hardware system, wherein the adapter maps input / output data between the proxy virtual machine and the hardware system application software, the memory map (601) being configured to associate memory addresses of hardware components (603) of the proxy physical hardware system (105) with memory locations of the proxy virtual machine (130); and The physical hardware system is tested (719) using the virtualization system by executing the hardware system application software in the proxy virtual machine on the proxy physical hardware system.

2. The method according to claim 1, wherein: The hardware abstraction software layer includes an ARINC 653 operating system.

3. The method according to claim 1, wherein: The at least one adapter includes a first adapter (134) executed in the hardware abstraction software layer (132) and a second adapter (135) executed in the proxy virtual machine.

4. The method according to claim 1, wherein: The physical hardware system includes an avionics system including a plurality of line replaceable units.

5. The method according to claim 1, further comprising: modifying (723) the physical hardware system based on the test to generate a modified physical hardware system; as well as The modified physical hardware system is deployed (727).

6. The method according to claim 1, wherein: The step of obtaining the proxy physical hardware system that matches the physical hardware system includes obtaining a proxy physical hardware system (105) having at least a processor (425) that is the same as a processor (325) of the physical hardware system.

7. The method according to claim 1, wherein: The step of constructing the proxy virtual machine from the proxy physical hardware system in the virtualization system includes emulating (907) at least a processor (425) of the proxy physical hardware system.

8. The method according to claim 1 also includes using the virtualization system to simulate at least one vehicle physical hardware system to train users of the vehicle physical hardware system.

9. A system for testing a physical hardware system (102) by executing hardware system application software (136) of the physical hardware system (102) on a corresponding simulated proxy physical hardware system (105) in a proxy virtual machine (130), the system comprising: a proxy physical hardware system (105) that matches aspects of the physical hardware system; and A virtualization system (110) comprising a proxy virtual machine constructed from the proxy physical hardware system, wherein the proxy virtual machine emulates hardware components of the proxy physical hardware system and executes (707) a hardware abstraction software layer (132), the hardware abstraction software layer (132) using a memory map (601) and using at least one adapter to execute the hardware system application software in the proxy virtual machine, the adapter accommodating differences in the physical hardware system compared to the proxy physical hardware system, wherein the adapter maps data between the proxy virtual machine and the hardware system application software, the memory map (601) being configured to associate memory addresses of hardware components (603) of the proxy physical hardware system (105) with memory locations of the proxy virtual machine (130).

10. The system according to claim 9, wherein: The hardware abstraction software layer includes an ARINC 653 operating system.

11. The system according to claim 9, wherein: The at least one adapter includes a first adapter (134) executed in the hardware abstraction software layer (132) and a second adapter (135) executed in the proxy virtual machine.

12. The system according to claim 9, wherein: At least one of the following is true: The physical hardware system includes an avionics system including a plurality of line replaceable units; The proxy physical hardware system (105) has at least a processor (425) that is the same as the processor (325) of the physical hardware system; and The proxy virtual machine constructed from the proxy physical hardware system emulates (907) at least a processor (425) of the proxy physical hardware system.