Information processing device, procedure and program
The information processing apparatus facilitates stable communication between virtual machines using a shared memory and delivery management system, addressing the destabilization issues caused by adding virtual machines in production environments.
Patent Information
- Application Number
- DE112018007104
- Authority / Receiving Office
- DE · DE
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2018-03-20
- Publication Date
- 2024-11-14
- Estimated Expiration
- 2038-03-20
AI Technical Summary
Existing methods for modifying applications in a production environment, such as those used in factory automation, often require adding virtual machines, which can destabilize the operational state and potentially cause failures in the production environment.
An information processing apparatus with a root operating system and guest operating systems that utilize a shared memory and delivery management means to manage data transmission between virtual machines without changing settings, enabling communication between virtual machines on different devices.
Enables stable communication between virtual machines without altering settings, preventing operational disruptions and ensuring data integrity across different environments.
Smart Images

Figure 00000000_0000_ABST
Abstract
Description
Technical area
[0001] The present disclosure relates to an information processing device, a method and a program. background
[0002] Applications can be run in conjunction with each other on a virtual machine, which is set up as a virtual environment on an information processing device. In the field of factory automation, for example, a control application for controlling a drive unit, an inspection device, and the like is run on the virtual machine running a real-time operating system. Meanwhile, an information processing application for processing inspection data output by the inspection device is run on a separate virtual machine running a non-real-time operating system.
[0003] Modifications may be made to a particular application due to a change in specifications, a malfunction, or similar reasons. In this case, the modified application is typically run in a test environment, separate from the production environment, for operational verification. Although dummy data can be used for testing in the test environment, there may be instances where verification is preferably performed using data collected in the production environment. Examples of such cases include modifying an application to correct a malfunction that only occurs in the production environment.
[0004] Patent literature 1 describes the setup of a production environment and a test environment within the same information processing device and the sharing of file resources between the production and test environments. With such a configuration, verification can be achieved in the test environment using data collected in the production environment.
[0005] To set up the test environment in a production information processing device according to patent literature 1, one or more virtual machines must be added to the information processing device, which contains a virtual environment. However, adding a virtual machine can cause the existing virtual machine to operate unstably, which can negatively affect the operating state in the production environment. In the field of factory automation, for example, the unstable operation of a virtual machine running an application to control a drive device, an inspection device, or the like can negatively impact the operating states of the drive device, the inspection device, and the like. In the worst case, a problem such as the failure of the drive device, the inspection device, or the like may occur. Citation list of patent literature
[0006] Patent literature 1: Unexamined published Japanese patent application no. H8-235011. Relevant prior art also includes US 2017 / 0168985A1 and US 9,553,764B2. Summary of the invention: Technical problem
[0007] The problem described above can be avoided by running an application, such as the application for controlling the drive unit, inspection device, and the like, on a virtual machine of a different information processing device during verification. However, in this case, the virtual machine running on the other information processing device must be able to communicate.
[0008] When a communication target is changed to the virtual machine of a different information processing device, settings for the virtual machine in the production environment and settings for the application running on the virtual machine of a different information processing device are required, which can negatively affect operations in the production environment.
[0009] In view of the above circumstances, one objective of the present disclosure is to enable communication between virtual machines of information processing devices without changing the settings on the virtual machine side. Solution to the problem
[0010] To achieve the above objective, an information processing device according to the present disclosure is an information processing device on which a virtual environment with virtual machines is built. The information processing device comprises a root operating system for running on the information processing device, guest operating systems for running on the respective virtual machines, a shared memory that the guest operating systems and the root operating system can access, and a transmission information storage means for specifying a relationship between (i) destination information, which indicates the destinations of data specified by the virtual machines, and source information, which indicates the sources of the data, and (ii) a transmission destination to which the data is actually to be transmitted.The root operating system includes a transmission management tool for managing the transmission of data output by the virtual machines and a communication tool for communicating with another information processing device via a communication channel. When the guest operating system of the first virtual machine writes initial data destined for a second virtual machine, along with the destination and source information, to the shared memory, the transmission management tool determines whether a transmission destination is specified in the transmission information storage tool, which is associated with the destination and source information.Upon determining that the transmission information storage medium specifies the other information processing device as the transmission destination, which is associated with the destination information and the source information, the transmission management device delivers the initial data to the communication device and transmits the initial data delivered by the transmission management device to the other information processing device. Upon determining that the transmission information storage medium does not specify a transmission destination associated with the destination information and the source information, the transmission management device transmits the initial data to the second virtual machine. Advantageous effects of the invention
[0011] If, in the information processing device according to the present disclosure, it is determined that another information processing device is specified in the transmission information storage means as the transmission destination, which is associated with the destination information and the source information for the initial data written to the common memory by the first virtual machine, the transmission management means delivers the initial data to the communication means, and the communication means transmits the initial data delivered by the transmission management means to the other information processing device. Such a configuration enables the virtual machines of the information processing devices to communicate with each other. Brief description of the drawings Fig. 1 is a drawing which shows an overview of a configuration of an information processing system according to an embodiment of the present disclosure; Fig. Figure 2 is a block diagram showing a hardware configuration of an information processing device according to the embodiment; Fig. Figure 3 is a functional block diagram of the information processing device according to the embodiment; Fig. 4 is a diagram showing a configuration of data according to the embodiment, which are stored in a common memory; Fig. Figure 5 is a drawing showing an example of data recorded in a transmission information table according to the embodiment; Fig. Figure 6 is a drawing showing an example of data recorded in a usage conditions table according to the embodiment; Fig. Figure 7 is a drawing showing another example of data recorded in the usage conditions table according to the embodiment; Fig. Figure 8 is a drawing showing a configuration of data that is sent and received between the information processing devices according to the embodiment; Fig. Figure 9 is a flowchart of a first transmission processing step according to the embodiment by a transmission manager of an information processing device acting as a sender; Fig. Figure 10 is a flowchart of a transmission processing operation according to the embodiment by the communicator of the information processing device acting as a sender; Fig. Figure 11 is a flowchart of a receiving process according to the embodiment by the communicator of an information processing device acting as a receiver; Fig. Figure 12 is a flowchart of a second transmission processing step according to the embodiment by the transmission manager of the information processing device acting as receiver; Fig. Figure 13 is a functional block diagram of an information processing device according to a modified example; Fig. Figure 14 is a drawing showing an example of data according to the modified example, which is recorded in a transmission information table; Fig. Figure 15 is a flowchart of a transmission processing operation according to the modified example by a transmission manager of the information processing device; Fig. Figure 16 is a drawing showing another example of data recorded in the transmission information table; Fig. Figure 17 is his drawing, which shows yet another example of data recorded in a usage conditions table; and Fig. Figure 18 is a drawing that shows yet another example of data recorded in the transmission information table. Description of embodiments / design forms
[0012] As in Fig. Figure 1 shows an information processing system 100 according to an embodiment of the present disclosure comprising an information processing device 11 and an information processing device 21, which can communicate with each other via a communication path 50. The information processing device 11 is a device that operates as a production environment of a factory automation control system (FA control system). The information processing device 21 is a device for a test environment of the FA control system.
[0013] In this case, information processing device 11 is installed in a factory, and information processing device 21 is installed at a location different from the factory. Therefore, information processing device 11 is connected to information processing device 21 via communication path 50. Communication path 50 is part of a local area network (LAN) (not shown).
[0014] A virtual environment is set up on each of the information processing devices 11 and 21. Virtual machines 12 and 13 run on information processing device 11. Virtual machines 22 and 23 run on information processing device 21. Fig. 1. The representation of a root operating system, which is installed on each of the information processing devices 11 and 21, was omitted.
[0015] Virtual machine 12 functions as a programmable logic controller (PLC). Virtual machine 12 is connected to drive units 91 and 92 and an inspection unit 93, which are located in the factory. Virtual machine 12 is an example of the first virtual machine of the present disclosure. A guest operating system (hereinafter referred to as the guest OS) 120 of virtual machine 12 executes a control application 130. The application 130 is firmware of the PLC. The application 130 performs processing related to the control of the drive units 91 and 92 and processing for collecting inspection data from the inspection unit 93. For example, the application 130 collects image data as inspection data, which is obtained by the inspection unit 93 capturing an image of a production part, and sends the image data to virtual machine 13.
[0016] Virtual machine 13 functions as a computer that performs information processing. Virtual machine 13 is an example of a second virtual machine in this disclosure. The guest operating system 140 of virtual machine 13 executes an application 150 for information processing, for example, a quality control application that analyzes local inspection data and provides feedback to a production line. The application 150 performs an analysis processing operation of analyzing the inspection data from the inspection device 93.For example, the application analyzes 150 image data obtained by the inspection device 93 and the application 130 of the virtual machine 12, generates data indicating an analysis-based quality status, for example by correcting the number of rejections in the total data received, and sends the generated data indicating a quality status to the virtual machine 12.
[0017] Virtual Machine 22 has a configuration similar to Virtual Machine 12 and functions as a programmable logic controller (PLC). Unlike Virtual Machine 12, Virtual Machine 22 does not control its information processing device. Virtual Machine 22 is connected to a Simulator 94. Simulator 94 is implemented by running a simulation program on a PC.
[0018] Virtual machine 23 has a configuration similar to that of virtual machine 13 and functions as a computer that performs information processing.
[0019] During operation of the production environment, virtual machines 12 and 13 of information processing device 11 cooperate with each other. During operational verification of the application, virtual machines 22 and 23 of information processing device 21 cooperate with each other for the test environment.
[0020] Because in the present embodiment the operational verification of the application is performed using data collected in the production environment, the virtual machine 12 of the information processing device 11 and the virtual machine 23 of the information processing device 21 can also cooperate with each other. The virtual machine 13 of the information processing device 11 and the virtual machine 22 of the information processing device 21 can also cooperate with each other. Therefore, each of the information processing devices 11 and 21 can forward data sent from one virtual machine to another virtual machine of the same information processing device to another information processing device specified by a user.In other words, data addressed to another virtual machine of the same information processing device can be transferred to another information processing device specified by a user.
[0021] As in Fig. As shown in Figure 2, the information processing device 11 comprises, as its hardware configuration, a processor 1, a main memory 2, a subsidiary memory 3, and a communication controller 4. The main memory 2, the subsidiary memory 3, and the communication controller 4 are all connected to and communicate with the processor 1 via an internal bus 9. The hardware configuration of the information processing device 21 is similar to the configuration of the information processing device 11.
[0022] Processor 1 comprises a central processing unit (CPU). Processor 1 executes various programs stored in subsidiary memory 3 to implement various functions of information processing device 11.
[0023] Main memory 2 comprises volatile memory and is used as the working memory of processor 1. Processor 1 loads a program, a parameter, and the like, which are stored in subsidiary memory 3, into main memory 2 and performs various types of processing using the program, the parameter, and the like that loaded into main memory 2.
[0024] Subsidiary memory 3 comprises non-volatile memory. Subsidiary memory 3 stores a program, a parameter, and the like. Subsidiary memory 3 stores a program 001 for implementing functions of a transmission manager 181, which will be described later, and a program 002 for implementing functions of the communicator 182. Subsidiary memory 3 further stores a program for creating virtual machines 12 and 13, a program for executing application 130 of virtual machine 12, a program for executing application 150 of virtual machine 13, and the like.
[0025] The communication controller 4 includes a network interface for communication via communication path 50. The communication controller 4 receives a signal transmitted via communication path 50 and outputs data to the processor 1 indicating the received signal. The communication controller 4 also transmits a signal via communication path 50 to the information processing device 21 indicating data supplied by the processor 1.
[0026] As in Fig. As shown in Figure 3, the information processing device 11 functionally comprises a hypervisor 110, which manages the virtual machines 12 and 13; a guest OS 120 and an application 130, which run on the virtual machine 12; a guest OS 140 and an application 150, which run on the virtual machine 13; a root operating system (hereinafter referred to as a root OS) 180, which is installed on and runs on the information processing device 11, which is a host machine; a transmission information table 161, in which a transmission destination is recorded, which is a destination for data sent and received between the virtual machines 12 and 13; and a usage condition table 162, in which information about the active or inactive state of information recorded in the transmission information table 161 is recorded.Transmission Information Table 161 is an example of a transmission information storage device of the present disclosure. Usage Conditions Table 162 is an example of an active / inactive setting conditions storage device of the present disclosure.
[0027] Hypervisor 110 creates virtual machines 12 and 13 according to the control of the root OS 180, which will be described later, and manages the created virtual machines 12 and 13. Hypervisor 110 is implemented by processor 1 by executing a dedicated program stored in subsidiary memory 3.
[0028] Hypervisor 110 comprises shared memory 111, which is allocated to virtual machine 12, shared memory 112, which is allocated to virtual machine 13, and a backend driver 113, which is a virtual device driver. Shared memory 111 is used for data exchange between guest OS 120 and root OS 180. Therefore, both guest OS 120 and root OS 180 can access shared memory 111. Writing data to shared memory 111 can be referred to hereafter as storing data. Shared memory 111 is implemented by subsidiary memory 3. Shared memory 112 is used for data exchange between guest OS 140 and root OS 180. Therefore, both guest OS 140 and root OS 180 can access shared memory 112. The shared memory 112 is implemented through the subsidiary memory 3.
[0029] In the present embodiment, data cannot be sent and received directly between guest OS 120 and guest OS 140. Therefore, root OS 180 performs data forwarding between guest OS 120 and guest OS 140 using shared memory locations 111 and 112. For example, when guest OS 120 sends data to guest OS 140, guest OS 120 first stores the data to be sent to guest OS 140 in shared memory location 111. Root OS 180 reads the data stored in shared memory location 111 by guest OS 120. Root OS 180 stores the read data in shared memory location 112. Guest OS 140 then reads the data stored in shared memory location 112 by root OS 180. In this way, data is forwarded from guest OS 120 to guest OS 140. The same applies to forwarding data from guest OS 140 to guest OS 120.
[0030] The backend driver 113 reads data and writes data to the shared memory locations 111 and 112 according to the control of the root OS 180.
[0031] Guest OS 120 is an operating system that runs on virtual machine 12. In the present embodiment, a real-time operating system (RTOS) is used for Guest OS 120. At the instruction of Root OS 180, Guest OS 120 starts application 130. Guest OS 120 exchanges data with Root OS 180 using shared memory 111. Guest OS 120 is implemented by processor 1 by executing a program stored in subsidiary memory 3.
[0032] The guest OS 120 has a frontend driver 121, which is a virtual device driver. The frontend driver 121 reads data and writes data to the shared memory 111 under the control of the guest OS 120.
[0033] The guest OS 120 controls the frontend driver 121 to write output data from the application 130 to the shared memory 111.
[0034] Fig. Figure 4 shows an example of a data format that the guest OS 120 stores in shared memory 111. The data stored in shared memory 111 includes a header 1010, a data part 1020, and an error detection code 1030.
[0035] Header 1010 comprises a target identification (target ID), which is identification information for a virtual machine designated as a target; a source ID 1012, which is identification information for a virtual machine designated as a source; a type 1013, which is information that specifies identification information for an application that outputs data; and a size 1014, which is information that specifies the size of a data part 1020. The target ID 1011 is an example of the target information from this disclosure, the source ID 1012 is an example of the source information from this disclosure, and the type 1013 is an example of the identification information from this disclosure.
[0036] For example, if virtual machine 12 sends output data from application 130 to virtual machine 13, each part of header 1010 is set to a value as specified below. An ID identifying virtual machine 13 is set as destination ID 1011, an ID identifying virtual machine 12 is set as source ID 1012, and identification information for application 130 is set as a value of type 1013.
[0037] Data part 1020 comprises output data from application 130. For example, data part 1020 includes inspection data collected by application 130 from inspection device 93. Fault detection code 1030 is a code used for fault detection. Fault detection schemes such as cyclic redundancy checking (CRC), parity, Hamming, or similar can be used.
[0038] The guest OS 120 also controls the frontend driver 121 to read data stored in shared memory 111 by the root OS 180. The format of data stored in shared memory 111 by the root OS 180 is defined in Fig. The example shown is similar to the one in 4.
[0039] The in Fig. The guest OS 120 shown in Figure 3 further controls the frontend driver 121 to establish bus communication with the root OS 180 via the virtual bus. Specifically, the guest OS 120 controls the frontend driver 121 to send a data storage message signal to the root OS 180, indicating that the data has been written to the shared memory 111. Upon receiving this signal, the root OS 180 reads the data from the shared memory 111.
[0040] When the root OS 180 stores data in the shared memory 111, it sends a data storage notification signal to the frontend driver 121. Upon receiving this signal, the guest OS 120 instructs the frontend driver 121 to read the data from the shared memory 111.
[0041] Application 130 performs processing related to the control of drive units 91 and 92 and processing to collect inspection data from inspection device 93. Application 130 collects the inspection data from inspection device 93 and sends it to virtual machine 13. Application 130 is started by guest operating system 120, which executes the program stored in subsidiary memory 3.
[0042] Guest OS 140 is an operating system that runs on virtual machine 13. In the present embodiment, a non-real-time operating system is used for Guest OS 140. Guest OS 140 starts application 150 upon instruction from root OS 180. Guest OS 140 also exchanges data with root OS 180 using shared memory 112. Guest OS 140 is implemented by processor 1, which executes a program stored in subsidiary memory 3.
[0043] The guest OS 140 has the frontend driver 141, which is a virtual device driver. The frontend driver 141 reads and writes data to the shared memory 112 under the control of the guest OS 140. The guest OS 140 controls the frontend driver 141 to write output data from the application 150 to the shared memory 112. The format of the data stored in the shared memory 112 by the guest OS 140 is the same as that of the data in the application 150. Fig. 4. Example shown. Here, data part 1020 is configured to display the data output by application 150. The guest OS 140 also controls the frontend driver 141 to read the data stored by the root OS 180 in shared memory 112. The format of the data stored by the root OS 180 in shared memory 112 is similar to that shown in Fig. 4 examples shown.
[0044] The in Fig. The guest OS 140 shown in Figure 3 further controls the frontend driver 141 to establish bus communication with the root OS 180 via the virtual bus. After data is stored in the shared memory 112, the guest OS 140 controls the frontend driver 141 to send the data storage message signal to the root OS 180. Upon receiving this signal, the root OS 180 uses the backend driver 113 to read the data from the shared memory 112.
[0045] When the root OS 180 stores the data in the shared memory 112, the root OS 180 sends the data storage notification signal to the frontend driver 141. When the frontend driver 141 receives this signal, the guest OS 140 controls the frontend driver 141 to read the data from the shared memory 112.
[0046] Application 150 performs an analysis of inspection data from inspection device 93. For example, application 150 analyzes the inspection data received by application 130 of virtual machine 12, generates data indicating a quality status based on the analysis, and sends this data to virtual machine 12. Application 150 is started by guest OS 140, which executes the program stored in subsidiary memory 3.
[0047] Guest OS 120 and Guest OS 140 each set an ID in the target ID 1011 of header 1010, which specifies the virtual machine designated as the target. Exactly one of the virtual machines 12 and 13 of the same information processing device 11 is specified as the target. However, as described above, if the user specifies the transfer to a different information processing device, the root OS 180 transfers the data stored by virtual machines 12 and 13 in shared memory locations 111 and 112 to the target specified by the user. Based on the user's specification, the root OS 180 also overwrites the information in header 1010 of the data stored by virtual machines 12 and 13 in shared memory locations 111 and 112. The transmission information table 161 and the usage conditions table 162 are used for the aforementioned processing by the root OS 180.
[0048] The transmission destinations, which are the targets for data transmission by virtual machines 12 and 13, are pre-recorded in the transmission information table 161. Recording in the transmission information table 161 is performed as follows: First, a user generates data to be recorded in the transmission information table 161 using a recording tool (not shown). The user connects the recording tool to the information processing device 11 via a communication cable, uploads the generated data to the information processing device 11, and records the data in the transmission information table 161. In this case, the recording tool is a dedicated program installed on the PC.
[0049] The transmission information table 161 contains information from header 1010, which is stored in shared memory locations 111 and 112 by guest OS 120 and guest OS 140, and information indicating the connection to the data's destination. Specifically, transmission information table 161 includes the destination of data, which is specified by the destination ID 1011, which identifies the virtual machine designated as the destination; the source ID 1012, which identifies the virtual machine designated as the source; and the type 1013, which is the identification information of the application sending the data. A value for header 1010 that must be updated during transmission is specified in transmission information table 161.
[0050] Fig. Figure 5 shows an example of data recorded in the transmission information table 161. In the following description, the ID for identifying virtual machine 12 is "VM12", the ID for identifying virtual machine 13 is "VM13", the ID for identifying virtual machine 22 is "VM22", and the ID for identifying virtual machine 23 is "VM23". The values set in type 1013 can include an identification information "Anw1" for a numerical computation application, an identification information "Anw2" for a control application, and an identification information "Anw3" for an image processing application.
[0051] As in Fig. As shown in Figure 5, in transmission setting No. 1, the transmission destination is specified as "Information Processing Device 21" when the destination ID is 1011 "VM13", the source ID is 1012 "VM12", and the type is 1013 "Anw1". Although in this example the values, such as "Information Processing Device 21", are recorded as information to identify the information processing devices, Internet Protocol (IP) addresses of the information processing devices can be specified as the transmission destinations.
[0052] In transmission setting No. 1, an update header includes Destination ID 1011 "VM23", Source ID 1012 "VM22", and Type 1013 "Anw1". This indicates that header 1010 is specified to update Destination ID 1011 to "VM23", Source ID 1012 to "VM22", and Type 1013 to "Anw1".
[0053] As an example, assume that the guest OS 120 of the virtual machine 12 stores the data output by the application for numerical calculations in the shared memory 111 in a Fig. The format shown in Figure 4 stores data intended for virtual machine 13. In this case, the data header 1010 is set such that the destination ID 1011 is "VM13", the source ID 1012 is "VM12", and the type 1013 is "Anw1". As shown in Figure 4, the data is stored in the format shown in Figure 4, which is intended for virtual machine 13. In this case, the header 1010 of the data is set such that the destination ID 1011 is "VM13", the source ID 1012 is "VM12", and the type 1013 is "Anw1". Fig. As shown in Figure 5, the transmission setting number corresponding to the information set in header 1010 is 1. Transmission setting number 1 specifies "Information Processing Device 21" as the transmission destination. Therefore, the data is transmitted from the transmission manager 181 and the communicator 182, described below, to Information Processing Device 21.
[0054] Furthermore, the header 1010 is updated by the transmission manager 181 according to transmission setting no. 1 such that the destination ID 1011 is "VM23", the source ID 1012 is "VM22", and the type 1013 is "Anw1". Therefore, the virtual machine 23 of the information processing device 21, which received the data, considers the received data to be the data output by the numerical computation application of the virtual machine 22 of the same information processing device 21.
[0055] As in Fig. As shown in Figure 5, in transmission setting No. 2, the transmission destination is specified as "Information Processing Device 21" when the destination ID is 1011 "VM13", the source ID is 1012 "VM12", and the type is 1013 "Anw2". Furthermore, in transmission setting No. 2, header 1010 is specified to be updated so that the destination ID becomes 1011 "VM23", the source ID becomes 1012 "VM22", and the type becomes 1013 "Anw3".
[0056] If the in Fig. 3. Virtual machine 12, shown in the shared memory 111, stores the application's output data for control as data intended for virtual machine 13. The data is transmitted according to transmission setting No. 2, shown in the following. Fig. 5, is transmitted to the information processing device 21. During transmission, each value of header 1010 is updated with the update header of transmission setting no. 2. The data received by the information processing device 21 therefore has "VM23" as destination ID 1011, "VM22" as source ID 1012, and "Anw3" as type 1013. The virtual machine 23 of the information processing device 21 therefore considers the received data to be the data output by the image processing application of the virtual machine 22 of the same information processing device 21.
[0057] With transmission setting No. 3, no information is recorded for the update header if the destination ID is 1011 "VM12", the source ID is 1012 "VM13", and the type is 1013 "Anw2". This means that the data is not transmitted anywhere.
[0058] If the in Fig. 3. The virtual machine 13 shown stores the application's output data for control in the shared memory 112 as the data intended for the virtual machine 12, according to the [document / section]. Fig. With transmission setting no. 3 shown in step 5, the data is not transmitted anywhere. This means that communication between virtual machine 13 and virtual machine 12 is cut off.
[0059] In transmission setting No. 4, a "local host," i.e., the user's own information processing device 11, is specified as the transmission destination when the destination ID is 1011 "VM13," the source ID is 1012 "VM12," and the type is 1013 "Anw3." In transmission setting No. 4, header 1010 is specified to be updated so that the destination ID is 1011 "VM13," the source ID is 1012 "VM12," and the type is 1013 "Anw1."
[0060] If the in Fig. 3. Virtual machine 12 shown stores the output data of the image processing application in the shared memory 111 as the data intended for virtual machine 13. The data is stored according to the... Fig. The data is transmitted to virtual machine 13 of the same information processing device 11 using transmission setting no. 4 shown in Figure 5. During transmission, each value of header 1010 is updated with the update header of transmission setting no. 4. Therefore, the data received by virtual machine 13 has the type 1013 "Anw3". Virtual machine 1013 thus considers the received data to be the data output by the application for numerical computation.
[0061] Information indicating whether the respective transmission setting in transmission information table 161 is active or inactive is pre-recorded in usage conditions table 162. Similar to the data in transmission information table 161, the data in usage conditions table 162 is generated by the user using the recording tool and uploaded to information processing device 11, thus recording the data in usage conditions table 162.
[0062] In the present embodiment, each transmission setting of the transmission information table 162 is active or inactive when a condition defined in the usage condition table 162 is met.
[0063] Fig. Figure 6 shows an example of data recorded in the usage conditions table 162. Here, the determination of activity or inactivity is specified based on a relationship between a threshold and a value stored at a memory address specified in the subsidiary memory 3 of the information processing device 11. In the example shown, transmission setting No. 1 is active when the value at the specified memory address is equal to the threshold; transmission setting No. 2 is active when the value at the specified memory address is less than the threshold; and transmission setting No. 3 is inactive when the value at the specified memory address is greater than the threshold.
[0064] Fig. Figure 7 shows another example of data recorded in the usage conditions table 162. Here, the activity or inactivity of the transmission setting is specified for a specified duration. In the example shown, transmission setting No. 4 is active for a period from a specified start date and time to a specified end date and time.
[0065] As in Fig. As shown in Figure 3, the root OS 180 is installed on the information processing device 11, and after the information processing device 11 is switched on, the root OS 180 is started first. The root OS 180 causes the hypervisor 110 to create and manage the virtual machines 12 and 13. The root OS 180 is implemented by processor 1, which executes a program stored in subsidiary memory 3.
[0066] The root OS 180 comprises the transmission manager 181 and the communicator 182. The transmission manager 181 is implemented by the root OS 180, which executes program 001 of subsidiary memory 3. The communicator 182 is implemented by the root OS 180, which executes program 002 of subsidiary memory 3. The transmission manager 181 is an example of the transmission management device of this disclosure. The communicator 182 is an example of a communication device of this disclosure.
[0067] The transfer controller 181 carries out processing relating to the transfer of data whose source is virtual machine 12 or 13 and where virtual machine 12 or 13 is specified as the destination.
[0068] First, the processing performed by the transfer manager 181 when virtual machines 12 and 13 store data in the shared storage 111 and 112 is described. Based on the aforementioned transfer information table 161 and the aforementioned usage conditions table 162, the transfer manager 181 transfers all data stored in the shared storage 111 and 112 to a transfer destination or to a destination specified by each of the respective virtual machines 12 and 13.
[0069] For example, if virtual machine 12, after receiving the data storage notification signal, determines that it will store the data in shared memory 111, the transmission manager 181 controls the backend driver 113 to read the data from shared memory 111. Based on the destination ID 1011, the source ID 1012, and the type 1013 of the read data, the transmission manager 181 determines whether the transmission destination is recorded in the transmission information table 161.
[0070] If the information processing device 21, which is another information processing device, is specified as the transmission destination in the transmission information table 161 for the data read from the shared memory 111, the transmission manager 181 updates the header 1010 to send the data to the communicator 182 along with information indicating the information processing device 21 as the transmission destination. If no transmission setting is recorded in the transmission information table 161 for the data read from the shared memory 111, the transmission manager 181 does not update the header 1010 and controls the backend driver 113 to write the data to the shared memory 112 of the virtual machine 13.If the information processing device 11 underlying the virtual machine 13 is specified as the transmission destination in the transmission information table 161 for the data read from the shared memory 111, the transmission manager 181 updates the header 1010 and controls the backend driver 113 to write the data to the shared memory 112 of the virtual machine 13.
[0071] The above processing is carried out by the transmission manager 181 when the virtual machines 12 and 13 place the data into the shared storage 111 and 112.
[0072] Next, the processing carried out by the transmission manager 181 when the communicator 182 receives a communication packet from the information processing device 21 is described.
[0073] After the communicator 182 receives data, which is the communication packet without a communication header 1040, the transmission manager 181 forwards the data to virtual machine 12 or 13 based on the destination ID of the data header 1010. For example, if the destination ID 1011 specifies virtual machine 13, the transmission manager 181 controls the backend driver 113 to write the data to shared memory 112 and sends a data storage message signal to the frontend driver 141. The transmission manager 181 performs similar processing if the destination ID 1011 specifies virtual machine 12. In this way, the data sent by the information processing device 21, which is another information processing device, is forwarded to virtual machine 12 or 13.
[0074] The communicator 182 performs the reception and transmission of communication packets via the communication path 50 to the information processing device 21.
[0075] First, the processing by the communicator 182 is described when the communicator 182 receives data from the transmission manager 181, which is intended for the information processing device 21. After receiving the data intended for the in Fig. 4. Information processing device 21 shown. From the specific data and the information of the transmission destination from the transmission manager 181, the communicator 182 generates the communication header 1040, which contains information about the transmission destination. For example, the communicator 182 generates an IP header as the communication header 1040 according to a protocol of a LAN, which is contained in the communication path 50. As in Fig. As shown in Figure 8, communicator 182 generates communication packet 1100, adding communication header 1040 to the data received by transmission manager 181 and intended for information processing device 21. Communicator 182 sends the generated communication packet 1100 to information processing device 21 via communication path 50.
[0076] Next, the processing by communicator 182 is described when communicator 182 receives the communication packet from information processing device 21. After receiving communication packet 1100 from information processing device 21, communicator 182 sends data to transmission manager 181, which is communication packet 1100 without the communication header 1040.
[0077] Although the configuration of each part of the information processing device 11 is described above, the information processing device 21 has a similar configuration.
[0078] Next, a process flow of several steps is described when the virtual machines 12 and 13 of the information processing device 11 act as senders. Data that the virtual machines 12 and 13 store in the shared memories 111 and 112 may subsequently be referred to as shared memory data. The shared memory data is an example of first data in this disclosure.
[0079] First, an initial transmission processing operation of the transmission manager 181 is described, which receives a data storage message signal concerning the data of the shared storage from one of the virtual machines 12 and 13.
[0080] As in Fig. As shown in Figure 9, the transmission manager 181 determines at a predetermined frequency whether it has received a data dump message signal (step S101). Upon determining that the transmission manager 181 has received the data dump message signal (yes in step S101), it controls the backend driver 113 to read the shared memory data from a shared memory allocated to the virtual machine 12 or 13 to which the data dump message signal is being sent (step S102). The read data is stored in a specific area of subsidiary memory 3. For example, after receiving the data dump message signal from virtual machine 12, the transmission manager 181 reads the shared memory data from shared memory 111.The transmission administrator 181 carries out the following processing of the data which are stored in the specified area of subsidiary storage 3 as follows.
[0081] Based on the destination ID 1011, the source ID 1012, and the type 1013 of the header 1010 of the data read from shared memory, the transmission manager 181 determines whether the transmission destination is set in the transmission information table 161 (step S103). For example, if the data read from shared memory 111 matches transmission setting number 1 of the transmission information table 161—that is, if the destination ID 1011 is "VM13," which specifies virtual machine 13, the source ID 1012 is "VM12," which specifies virtual machine 12, and the type 1013 is "Anw1"—then the transmission manager 181 determines that the transmission destination is specified (Yes in step S103).
[0082] Referring to the usage condition table 162, the transmission manager 181 determines whether the transmission setting is active (step S104). For example, if it is determined that a value at the specified memory address "0x100000" is equal to a threshold of "100" for transmission setting No. 1, the transmission manager 181 determines that the transmission setting is active (Yes in step S104).
[0083] The transmission manager 181 updates a value in header 1010 of the shared storage data read from shared storage 111 (step S105). The value of header 1010 is specified as an update header in transmission information table 161. For example, with transmission setting #1, transmission manager 181 updates header 1010 so that destination ID 1011 becomes "VM23", source ID 1012 becomes "VM22", and type 1013 becomes "Anw1".
[0084] The transmission manager 181 provides to the communicator 182 the information which specifies the information processing device which specifies the transmission destination in the transmission information table 161, and the data of the shared memory with the value with the updated value of the header 1010 (step S106).
[0085] In contrast, if the transmission manager 181 determines in step S103 that no transmission destination is specified (No in step S103), the transmission manager 181 controls the backend driver 113 to write the shared memory data to the shared memory of the virtual machine specified as destination ID 1011 in the shared memory read data (step S107). The transmission manager 181 then sends a data drop message signal to the frontend driver of the virtual machine specified as destination ID 1011 (step S108). For example, if the destination ID 1011 of the shared memory data read from shared memory 111 is "VM13", which identifies virtual machine 13, the transmission manager 181 writes the shared memory data to the shared memory 112 of virtual machine 13.The transmission manager 181 then sends a data storage message signal to the frontend driver 141 of the virtual machine 13.
[0086] After determining in step S104 that the transmission setting is not active (No in step S104), the transmission manager 181 executes the processing of the aforementioned steps S107 and S108. The above processing is performed when the transmission manager 181 receives the data storage notification signal from one of the virtual machines 12 and 13.
[0087] Next, the transmission processing of communicator 182 is described, to which the data of the shared memory and the information about the information processing device, which is the transmission destination, are transferred by the transmission manager 181 in step S106 of the Fig. 9 will be delivered.
[0088] As in Fig. As shown in Figure 10, communicator 182 determines whether it receives from transmission manager 181 the information specifying the information processing device as the transmission destination and the shared memory data to be sent (step S201). If communicator 182 receives the information specifying the information processing device as the transmission destination and the shared memory data to be sent (Yes in step S201), communicator 182 generates the communication header 1040, which contains the information specifying the information processing device as the transmission destination (step S202).
[0089] Communicator 182 generates the communication packet (step S203) by adding the communication header 1040, generated in step S202, to the shared memory data to be sent, which is received by the transmission manager 181 in step S201. Communicator 182 then transmits the communication packet via communication path 50 (step S204). This is the transmission processing of communicator 182.
[0090] Although the above description uses information processing device 11 as an example, the same applies to the case in which the virtual machines 22 and 23 of information processing device 21 act as senders.
[0091] Next, a process flow of a series of steps is described when the virtual machines 12 and 13 of the information processing device operate as receivers.
[0092] First, the receiving processing of the communicator 182 is described when the communication packet, which contains the data of the shared memory, is transmitted by the information processing device 21.
[0093] As in Fig. As shown in Figure 11, communicator 182 determines at a predetermined frequency whether it is receiving the communication packet via communication path 50 (step S301). Upon determining that the communication packet has been received (Yes in step S301), communicator 182 retrieves the data for the shared memory from the received packet (step S302). In particular, the Fig. The communication headers shown in section 8 are 1040 removed from the communication packet. As shown in Fig. As shown in Figure 11, communicator 182 delivers the shared memory data to transmission manager 181 (step S303). This is the communication processing of communicator 182.
[0094] Next, a second transmission processing step of the transmission manager 181 is described, to which the data of the shared storage is transferred from the communicator 182 in step S303 of the Fig. 11 have been delivered.
[0095] As in Fig. As shown in Figure 12, the transmission manager 181 determines at a predetermined frequency whether the shared memory data has been delivered by the communicator 182 (step S401). After the shared memory data has been delivered (Yes in step S401), the following processing is performed. The transmission manager 181 controls the backend driver 213 to store the shared memory data in the shared memory of the virtual machine specified by the destination ID 1011 of the received shared memory data (step S402). The transmission manager 181 provides a data storage notification signal to the frontend driver of the virtual machine specified by the destination ID 1011, indicating that the data has been stored (step S403). This is the second transmission processing step performed by the transmission manager 181 upon receiving the shared memory data.
[0096] Although the above description is given using the information processing device 11 as an example, the same applies to the case in which the virtual machines 22 and 23 of the information processing device 21 operate as receivers.
[0097] As described above, in the information processing device 11 according to the embodiment of the present disclosure, the sending and receiving of data between the virtual machines 12 and 13 is carried out via the root OS 180. If it is specified that the data between the virtual machines 12 and 13 is transferred to the information processing device 21, the data is transferred to the information processing device 21. In this way, the virtual machines of the information processing devices can communicate with each other.
[0098] Although the above description states that the data to be sent and received between virtual machines 12 and 13 of information processing device 11 is transferred to another information processing device 21, data can actually be transferred between virtual machines within information processing device 11. This is described in the following modified example. Modified example
[0099] As in Fig. As shown in Figure 13, an information processing device 11, according to a modified example, has a virtual machine 14 in addition to the virtual machines 12 and 13. Although a representation of the configuration of the information processing device 21 in Fig. If 13 is omitted, the configuration of the information processing device 21 is similar to that of the embodiment.
[0100] Virtual machine 14 functions as a computer that performs information processing similar to that of virtual machine 13. Virtual machine 14 is an example of the third virtual machine of the present disclosure. The guest OS 170 of virtual machine 14 executes an application 190 for information processing, similar to the guest OS 140 of virtual machine 13. Because virtual machine 14 has a similar configuration to virtual machine 13, a description of the hardware and functions of virtual machine 14 is omitted here.
[0101] The modified example is described under the assumption that the data to be sent and received between virtual machines 12 and 13 within the information processing device 11 is transferred to virtual machine 14 of the same information processing device 11. For this case, in Fig. Figure 14 shows an example of data recorded in the transmission information table 161. This includes an ID for identifying virtual machine 14, "VM14". The ID for identifying another virtual machine and the value of type 1013 are similar to those of the embodiment. The description of the content of transmission settings Nos. 1 to 4 is omitted, as this content is similar to that of the embodiment.
[0102] As in Fig. As shown in Figure 14, with transmission setting No. 5, the transmission destination is specified as the "local host" when the destination ID is 1011 "VM13", the source ID is 1012 "VM12", and the type is 1013 "Anw1". Furthermore, each value of header 1010 is specified to be updated so that the destination ID becomes 1011 "VM14", the source ID becomes 1012 "VM12", and the type becomes 1013 "Anw1".
[0103] This section describes how data is transferred based on transmission setting No. 5. It is assumed that transmission setting No. 5 is active. It is further assumed that virtual machine 12 has stored the application's output data for numerical computation, intended for virtual machine 13, in shared memory 111, and that the data storage message has been sent to root OS 180. In this case, in shared memory 111, the destination ID 1011 is set to "VM13", the source ID 1012 is set to "VM12", and the type 1013 is set to "Anw1".
[0104] The following refers to Fig. 14 describes an initial delay management processing according to a modified example of the transmission manager 181. The description focuses on a configuration that differs from that of the embodiment.
[0105] After determining that the transmission manager 181 is receiving a data storage message signal from the virtual machine 12 (Yes in step S101), the transmission manager 181 controls the backend driver 113 to read the data from the shared memory 111 allocated to the virtual machine 12 (step S102) and stores the read data in a specific area of the subsidiary memory 3.
[0106] Based on the destination ID 1011, the source ID 1012, and the type 1013 of the header 1010 read from the shared memory, the transmission manager 181 determines whether the transmission destination is set in the transmission information table 161. Because in this case the Fig. The 14 values shown, with target ID 1011, source ID 1012 and type 1013, are those in Fig. If the transmission setting shown in step 15 is the same, the transmission manager 181 determines that the transmission destination is specified (Yes in step S103).
[0107] The transmission manager 181 determines, with reference to the usage conditions table 162, whether the transmission setting is active or not (step S104), the transmission manager 181 determines that the transmission setting No. 5 is active (Yes in step S104).
[0108] The transmission manager 181 updates the values of header 1010 of the data read from shared memory 111 with the values specified as the update header in transmission information table 161 (step S105). As in Fig. As shown in Figure 14, the transmission manager 181 updates the header 1010 for transmission setting No. 5 so that the destination ID becomes 1011 “VM14”, the source ID becomes 1012 “VM12”, and the type becomes 1013 “Anw1”.
[0109] As in Fig. As shown in Figure 15, the transmission manager 181 determines whether the transmission destination of the transmission information table 161 is a different information processing device, i.e., a device different from the information processing device 11 (step S109). As shown in Fig. 14 shown, because for transmission setting No. 5 the transmission destination is the “local host”, as shown in Fig. As shown in 15, the transmission administrator 181 determines that the transmission destination is not another information processing device 21 (No in step S109).
[0110] The transfer manager 181 controls the backend driver 113 to write the shared memory data to the shared memory of the target virtual machine, as specified by the transfer setting (step S110). In this case, the transfer manager 181 writes the shared memory data to shared memory 114, which is assigned to virtual machine 14. The transfer manager 181 then sends a data storage message signal to the frontend driver 171 of virtual machine 14 (step S111).
[0111] As in Fig. As shown in 15, in contrast, in step S106, upon confirmation that the transmission destination is a different information processing device (Yes in step S109), the transmission manager 181 provides the communicator 182 with the information from the transmission information table 161 specifying the information processing device designated as the destination and the data of the shared memory with the updated values of the header 1010 (step S112).
[0112] In step S103, the processing performed when the transmission manager 181 determines that no transmission destination is specified in the transmission information table 161 (No in step S103) is similar to that of the embodiment. In step S104, the processing performed when it is determined that the transmission setting is not active (No in step S104) is similar to that of the embodiment.
[0113] As described in the embodiment and the modified example, if the data to be sent and received between the virtual machines is specified to be transmitted to another information processing device in the transmission information table 161, the information processing device according to the present disclosure does not send the data to the virtual machine for which it is intended, but to the specified other information processing device. Such a configuration enables communication between the virtual machines of information processing devices without requiring any changes to the settings on the virtual machine side.
[0114] If, in the modified example, a virtual machine is specified in the transmission information table 161 that is different from the target ID 1011 written to the shared memory by the virtual machine, the transmission manager 181 transmits the data to the shared memory allocated to the specified virtual machine. In this way, data can also be transferred to the virtual machine on the same information processing device.
[0115] The data transmission destination is specified in transmission information table 261 based on the destination ID 1011, the source ID 1012, and the type 1013. Therefore, communication between virtual machines on information processing devices is active for a given application. Even when communicating between virtual machines on the same information processing device, data can be sent and received in a similar manner under certain applications.
[0116] Because the usage condition table 262 allows setting whether the transmission setting of each entry in the transmission information table 261 is active or inactive, for example when testing the sending and receiving of data between applications, irrelevant communication with an application that is different from a target application can be eliminated.
[0117] The guest operating system of the virtual machine sends a write-to-share signal to the root operating system, indicating that the data has been written to the shared memory. It is sufficient for the root operating system to be able to read the shared memory data when a write-to-share signal is received; monitoring the shared memory allocated to the respective virtual machine is not required. Furthermore, the root operating system can identify the virtual machine that wrote to the shared memory without relying on information from header 1010.
[0118] The transmission manager 181 sends the data write signal to the designated guest operating system, indicating that the data has been written to the shared memory. It is sufficient for the guest operating system to retrieve data from the shared memory when the data write signal is received; monitoring of the shared memory is not required.
[0119] When multiple virtual machines are run on a single information processing device, they may experience resource shortages because they physically consume the hardware resources of that device. However, because this implementation allows communication between virtual machines on two or more information processing devices, this hardware resource shortage can be prevented.
[0120] In the aforementioned example, the activity or inactivity of the transmission setting is determined using usage condition tables 162 and 262. However, information processing devices 11 and 21 do not require usage condition tables 162 and 262. In this case, all transmission settings recorded in transmission information tables 161 and 261 can be set to active, and if setting the transmission setting to inactive is desired, the transmission setting can be deleted from transmission information tables 161 and 261. In this case, it is sufficient for each of the information processing devices 11 and 21 to have only a single table of usage condition tables 162 and 262, and therefore the maintenance of the tables is simple.
[0121] As in Fig. As shown in Figure 16, an alternative usage condition field can be added to the transmission information tables 161 and 261. Because it is sufficient for the information processing devices 11 and 21 to have only one table of usage conditions tables 162 and 262, maintenance of the tables is simple in this case.
[0122] Alternatively, usage condition tables 162 and 262 can have only one field to specify active / inactive. In the Fig. In example 17, being active or inactive is simply specified without conditions.
[0123] As in Fig. As shown in Figure 18, the activity or inactivity of the transmission information can alternatively be specified by adding a field to transmission information tables 161 and 261 that specifies active / inactive and changing its value. In the Fig.In example 18, being active or inactive is simply specified without conditions.
[0124] Although in the embodiment and the modified example each virtual machine is allocated (exactly) one shared memory, all virtual machines can write data to be sent to another virtual machine into the same shared memory. In this case, the root OS 180 can also determine, based on the source ID 1012 of the header 1010 written to the shared memory, which virtual machine wrote the data.
[0125] The number of virtual machines built on a single information processing device is not limited to two or three, but can be more than three. Alternatively, the number of virtual machines built on a single information processing device can be one. For example, a virtual machine 23 can be built alone on information processing device 21. In this case, a simulator 94 can also be connected to virtual machine 22. For example, when an operation of application 150 of virtual machine 13 is being tested, virtual machine 13 of information processing device 11 communicates with virtual machine 23 of information processing device 21, thus preventing operating conditions between inspection device 93 and drive devices 91 and 92 from interfering with each other.Furthermore, the information processing device 21 can have specifications according to which a single virtual machine 23 can be built. The information processing device 21 therefore does not need to have specifications identical to those of the information processing device 11. Therefore, a reduction in costs can be achieved.
[0126] In the example above, communication path 50 is part of a LAN; therefore, information processing devices 11 and 21 communicate with each other using the LAN. However, communication path 50 is not limited to this configuration. For example, communication path 50 can use a communication cable based on the USB standard, and information processing devices 11 and 21 can communicate with each other via USB. Alternatively, communication path 50 does not need to be a wired cable. Information processing devices 11 and 21 can communicate with each other using a wireless LAN or a wireless personal area network (WPAN).
[0127] Although the above example describes an instance in which a single virtual machine runs only a single application, a single virtual machine can run a multitude of applications.
[0128] Examples of recording media that store a program executed by the aforementioned Root-OS 180 include a USB storage device, a flexible disk, a CD (compact disc), a DVD (Digital Versatile Disc), a Blu-ray (registered trademark) disc, a magneto-optical disc (MO), an SD card (Secure Digital), a memory stick (registered trademark), and other computer-readable recording media, such as a magnetic floppy disk, an optical disk, a magneto-optical disk, a semiconductor memory, and a magnetic tape.
[0129] The foregoing describes some examples of embodiments for illustrative purposes. Although the preceding discussion presented specific embodiments, the person skilled in the art will recognize that changes in form and detail can be made without departing from the larger spirit and scope of the invention. Accordingly, the specification and the drawings are to be understood as exemplary rather than restrictive. This detailed description is therefore not to be regarded as limiting, and the scope of the invention is defined solely by the appended claims, together with the full scope of equivalents associated with those claims. Reference symbol list 001,002 Program 1 processor 2 main memory 3 subsidiary storage 4 Communication control 9 Bus 11, 21 Information processing device 12, 13, 14, 22, 23 virtual machine 50 communication channels 91, 92 Drive unit 93 Inspection device 94 Simulator 100 Information processing system 110, 210 Hypervisor 111, 112, 114, 211, 212 shared storage 113,213 Backend drivers 120, 140, 220, 240 Guest operating system 121, 141, 171, 221, 241 Frontend drivers 130, 150, 190, 230, 250 Application 161,261 Transmission Information Table 162,262 Terms of Use table 180,280 Root-OS 181, 281 Transmission administrator 182, 282 Communicator 1010 Header 1011 Target ID 1012 Source ID 1013 Type 1014 size 1020 Data section 1030 Fault detection code 1040 Communication header 1100 Communication package
Claims
[1] Information processing device (11, 21) on which a virtual environment with virtual machines (12, 13, 14, 22, 23) is constructed, the information processing device (11, 21) comprising: a root operating system (180, 280) for operation on the information processing device (11, 21); Guest operating systems (120, 140, 220, 240) for operation on the respective virtual machines (12, 13, 14, 22, 23); a shared memory (111, 112) accessible by the guest operating systems (120, 140, 220, 240) and the root operating system (180, 280); and a transmission information storage means (161) for specifying a relationship between (i) destination information (1011) indicating destinations of data specified by the virtual machines (12, 13, 14, 22, 23), and Source information (1012) indicating the sources of the data, and (ii) a transmission destination to which the data is actually to be transmitted, wherein the root operating system (180, 280) comprises transmission management means (181) for managing the transmission of data output from the virtual machines (12, 13, 14, 22, 23) and communication means (182) for communicating with another information processing device (21, 11) via a communication path (50), wherein, if the guest operating system of a first virtual machine of the virtual machines (12, 13, 14, 22, 23) first data intended for a second virtual machine of the virtual machines (12, 13, 14, 22, 23), writes together with the destination information (1011) and the source information (1012) into the common memory (111, 112), the transmission management means (181) determines whether a transmission destination is specified in the transmission information storage means (161) which is associated with the destination information (1011) and the source information (1012), wherein, upon determining that the other information processing device (21, 11) is specified as the transmission destination in the transmission information storage means (161) associated with the destination information (1011) and the source information (1012), the transmission management means (181) supplies the first data to the communication means (182), and the communication means (182) transmits the first data supplied by the transmission management means (181) to the other information processing device (21, 11), and wherein, upon determining that no transmission destination associated with the destination information (1011) and the source information (1012) is specified in the transmission information storage means (161), the transmission management means (181) transmits the first data to the second virtual machine. [2] The information processing apparatus (11, 21) according to claim 1, wherein, upon determining that a third virtual machine of the virtual machines (12, 13, 14, 22, 23) on the information processing apparatus (11, 21) is specified in the transmission information storage means (161) as the transmission destination associated with the destination information (1011) and the source information (1012), the transmission management means (181) supplies the first data to the third virtual machine. [3] Information processing device (11, 21) according to claim 1 or 2, wherein the transmission information storage means (161) specifies a transmission destination of data sent and received between the virtual machines (12, 13, 14, 22, 23) based on the destination information (1011) and the source information (1012) and identification information (1013) for identifying an application executed on the virtual machine (12, 13, 14, 22, 23), wherein the guest operating system of the first virtual machine writes data intended for the second virtual machine together with the destination information (1011) and the source information (1012) and the identification information (1013) into the shared memory (111, 112), the data being output by the application executing on the first virtual machine, and wherein the transmission management means (181) determines a destination for the transmission of the first data based on the destination information (1011) and the source information (1012) and the identification information (1013) read from the common memory (111, 112). [4] Information processing device (11, 21) according to one of claims 1 to 3, further comprising: an active / inactive setting condition storage means in which it is set whether the specification of the transmission destination by the transmission information storage means (161) is active or not, wherein, when the transmission management means (181) determines in the first data read from the common memory (111, 112) that specifying the transmission destination in the active / inactive setting condition storage means is active in a case where the transmission destination is specified in the transmission information storage means (161), the transmission management means (181) delivers the first data to the transmission destination specified in the transmission information storage means (161). [5] Information processing device (11, 21) according to one of claims 1 to 4, wherein, upon writing the first data to the shared memory (111, 112), the guest operating system of the first virtual machine notifies the root operating system (180, 280) that the writing of the data to the shared memory (111, 112) has been completed, and wherein upon receiving the notification from the guest operating system of the first virtual machine that the writing of the data is complete, the root operating system (180, 280) reads the first data from the shared memory (111, 112). [6] Information processing device (11, 21) according to one of claims 1 to 5, wherein, upon writing the first data into the shared memory (111, 112) to transmit the first data to its transmission destination, the transmission management means (181) notifies the guest operating system of the virtual machine, which is a destination for the transmission of the first data, that the writing of the first data into the shared memory (111, 112) has been completed, and wherein, upon receiving the notification from the transmission management means (181) that the writing of the first data is completed, the guest operating system of the virtual machine to which the first data is transmitted reads the first data from the shared memory (111, 112). [7] A method for transmitting data sent and received between virtual machines (12, 13, 14, 22, 23) on an information processing device (11, 21) on which a virtual environment with the virtual machines (12, 13, 14, 22, 23) is constructed, the information processing device (11, 21) comprising: a root operating system (180, 280) for operation on the information processing device (11, 21), Guest operating systems (120, 140, 220, 240) for operation on the respective virtual machines (12, 13, 14, 22, 23), a shared memory (111, 112) accessible by the guest operating systems (120, 140, 220, 240) and the root operating system (180, 280), and a transmission information storage means (161) for specifying a relationship between (i) destination information (1011) indicating destinations of data specified by the virtual machines (12, 13, 14, 22, 23), and Source information (1012) indicating sources of the data, and (ii) a transmission destination to which the data is actually to be transmitted, the method comprising: Writing first data intended for a second virtual machine of the virtual machines (12, 13, 14, 22, 23) together with the destination information (1011) and the source information (1012) into the shared memory (111, 112) by the guest operating system of a first virtual machine of the virtual machines (12, 13, 14, 22, 23); Determining, by the root operating system (180, 280), whether a transmission destination associated with the destination information (1011) and the source information (1012) written in the common memory (111, 112) is specified in the transmission information storage means (161); upon determining that the transmission destination of the first data is specified in the transmission information storage means (161), determining, by the root operating system (180, 280), whether another information processing device (21, 11) is specified as the transmission destination in the transmission information storage means (161); upon determining that the other information processing device (21, 11) is specified in the transmission information storage means (161) as the transmission destination associated with the destination information (1011) and the source information (1012), transmitting, by the root operating system (180, 280), the first data to the other information processing device (21, 11); and upon determining that no transmission destination associated with the destination information (1011) and the source information (1012) is specified in the transmission information storage means (161), transmitting the first data to the second virtual machine by the root operating system (180, 280). [8] A program for execution by a root operating system (180, 280) running on an information processing device (11, 21) on which a virtual environment with virtual machines (12, 13, 14, 22, 23) is constructed, the information processing device (11, 21) comprising: the root operating system (180, 280), Guest operating systems (120, 140, 220, 240) for operation on the respective virtual machines (12, 13, 14, 22, 23), a shared memory (111, 112) accessible by the guest operating systems (120, 140, 220, 240) and the root operating system (180, 280), and transmission information storage means (161) for specifying a relationship between (i) destination information (1011) indicating destinations of data sent and received between the virtual machines (12, 13, 14, 22, 23) and source information (1012) indicating sources of the data, and (ii) a transmission destination to which the data is actually to be transmitted, wherein the program causes the root operating system (180, 280) to execute instructions comprising: when the guest operating system of a first virtual machine of the virtual machines (12, 13, 14, 22, 23) writes first data intended for a second virtual machine of the virtual machines (12, 13, 14, 22, 23) together with the destination information (1011) and the source information (1012) into the shared memory (111, 112), determining whether a delivery destination associated with the destination information (1011) and the source information (1012) is specified in the delivery information storage means (161), upon determining that the transmission destination for the first data is specified in the transmission information storage means (161), determining whether another information processing device (21, 11) is specified as the transmission destination in the transmission information storage means (161); upon determining that the other information processing device (21, 11) is specified in the transmission information storage means (161) as the transmission destination associated with the destination information (1011) and the source information (1012), transmitting the first data to the other information processing device (21, 11); and upon determining that no transmission destination associated with the destination information (1011) and the source information (1012) is specified in the transmission information storage means (161), transmitting the first data to the second virtual machine.
Citation Information
Patent Citations
Chaining Virtual Network Function Services via Remote Memory Sharing
US20170168985A1
Migration of guest bridge
US9553764B2
