JP6045397B2 - Virtual computer system, fault simulation method and fault simulation program for virtual computer system - Google Patents

Description

  The present invention relates to a virtual machine system in a virtual machine using para-virtualization, a fault simulation method of a virtual machine system, and a fault simulation program. In particular, the present invention relates to a virtual computer system that simulates a hardware failure in a guest computer using para-virtualization and checks the operation of a failure processing function, a failure simulation method of the virtual computer system, and a failure simulation program.

  Aggregating a plurality of computers using virtualization technology is useful in terms of effective use of server resources and reducing operational costs, and in recent years, cases of server aggregation using virtualization technology are increasing. As the number of cases increases, the reliability of virtual machines becomes important.

In a configuration in which multiple virtual machines are aggregated on a single computer, the failure of the host computer has a large effect on the guest computer, so the guest computer and the application on the guest computer when a failure occurs in the host computer It is important to verify the operation.
Against this background, it is becoming possible to check the operation of a guest application by simulating a hardware failure in a virtual environment.

  There is a technique for simulating information on I / O ports, memory-mapped I / O, or interrupts in a virtualized environment so that the normality of a fault processing function of a system built in the virtualized environment can be confirmed (for example, , See Patent Document 1).

JP 2011-227700 A

In the virtual environment, there are two device emulation methods.
The first is a method called complete virtualization, which reproduces all the operations of the real device including the device registers. Since the real device is completely reproduced in the complete virtualization, the same device driver as that used in the real computer can be used as the guest OS (Operating System) device driver. However, since device emulation is a large overhead, the device I / O performance of the guest OS is not high.

On the other hand, in the second method called para-virtualization, device emulation is simplified and an interface between the host OS and the guest OS (hereinafter referred to as I / F) is mounted so as to be convenient for the virtual environment. .
In the para-virtualization method, device I / O is zero-copy I / O by address passing using shared memory between the host OS and guest OS, enabling faster device I / O than the full virtualization method. It becomes. In addition, since processing such as device emulation is simplified, the CPU usage rate can be reduced in the para-virtualization method.

  The technique disclosed in Patent Document 1 is intended for a complete virtualization system. In the virtualization environment to which the para-virtualization technology is applied, the device driver of the guest OS is a dedicated implementation for supporting device I / O using a shared memory. For this reason, the device driver of the guest OS when the para-virtualization technology is applied has a problem that the simulated failure cannot be detected by the guest OS because the device driver itself does not have a function of detecting the failure. .

  The present invention has been made to solve such problems. In a virtual environment to which paravirtualization is applied, a hardware failure simulated by a virtual machine monitor can be detected by a device driver on a guest OS. It is an object to obtain a virtual machine system having a mechanism for notifying a detected hardware failure to a guest OS or a guest application.

The virtual machine system according to the present invention is
In a virtual computer system in which a guest computer that is realized using a para-virtualization method by a virtual computer monitor and the guest computer to which virtual hardware is allocated by the virtual computer monitor operates,
A fault simulation request for requesting simulation of a fault of the virtual hardware, comprising a fault simulation request input unit for inputting a fault simulation request including fault definition information in which fault information for which simulation is requested is defined;
The guest computer is
A guest side driver for operating the virtual hardware,
The guest driver is
A failure information table stored in a storage device, the failure information table in which the failure definition information included in the failure simulation request input by the failure simulation request input unit is set;
A failure determination unit that determines whether or not the failure definition information is set in the failure information table by a processing device;
When the failure determination unit determines that the failure definition information is set in the failure information table, based on the failure definition information set in the failure information table,
And a failure simulation unit that simulates a failure of the virtual hardware.

  According to the virtual computer system according to one aspect of the present invention, even in the virtual computer system to which the para-virtualization technology is applied, the simulated failure can be detected by the failure determination unit of the guest computer, and the guest when the failure occurs There is an effect that it is possible to check the operation of the computer.

2 is a diagram showing a system configuration of a virtual machine system 800 according to Embodiment 1. FIG. 2 is a block configuration diagram of a virtual machine system 800 according to Embodiment 1. FIG. 6 is a diagram illustrating an example of a configuration of an H / W failure information table 440 according to Embodiment 1. FIG. 2 is a diagram illustrating an example of a hardware configuration of a real computer 100 according to the first embodiment. FIG. FIG. 10 is a sequence diagram showing an operation of the H / W failure simulation method of the virtual computer system 800 according to the first embodiment. FIG. 10 is a sequence diagram showing an operation of the H / W failure simulation method of the virtual computer system 800 according to the first embodiment. FIG. 10 is a sequence diagram showing an operation of the H / W failure simulation method of the virtual computer system 800 according to the first embodiment. 6 is a block configuration diagram of a virtual machine system 801 according to a second embodiment. FIG. FIG. 10 is a sequence diagram showing the operation of the H / W failure simulation method of the virtual machine system 801 according to the second embodiment. FIG. 10 is a block configuration diagram of a virtual computer system 802 according to a third embodiment. FIG. 10 is a sequence diagram showing an operation of the H / W failure simulation method of the virtual machine system 802 according to the third embodiment. FIG. 10 is a block configuration diagram of a virtual computer system 803 according to a fourth embodiment. FIG. 20 is a sequence diagram illustrating an operation of the H / W failure simulation method of the virtual machine system 803 according to the fourth embodiment. FIG. 20 is a diagram illustrating an example of a system configuration of a virtual machine system 804 according to a fifth embodiment. FIG. 10 illustrates a block configuration of a virtual machine system 804 according to a fifth embodiment. FIG. 20 is a sequence diagram illustrating an operation of the H / W failure simulation method of the virtual computer system 804 according to the fifth embodiment. FIG. 20 illustrates an example of a system configuration of a virtual machine system 805 according to a sixth embodiment. FIG. 20 is a block configuration diagram of a virtual computer system 805 according to a sixth embodiment. FIG. 20 is a sequence diagram illustrating the operation of the H / W failure simulation method of the virtual machine system 805 according to the sixth embodiment.

Embodiment 1 FIG.
The virtual computer system 800 according to the present embodiment detects a hardware failure simulated in a virtual computer (guest computer) using para-virtualization using a device driver of the guest OS, and notifies the guest OS and guest application of the failure. Is to do.

FIG. 1 is a diagram showing a system configuration of a virtual machine system 800 according to the present embodiment.
A system configuration of a virtual machine system 800 according to the present embodiment will be described with reference to FIG.

FIG. 1 shows a configuration example of a virtual computer system 800 using a para-virtualization technology, and uses a host OS embedded type host OS type virtual machine monitor.
The virtual machine system 800 includes a real machine 100, a host OS 200, a virtual machine 300, a guest OS 400, and a guest APP (Application) 500 (guest application).

  The real computer 100 is a computer and physical hardware for operating the virtual computer system 800. The real computer 100 includes a CPU, a memory, an interrupt controller, and the like.

  The host OS 200 (host computer) is software that operates on the real computer 100, and abstracts hardware resources such as a CPU and a memory and provides them to an application. A virtual machine monitor 210 (virtual machine monitor) is incorporated in the host OS 200 according to the present embodiment.

  The virtual machine monitor 210 is software for operating a plurality of OSs on the real computer 100, and creates the virtual computer 300 and provides it to the guest OS 400. The virtual computer 300 on which the guest OS 400 operates is an example of a guest computer.

The virtual machine monitor 210 according to the present embodiment is a host OS type virtual machine monitor.
In the host OS type virtual machine monitor, the host OS 200 operates on the real computer 100, and the virtual machine monitor 210 and the guest OS 400 operate on the host OS 200. Then, the guest APP 500 operates on the guest OS 400.

  Particularly, in the present embodiment, a virtual machine system 800 in which the virtual machine monitor 210 is incorporated as a kernel module that directly controls hardware resources such as a CPU and a memory in the host OS 200 is shown as an example.

In this embodiment, it is assumed that the para-virtualization technology is applied to the virtual machine monitor 210 and the guest OS 400.
The para-virtualization technology is a device I / O acceleration technology for the virtual computer system 800. In an environment to which the para-virtualization technology is applied, the device driver of the guest OS 400 includes the shared memory 430 between the virtual machine monitor 210 and the device driver.

In the virtual computer system 800 to which the para-virtualization technology is applied, by using this shared memory 430, high-speed device I / O is possible.
In addition, since device emulation in the virtual machine monitor 210 is simplified, the CPU load on the real computer 100 can be reduced.
In the para-virtualization technology, a virtual H / W (virtual hardware) is assigned to the guest OS 400 by the virtual machine monitor 210. In order to use the para-virtualization technology, it is necessary that the guest OS 400 and the virtual machine monitor 210 are dedicated drivers corresponding to the para-virtualization and have a driver for operating the virtual H / W. Become.

  As shown in FIG. 1, the guest OS 400 incorporates a front-end driver 420 (an example of a guest-side driver) as a driver corresponding to paravirtualization. The virtual machine monitor 210 incorporates a back-end driver 220 (an example of a monitor-side driver) as a driver corresponding to paravirtualization.

  FIG. 2 is a block configuration diagram of the virtual machine system 800 according to the present embodiment. A block configuration of the virtual machine system 800 according to the present embodiment will be described with reference to FIG.

  As shown in FIG. 2, the virtual computer system 800 further includes an H / W failure operation tool 310, a virtual machine monitor management API 230, an H / W failure information setting unit 320, a failure determination unit 450, a failure simulation unit 451, a failure A notification unit 452, a normal processing unit 453, and an H / W failure information table 440 are provided. The H / W failure information table 440 is stored in the shared memory 430 (shared storage area). “H / W” is an abbreviation for “Hardware (hardware)”. “API” is an abbreviation for “Application / Programming / Interface”.

The H / W failure operation tool 310 is an application that operates on the host OS 200. The H / W failure operation tool 310 serves as a user interface when the user operates the H / W failure.
The virtual computer system 800 is an example of a failure simulation system that simulates an H / W failure and confirms the function of the system against the H / W failure.
The H / W fault operation tool 310 is a fault simulation request for requesting simulation of a virtual hardware fault, and includes a fault simulation request including fault definition information in which fault information for which simulation is required is defined. Input from the user. The H / W failure operation tool 310 is an example of a failure simulation request input unit.

The virtual machine monitor management API 230 is a library that manages the virtual memory and virtual network of the virtual machine 300 (virtual machine).
In the present embodiment, the virtual machine monitor management API 230 is used as an example, but the virtual machine monitor 210 is not limited to the virtual machine monitor management API 230 as long as the virtual machine monitor 210 can be operated from the outside.

The H / W failure information setting unit 320 (failure information setting unit) is an H / W failure information table 440 (failure information table) constructed in a shared memory 430 area that can be used between the front-end driver 420 and the back-end driver 220. On the other hand, it is a functional module for writing H / W failure information 441 (failure definition information).
In the present embodiment, the H / W failure information setting unit 320 is mounted on the back-end driver 220 of the virtual machine monitor 210.

  FIG. 3 is a diagram showing an example of the configuration of the H / W failure information table 440 according to the present embodiment. The configuration of the H / W failure information table 440 according to the present embodiment will be described with reference to FIG.

  The H / W failure information table 440 is a table in which information about an H / W failure for executing simulation is set. In the H / W failure information table 440, H / W failure information 441 (failure definition information) included in the failure content instruction (failure simulation request) input by the H / W failure operation tool 310 is set. The H / W failure information 441 includes failure type information that specifies the type of failure and failure content information that specifies the content of the failure.

  As shown in FIG. 3, H / W failure information 441 is set for each device in the H / W failure information table 440. For example, H / W failure information 441a of device A, H / W failure information 441b of device B, and the like are configured.

  The H / W failure information 441 includes information such as H / W information, failure type, failure content, register value (H / W information, failure type, failure content, register value, etc. Hereinafter, it is referred to as H / W failure information 441). One H / W failure information 441 exists for each virtual device of the guest OS 400.

In “H / W information”, information indicating a virtual device that is a target for generating an H / W failure is set. From the set H / W information, the guest OS 400 or the virtual device that is the target for generating the H / W failure is specified.
In the “H / W information”, for example, a file path on the host OS 200 is set for a block device. In the case of a network device, information that can specify a virtual H / W such as a MAC address is set.

“Fault type” is information indicating a fault to be simulated. The “failure type” can clearly distinguish between the case where H / W failure generation is not instructed and the case where H / W failure generation is instructed.
In the present embodiment, for example, when the value of “failure type” is 0, there is no H / W failure generation instruction, and when it is other than 0, there is an H / W failure generation instruction. Further, when a value other than 0 is set, it is assumed that the H / W failure generated by the set value can be determined. For example, when the value of “failure type” is 1, the response delay of the virtual device is simulated, and when the value of “failure type” is 2, the non-response state of the virtual device is simulated.

The “contents of failure” is a value for instructing a specific processing method for simulating the H / W failure specified by “type of failure”.
The case where the H / W failure to be generated (simulated) is a response delay of the virtual device is taken as an example. In this case, a time for delaying the response is set in “contents of failure”. The delay time set in “content of failure” can be arbitrarily specified.
Further, a case where the H / W failure to be generated is no response from the virtual device is taken as an example. In this case, by specifying the number of times the virtual device response is discarded in the “failure content”, the failure is simulated so that the virtual device becomes unresponsive for the number of times specified in the “failure content”.

The “register value” stores a value to be set as the value of the device register of the virtual device. The device register is a register in which information for communicating the guest OS 400 and the device is stored.
When para-virtualization is applied to the virtual machine system 800, the device register is not simulated by the virtual machine monitor 210, and thus the device register of the virtual device does not actually exist. However, when a failure simulation unit 451 or a failure notification unit 452 to be described later notifies the guest OS 400 or the guest APP 500 (guest application) of the H / W failure, it may be necessary to pass the value of the device register. In such a case, the failure simulation unit 451 or the failure notification unit 452 uses the value stored in the “register value”. Further, even when a request for referring to a device register is issued from the guest OS 400 when an H / W failure occurs, an arbitrary value can be stored and passed to the “register value”. The device register reference request from the guest OS 400 is, for example, when the device is accessed.

The failure determination unit 450 is called from an interrupt handler in the front-end driver 420 when a virtual interrupt from the virtual machine monitor 210 is input. The failure determination unit 450 determines whether failure simulation is instructed according to the H / W failure information table 440 in the shared memory 430.
The failure determination unit 450 determines whether the value of the “failure type” in the H / W failure information table 440 is cleared to 0 or a value other than 0 is set by the processing device. It is determined whether or not there is an instruction for generating a W fault.

  The failure simulation unit 451 simulates an H / W failure based on the contents of the H / W failure information table 440 in the shared memory 430. The failure simulation unit 451 simulates failure details and failure information required by the guest OS 400 and the guest APP 500.

  The failure notification unit 452 notifies the guest OS 400 or the guest APP 500 of a failure that has occurred in H / W.

  The normal processing unit 453 is a part that performs normal functions as a device driver such as device I / O and device I / O completion processing.

  FIG. 4 is a diagram illustrating an example of a hardware configuration of the real computer 100.

  In FIG. 4, an actual computer 100 is a computer, and includes an LCD 901 (Liquid / Crystal / Display), a keyboard 902 (K / B), a mouse 903, an FDD 904 (Flexible / Disk / Drive), and a CDD 905 (Compact / Disc / Drive). , A hardware device such as a printer 906 is provided. These hardware devices are connected by cables and signal lines. Instead of the LCD 901, a CRT (Cathode / Ray / Tube) or other display device may be used. Instead of the mouse 903, a touch panel, a touch pad, a trackball, a pen tablet, or other pointing devices may be used.

  The real computer 100 includes a CPU 911 (Central Processing Unit) that executes a program. The CPU 911 is an example of a processing device. The CPU 911 includes a ROM 913 (Read / Only / Memory), a RAM 914 (Random / Access / Memory), a communication board 915, an LCD 901, a keyboard 902, a mouse 903, an FDD 904, a CDD 905, a printer 906, and an HDD 920 (Hard / Disk) via a bus 912. A drive is connected to the magnetic disk device to control these hardware devices. Instead of the HDD 920, a flash memory, an optical disk device, a memory card reader / writer, or other recording medium may be used.

  The RAM 914 is an example of a volatile memory. The ROM 913, the FDD 904, the CDD 905, and the HDD 920 are examples of nonvolatile memories. These are examples of the storage device. The communication board 915, the keyboard 902, the mouse 903, the FDD 904, and the CDD 905 are examples of input devices. The communication board 915, the LCD 901, and the printer 906 are examples of output devices.

  The communication board 915 is connected to a LAN (Local / Area / Network) or the like. The communication board 915 is not limited to a LAN, but is an IP-VPN (Internet, Protocol, Private, Network), a wide area LAN, an ATM (Asynchronous / Transfer / Mode) network, a WAN (Wide / Area / Network), or the Internet. It does not matter if it is connected to. LAN, WAN, and the Internet are examples of networks.

  The HDD 920 stores an operating system 921 (OS), a window system 922, a program group 923, and a file group 924. The programs in the program group 923 are executed by the CPU 911, the operating system 921, and the window system 922. The program group 923 includes programs that execute the functions described as “˜units” in the description of the present embodiment. The program is read and executed by the CPU 911. The file group 924 includes data, information, and signal values described as “˜data”, “˜information”, “˜ID (identifier)”, “˜flag”, and “˜result” in the description of this embodiment. And variable values and parameters are included as items of “˜file”, “˜database”, and “˜table”. The “˜file”, “˜database”, and “˜table” are stored in a recording medium such as the RAM 914 or the HDD 920. Data, information, signal values, variable values, and parameters stored in a recording medium such as the RAM 914 and the HDD 920 are read out to the main memory and the cache memory by the CPU 911 via a read / write circuit, and extracted, searched, referenced, compared, and calculated. It is used for processing (operation) of the CPU 911 such as calculation, control, output, printing, and display. During the processing of the CPU 911 such as extraction, search, reference, comparison, calculation, calculation, control, output, printing, and display, data, information, signal values, variable values, and parameters are temporarily stored in the main memory, cache memory, and buffer memory. Remembered.

  The arrows in the block diagrams and flowcharts used in the description of this embodiment mainly indicate input / output of data and signals. Data and signals are recorded in memory such as RAM 914, FDD904 flexible disk (FD), CDD905 compact disk (CD), HDD920 magnetic disk, optical disk, DVD (Digital Versatile Disc), or other recording media Is done. Data and signals are transmitted by a bus 912, a signal line, a cable, or other transmission media.

  In the description of the present embodiment, what is described as “to part” may be “to circuit”, “to device”, “to device”, and “to step”, “to process”, “to”. ~ Procedure "," ~ process ". That is, what is described as “˜unit” may be realized by firmware stored in the ROM 913. Alternatively, what is described as “˜unit” may be realized only by software, or only by hardware such as an element, a device, a board, and wiring. Alternatively, what is described as “to part” may be realized by a combination of software and hardware, or a combination of software, hardware and firmware. Firmware and software are stored as programs in a recording medium such as a flexible disk, a compact disk, a magnetic disk, an optical disk, and a DVD. The program is read by the CPU 911 and executed by the CPU 911. That is, the program causes the computer to function as “to part” described in the description of the present embodiment. Or a program makes a computer perform the procedure and method of "-part" described by description of this Embodiment.

Next, an operation for realizing the H / W failure simulation method in the virtual computer system 800 will be described.
FIG. 5 is a sequence diagram showing the operation of the H / W failure simulation method of the virtual machine system 800 according to this embodiment. FIG. 5 shows a sequence until the user sets the H / W failure information 441 in the H / W failure information table 440 using the H / W failure operation tool 310.
FIG. 6 is a sequence diagram showing the operation of the H / W failure simulation method of the virtual machine system 800 according to this embodiment. FIG. 6 shows the operation of the guest OS 400 when the H / W failure information 441 is set in the H / W failure information table 440.
FIG. 7 is a sequence diagram showing the operation of the H / W failure simulation method of the virtual machine system 800 according to this embodiment. FIG. 7 shows the operation of the guest OS 400 when the H / W failure information 441 is not set in the H / W failure information table 440.

A sequence until the user sets the H / W failure information 441 in the H / W failure information table 440 using the H / W failure operation tool 310 will be described with reference to FIG.
First, when the user of the virtual computer system 800 uses the H / W failure simulation method, H / W information and failure information are displayed on the H / W failure operation tool 310 from the display or the like (input device) of the actual computer 100. Information that is the basis of the H / W failure information 441 such as the type and the content of the failure is input.
That is, the user instructs the virtual machine monitor management API 230 to generate an H / W failure using the H / W failure operation tool 310.

  In S100, the H / W failure operation tool 310 outputs the content information of the H / W failure input by the user to the virtual machine monitor management API 230, and instructs the generation of the H / W failure. Output generation instructions. This H / W failure generation instruction includes information such as the guest OS 400 to be simulated for the H / W failure, virtual device, H / W failure type, H / W failure content, and device register value.

  In S 101, the virtual machine monitor management API 230 inputs an H / W failure generation instruction from the H / W failure operation tool 310. When the H / W failure generation instruction is input, the virtual machine monitor management API 230 issues (outputs) an H / W failure generation command to the H / W failure information setting unit 320 in the virtual machine monitor 210.

In S <b> 102, the H / W failure information setting unit 320 inputs an H / W failure generation command from the virtual machine monitor management API 230. The H / W failure generation command includes a guest OS 400 (hereinafter referred to as a simulation target guest OS 400a), a virtual device, a type of H / W failure, a content of the H / W failure, a device Contains information such as register values.
When an H / W failure generation command is input, the H / W failure information setting unit 320 receives the H of the simulation target guest OS 400a in the H / W failure information table 440 of the shared memory 430 based on the input H / W failure generation command. H / W failure information is set in the / W failure information 441a.

The H / W failure information setting unit 320 sets H / W failure information in the H / W failure information 441a of the simulation target guest OS 400a specified by the H / W failure generation command.
Then, immediately after the H / W failure information setting unit 320 sets the H / W failure information in the H / W failure information 441a, the back-end driver 220 raises a virtual interrupt to the simulation target guest OS 400a.
That is, the H / W failure information setting unit 320 executes setting of H / W failure information in the H / W failure information 441a, and the back-end driver 220 transmits a virtual interrupt signal to the simulation target guest OS 400a.

As shown in S103, when the H / W failure information is normally set in the H / W failure information 441a of the H / W failure information table 440 of the shared memory 430, the write completion signal is set to the H / W failure information setting. Is output to the unit 320.
In S104, upon receiving a write completion signal from the shared memory 430, the H / W failure information setting unit 320 transmits an H / W failure generation response corresponding to the H / W failure generation command to the virtual machine monitor management API 230. .
In S105, when receiving the H / W failure generation response from the H / W failure information setting unit 320, the virtual machine monitor management API 230 sends an H / W failure generation instruction response corresponding to the H / W failure generation instruction to the H / W. It transmits to the failure operation tool 310.
When the H / W failure operation tool 310 receives the H / W failure generation instruction response from the virtual machine monitor management API 230, the H / W failure operation tool 310 issues a notification of completion of H / W failure generation corresponding to the H / W failure generation instruction from the user. You may output to the display etc. of the computer 100. FIG.

  FIG. 6 shows the operation of the guest OS 400 when the H / W failure information 441 of the H / W failure information table 440 is set.

  First, in S200, when a virtual interrupt is raised from the back-end driver 220 to the front-end driver 420 of the guest OS 400 to be simulated (see the description of the processing in S102 in FIG. 5), first, an interrupt in the front-end driver 420 is obtained. Processing enters the fault determination unit 450 from the handler.

In S201, the failure determination unit 450 refers to the H / W failure information table 440 in the shared memory 430 and determines whether the H / W failure information 441 is set by the processing device.
Since the H / W failure information 441 is set here, the failure determination unit 450 determines that the H / W failure information 441 is set in the H / W failure information table 440, and the H / W failure information 441 is determined. Is read (S202).

  Next, the process proceeds to the failure simulation unit 451 and the failure notification unit 452 (S203 and S205).

In S203, the failure determination unit 450 transmits, for example, a failure simulation signal including the read H / W failure information 441 to the failure simulation unit 451.
When receiving the failure simulation signal from the failure determination unit 450, the failure simulation unit 451 generates a H / W failure in a simulated manner based on the H / W failure information 441 included in the failure simulation signal.
Further, the failure simulation unit 451, when there is a reference to the failure content from the guest OS 400 or the guest APP 500, performs H / W based on the H / W failure information 441 included in the failure simulation signal received from the failure determination unit 450. The contents of the failure are simulated, and the contents are returned to the guest OS 400 or the guest APP 500. The contents simulated at this time are, for example, the contents of the device register.

  In S204, when the simulation of the H / W failure is completed, the failure simulation unit 451 transmits a failure simulation completion signal for the failure simulation signal to the failure determination unit 450.

  In S205, when the failure determination unit 450 receives the failure simulation completion signal from the failure simulation unit 451, the failure determination unit 450 transmits a failure notification instruction to the guest OS 400 or the guest APP 500 to notify the H / W failure notification to the failure notification unit 452. To do.

In S206, when receiving the failure notification instruction from the failure determination unit 450, the failure notification unit 452 notifies the guest OS 400 or the guest APP 500 that an H / W failure has occurred. The failure notification unit 452 uses the failure notification function provided in the guest OS 400 to perform H / W failure notification. Thereby, even when the H / W failure does not actually occur, it is possible to verify whether or not the failure notification function provided in the guest OS 400 functions normally.
Here, the operation of the guest OS 400 or the guest APP 500 that has received the notification of the simulated H / W failure is not particularly mentioned. The configuration in which the notification of the H / W failure by the failure notification function provided in the guest OS 400 is raised from the driver is the same as the failure notification operation when the H / W failure occurs in the real computer system. The failure notification function of the guest OS 400 performs an operation such as displaying an H / W failure message on a display, for example.

  In S207, the failure notification function of the guest OS 400 transmits a failure notification operation response to the failure notification unit 452 regarding whether or not the failure notification operation such as displaying an H / W failure message on a display or the like is completed. For example, when the failure notification function of the guest OS 400 does not operate normally, the failure notification function of the guest OS 400 displays an error message, or brings down the guest OS 400, etc. May be notified to the user by a failure notification operation response.

In S208, when receiving the failure notification operation response from the guest OS 400, the failure notification unit 452 transmits a failure notification instruction response to the failure determination unit 450 based on the content of the failure notification operation response to the failure determination unit 450. To do.
When the failure determination unit 450 determines that the H / W failure information 441 is set in the H / W failure information table 440, the failure notification unit 452 includes the failure type information included in the H / W failure information 441 and Information including failure content information is notified.

The failure determination unit 450 receives the failure notification instruction response from the failure notification unit 452. For example, the failure determination unit 450 issues a result of the operation at the time of the H / W failure to the user based on the content of the received failure notification instruction response.
For example, the failure determination unit 450 may display a list in which the simulated H / W failure is associated with the subsequent operation of the guest OS 400 or the guest APP 500 on the display.

  FIG. 7 shows the operation of the guest OS 400 when the H / W failure information 441 is not set in the H / W failure information table 440. In the virtual computer system 800, when the H / W failure information 441 is not set in the H / W failure information table 440, when the device is accessed, a normal operation is executed.

  Here, as an example, the operation of the guest OS 400 (virtual computer system 800) when the guest OS 400 instructs the front-end driver 420 to operate the device will be described.

In S300, when the guest OS 400 is called to the front-end driver 420, the failure determination unit 450 is first processed.
In S301, the failure determination unit 450 refers to the H / W failure information table 440 in the shared memory 430, and determines (confirms) whether or not the H / W failure information 441 is set.

Here, it is assumed that the H / W failure information 441 is not set in the H / W failure information table 440.
In S302, the failure determination unit 450 determines that the H / W failure information 441 is not set in the H / W failure information table 440.

  Then, the failure determination unit 450 moves the process to the normal processing unit 453 in S303. The normal processing unit 453 executes normal processing of the front end driver 420. Here, the device operation process instructed by the guest OS 400 is executed.

As described above, the H / W failure simulation method of the virtual computer system 800 according to the present embodiment is the H / W failure simulation method of the virtual computer system 800 using the host OS type virtual machine monitor 210. Means (a) to (e) are provided. Further, an H / W failure simulation program including the following procedures (a) to (e) is executed on the virtual computer system 800 that is a computer.
(A) A shared memory 430 in which an H / W failure information table 440 for simulating an H / W failure is stored.
(B) An H / W failure information setting unit 320 for registering and updating the H / W failure information table 440.
(C) A failure determination unit 450 that branches processing in the para-virtualized driver of the guest OS 400 based on the H / W failure information table 440.
(D) A failure simulation unit 451 that simulates an H / W failure based on the H / W failure information table 440.
(E) A failure notification unit 452 that notifies the guest OS 400 or the guest APP 500 of an H / W failure.

  As described above, according to the H / W failure simulation method of the virtual machine system 800 according to the present embodiment, the H / W failure information table 440 created in the shared memory 430 between the front-end driver 420 and the back-end driver 220. Depending on whether or not the H / W failure information 441 is set, the front end driver 420 can detect whether or not an H / W failure has occurred. Then, when the H / W failure information 441 is set in the H / W failure information table 440, the failure simulation and the failure notification are performed, thereby detecting the H / W failure in the virtual environment to which the para-virtualization is applied. And failure notification can be realized. This makes it possible to check the operation of the guest OS 400 or the guest APP 500 when an H / W failure occurs in a virtual environment to which the para-virtualization technology is applied.

Embodiment 2. FIG.
In the present embodiment, differences from the first embodiment will be mainly described.
FIG. 8 is a block configuration diagram of the virtual machine system 801 according to the present embodiment.
FIG. 8 is a diagram corresponding to FIG. 2 described in the first embodiment, and components having similar functions are denoted by the same reference numerals, and description thereof may be omitted.

In this embodiment, a virtual machine environment using the host OS type virtual machine monitor 210 in which the virtual machine monitor 210 shown in FIG.
The virtual machine system 801 according to the present embodiment is a derivative form of the virtual machine system 800 described in the first embodiment. The difference from the virtual computer system 800 described in the first embodiment is that the virtual machine management API 230 (see FIG. 2) is excluded from the instruction path when generating the H / W failure.
That is, the H / W failure operation tool 310 directly inputs an H / W failure generation command to the H / W failure information setting unit 320.

  FIG. 9 is a sequence diagram showing the operation of the H / W failure simulation method of the virtual computer system 801 according to this embodiment. FIG. 9 shows a sequence until the user sets the H / W failure information 441 in the H / W failure information table 440 using the H / W failure operation tool 310.

As shown in FIG. 9, the sequence after the user instructs the H / W failure operation tool 310 to generate an H / W failure is different.
In S400, the H / W failure operation tool 310 issues (outputs) an H / W failure generation command to the H / W failure information setting unit 320 based on the content information of the H / W failure input by the user. To do.
In this embodiment, the H / W failure information setting unit 320 of the virtual machine monitor 210 is directly called from the H / W failure operation tool 310.

Other configurations and processing sequences (S401, S402) are the same as those in the first embodiment (S102, S103).
In S405, when the H / W failure information setting unit 320 receives the write completion signal from the shared memory 430, the H / W failure generation instruction response corresponding to the H / W failure generation instruction is sent to the H / W failure operation tool. To 310.

  The subsequent sequence (after setting the H / W failure information) in the H / W failure simulation method of the virtual computer system 801 according to the present embodiment is the same as that in the first embodiment.

As described above, the H / W failure simulation method of the virtual computer system 801 according to the present embodiment is the H / W failure simulation method of the virtual computer system 801 using the host OS type virtual machine monitor 210. (A) means is provided. In addition, an H / W failure simulation program including the following procedure (a) is executed on the virtual computer system 801 that is a computer.
(A) The H / W failure operation tool 310 issues a H / W failure generation command directly to the H / W failure information setting unit 320 without going through the virtual machine monitor management API 230.

  As described above, according to the virtual computer system 801 according to the present embodiment, the H / W failure information 441 is added to the H / W failure information table 440 created in the shared memory 430 between the front-end driver 420 and the back-end driver 220. Whether or not an H / W failure has occurred is detected by the front-end driver 420 depending on whether or not is set. Then, when H / W failure information 441 is set in the H / W failure information table 440, failure simulation and failure notification are performed, thereby detecting H / W failure in a virtual environment to which paravirtualization is applied. Failure notification can be realized. This makes it possible to check the operation of the guest OS 400 or the guest APP 500 when an H / W failure occurs in a virtual environment to which the para-virtualization technology is applied.

  Further, according to the virtual machine system 801 according to the present embodiment, the back-end driver 220 can be directly operated without passing through the virtual machine monitor management API 230 (see the first embodiment). Therefore, the processing for the virtual machine monitor management API 230 can be omitted, and the processing for generating an H / W failure can be speeded up. Further, compared to the case where the virtual machine management API 230 is used, the interfaces of the H / W failure operation tool 310 and the H / W failure information setting unit 320 can be freely designed and implemented.

Embodiment 3 FIG.
In the present embodiment, differences from the first and second embodiments will be mainly described.
FIG. 10 is a block configuration diagram of the virtual machine system 802 according to the present embodiment.
FIG. 10 is a diagram corresponding to FIG. 2 described in the first embodiment, and components having similar functions are denoted by the same reference numerals, and description thereof may be omitted.

A virtual machine system 802 according to the present embodiment will be described with reference to FIG.
In this embodiment, a virtual machine environment using the host OS type virtual machine monitor 210 in which the virtual machine monitor 210 shown in FIG.

The difference from the virtual machine system 800 described in the first embodiment is that the H / W failure operation tool 310 is a guest application and the H / W failure information setting unit 320 is arranged (mounted) inside the front-end driver 420. That is.
By arranging the H / W failure information setting unit 320 inside the front-end driver 420, the H / W failure information table 440 (H / W failure information 441) does not need to be placed on the shared memory 430. Therefore, in the virtual machine system 802 according to the present embodiment, the failure information holding area 480 (failure information storage area) is secured in the front-end driver 420, and the H / W failure information table 440 (H / W failure information 441). Is stored in the failure information holding area 480.

  FIG. 11 is a sequence diagram showing the operation of the H / W failure simulation method of the virtual computer system 802 according to the present embodiment. FIG. 11 shows a sequence until the user writes the H / W failure information 441 to the H / W failure information table 440 in the failure information holding area 480 using the H / W failure operation tool 310.

  The process of S500 is the same as the process of S400 of FIG. However, in this embodiment, the H / W failure operation tool 310 is a guest application, and the H / W failure information setting unit 320 is disposed inside the front-end driver 420.

In S501, when the H / W failure information setting unit 320 receives the H / W failure generation command, the H / W failure information setting unit 320 stores H in the H / W failure information table 440 of the failure information holding area 480 based on the received H / W failure generation command. / W failure information 441 is set.
The processes of S502 and S503 are the same as the processes of S402 and S403.

  The subsequent sequence (after setting the H / W failure information) in the H / W failure simulation method of the virtual computer system 802 according to the present embodiment is the same as in the first embodiment.

As described above, the H / W failure simulation method of the virtual computer system 802 according to the present embodiment is a H / W failure simulation method of the virtual computer system 802 using the host OS type virtual machine monitor 210. Means (a) to (f) are provided. In addition, on the virtual computer system 802 that is a computer, an H / W failure simulation program having the following procedures (a) to (f) is executed.
(A) An H / W failure operation tool 310 that instructs the H / W failure information setting unit 320 to generate an H / W failure based on information on the H / W failure input by the user.
(B) A failure information holding area 480 in which an H / W failure information table 440 for simulating an H / W failure is stored.
(C) An H / W failure information setting unit 320 for registering and updating the H / W failure information table 440.
(D) A failure determination unit 450 that branches processing in the para-virtualized driver of the guest OS 400 based on the H / W failure information table 440.
(E) A failure simulation unit 451 that simulates H / W failure based on the H / W failure information table 440.
(F) A failure notification unit 452 that notifies the guest OS 400 or the guest APP 500 of an H / W failure.

  As described above, according to the H / W failure simulation method of the virtual machine system 802 according to the present embodiment, the H / W failure information table 440 created in the failure information holding area 480 in the front-end driver 420 has the H / W failure information table 440. Depending on whether or not the W failure information 441 is set, the front end driver 420 can detect whether or not an H / W failure has occurred. Then, when H / W failure information 441 is set in the H / W failure information table 440, failure simulation and failure notification are performed, thereby detecting H / W failure in a virtual environment to which paravirtualization is applied. Failure notification can be realized. This makes it possible to check the operation of the guest OS 400 or the guest APP 500 when an H / W failure occurs in a virtual environment to which the para-virtualization technology is applied.

  Further, according to the H / W failure simulation method of the virtual machine system 802 according to the present embodiment, since the simulation / detection / notification processing of H / W failure is implemented only on the guest OS 400 side, the host OS 200 side There is no need to change. Further, it can be used regardless of a virtual machine monitor method such as a hypervisor type or a host OS type.

Embodiment 4 FIG.
In the present embodiment, differences from the third embodiment will be mainly described.
FIG. 12 is a block configuration diagram of the virtual machine system 803 according to the present embodiment.
FIG. 12 is a diagram corresponding to FIG. 10 described in the third embodiment, and components having similar functions are denoted by the same reference numerals, and description thereof may be omitted.

In this embodiment, a virtual machine environment using the host OS type virtual machine monitor 210 in which the virtual machine monitor 210 shown in FIG.
The virtual machine system 803 according to the present embodiment is a derivative form of the virtual machine system 802 described in the third embodiment.
The difference from the virtual machine system 802 described in the third embodiment is that the H / W failure information setting unit 320 is not the front end driver 420 but is a kernel module different from the front end driver 420. 490 (failure setting module).
Other configurations are the same as those described in the third embodiment.

  FIG. 13 is a sequence diagram showing the operation of the H / W failure simulation method of the virtual machine system 803 according to the present embodiment. FIG. 13 shows a sequence until the user writes the H / W failure information 441 into the H / W failure information table 440 using the H / W failure operation tool 310.

FIG. 13 shows a sequence from when an H / W failure generation instruction is given to the H / W failure operation tool 310 until the H / W failure information 441 is set in the failure information holding area 480. .
In S600, the H / W failure operation tool 310 issues an H / W failure generation command to the H / W failure information setting module 490.
In S601, the H / W failure information setting unit 320 of the H / W failure information setting module 490 sets H / W failure information for the failure information holding area 480 in the front-end driver.

  As described above, the difference between FIG. 13 and FIG. 11 described in the third embodiment is that the H / W failure information setting unit 320 is arranged in the H / W failure information setting module 490. Other processes (S600 to S603) are the same as S500 to S503 described in the third embodiment.

  The subsequent sequence in the H / W failure simulation method of the virtual computer system 803 according to the present embodiment (after setting the H / W failure information) is the same as in the first to third embodiments.

As described above, the H / W failure simulation method of the virtual computer system 803 according to the present embodiment is a H / W failure simulation method of the virtual computer system 803 using the host OS type virtual machine monitor 210. (A) to (c) are provided. Further, an H / W failure simulation program including the following procedures (a) to (c) is executed on the virtual computer system 803 that is a computer.
(A) An H / W failure information setting module 490 including an H / W failure information setting unit 320 is installed in the guest OS 400.
(B) The H / W failure operation tool 310 provides an H / W failure to the H / W failure information setting unit 320 in the H / W failure setting module 490 based on information on the H / W failure input by the user. Instruct the generation of.
(C) The H / W failure information setting unit 320 in the H / W failure setting module 490 sets the H / W failure information 441 in the failure information holding area 480 in the front end driver 420.

  As described above, according to the H / W failure simulation method of the virtual machine system 803 according to the present embodiment, the H / W failure information table 440 created in the failure information holding area 480 in the front-end driver 420 is stored in the H / W failure information table 440. Depending on whether or not the W failure information 441 is set, the front end driver 420 can detect whether or not an H / W failure has occurred. Then, when the H / W failure information 441 is set in the H / W failure information table 440, the failure simulation and the failure notification are performed to detect the H / W failure in the virtual environment to which the para-virtualization is applied. And failure notification can be realized. This makes it possible to check the operation of the guest OS 400 or the guest APP 500 when an H / W failure occurs in a virtual environment to which the para-virtualization technology is applied.

  Further, according to the H / W failure simulation method of the virtual machine system 803 according to the present embodiment, since the simulation / detection / notification process of the H / W failure is implemented only on the guest OS 400 side, the host OS 200 side There is no need to change. Further, it can be used regardless of the method of the virtual machine monitor 210 such as a bare metal type or a host OS type.

  Furthermore, according to the H / W failure simulation method of the virtual machine system 803 according to the present embodiment, the H / W failure information setting unit 320 is separated as a kernel module of the guest OS 400 different from the front-end driver 420. The processing load of the front end driver 420 can be reduced. Further, there are a plurality of types of front-end drivers 420 such as for block devices and for network devices. By adopting the present embodiment, the H / W failure information setting unit 320 used in the front-end driver 420 for each device can be shared as an API. It can be simplified and facilitated.

Embodiment 5. FIG.
In the present embodiment, differences from the first to fourth embodiments will be mainly described.
FIG. 14 is a diagram showing an example of a system configuration of the virtual machine system 804 according to the present embodiment. The system configuration of the virtual machine system 804 according to this embodiment will be described with reference to FIG.

  In this embodiment, components having the same functions as those described in Embodiments 1 to 4 are denoted by the same reference numerals, and the description thereof may be omitted.

  FIG. 14 shows an example of the configuration of a virtual computer system 804 using a para-virtualization technology. A virtual machine system 804 using the para-virtualization technology shown in FIG. 14 is not a host OS embedded virtual machine monitor 210 (described in the first embodiment), but a host OS type that operates as an application on the host OS 200. This is a configuration using the virtual machine monitor 210a.

The real computer 100 is physical hardware for operating the virtual computer system 804, and includes a CPU, a memory, an interrupt controller, and the like.
The host OS 200 is software that operates on the real computer 100 and abstracts hardware resources such as a CPU and a memory and provides them to an application.

The virtual machine monitor 210a is software for operating a plurality of OSs on the real computer 100, and creates the virtual computer 300 and provides it to the guest OS 400. The host OS type virtual machine monitor 210a is one in which the host OS 200 operates on the real computer 100, and the virtual machine monitor 210a and the guest OS 400 operate on the host OS 200.
In particular, in the present embodiment, a virtual machine system 804 in which the virtual machine monitor 210a operates as an application on the host OS 200 is shown as an example.

Also in this embodiment, it is assumed that the para-virtualization technology is applied to the virtual machine monitor 210a and the guest OS 400.
Since the para-virtualization technology has been described in the first embodiment, the description thereof is omitted here.

FIG. 15 is a diagram showing a block configuration of the virtual machine system 804 according to the present embodiment.
FIG. 15 is a diagram corresponding to FIG. 8 described in the second embodiment. The difference from the second embodiment is that the virtual machine monitor 210a is an application that operates on the host OS 200. The virtual machine monitor 210a includes a back-end driver 220a, and an H / W failure information setting unit 320 is mounted on the back-end driver 220a. The functional configurations of the back-end driver 220a and the H / W failure information setting unit 320 are the same as those in the second embodiment. Other configurations are the same as those in the second embodiment.

FIG. 16 is a sequence diagram showing the operation of the H / W failure simulation method of the virtual machine system 804 according to this embodiment.
FIG. 16 shows a sequence from when a failure generation instruction is given to the H / W failure operation tool 310 until the H / W failure information 441 is set in the shared memory 430.
First, in S700, when a failure generation instruction is given to the H / W failure operation tool 310, the failure is generated from the H / W failure operation tool 310 to the H / W failure information setting unit 320 of the virtual machine monitor 210a. The contents about the H / W failure are instructed.
The inter-process communication method in this case is not particularly mentioned, but for example, message passing, signal, socket communication, etc. are used.

In step S <b> 701, the H / W failure information setting unit 320 that has received an instruction to generate an H / W failure sets the H / W failure information 441 for the shared memory 430 and raises a virtual interrupt for the guest OS 400.
The subsequent sequence is the same as that in the first embodiment, and is the sequence shown in FIGS.
The sequence of S702 to S703 is the same as the sequence of S402 to S403 shown in FIG.

As described above, the H / W failure simulation method of the virtual machine system 804 according to the present embodiment uses the virtual machine system 804 using the host OS type virtual machine monitor 210a in which the virtual machine monitor 210a operates as an application of the host OS 200. H / W failure simulation method. The H / W failure simulation method of the virtual computer system 804 includes the following means (a) to (e). Further, an H / W failure simulation program including the following procedures (a) to (e) is executed on the virtual computer system 804 that is a computer.
(A) A shared memory 430 in which an H / W failure information table 440 for simulating an H / W failure is stored.
(B) An H / W failure information setting unit 320 for registering and updating the H / W failure information table 440.
(C) A failure determination unit 450 that branches processing in the para-virtualized driver of the guest OS 400 based on the H / W failure information table 440.
(D) A failure simulation unit 451 that simulates an H / W failure based on the H / W failure information table 440.
(E) A failure notification unit 452 that notifies the guest OS 400 or the guest APP 500 of an H / W failure.

  In the first to fourth embodiments, a virtual environment in which the virtual machine monitor 210 is incorporated in the host OS 200 is targeted. In the present embodiment, the virtual machine monitor 210a is configured as described above. Even in a virtual environment in which the OS operates as an application on the host OS 200, it is possible to detect and notify an H / W failure on the guest OS 400 to which the para-virtualization technology is applied. Accordingly, it is possible to check the operation of the guest OS 400 or the guest APP 500 when an H / W failure occurs in a virtual environment to which the para-virtualization technology is applied.

Embodiment 6 FIG.
In this embodiment, differences from Embodiments 1 to 5 will be mainly described.
FIG. 17 is a diagram illustrating an example of a system configuration of the virtual machine system 805 according to the present embodiment. A system configuration of the virtual machine system 805 according to the present embodiment will be described with reference to FIG.

  In this embodiment, components having the same functions as those described in Embodiments 1 to 5 are denoted by the same reference numerals, and the description thereof may be omitted.

The virtual computer system 805 according to the present embodiment has a configuration using a hypervisor type virtual machine monitor 210b.
The real computer 100 is physical hardware for operating the virtual computer system 805, and includes a CPU, a memory, an interrupt controller, and the like.
The virtual machine monitor 210b is software for operating a plurality of OSs on a real computer, and creates the virtual computer 300 and provides it to the guest OS 400.

  The hypervisor type virtual machine monitor 210b is a virtual machine monitor 210b in a form in which a virtual machine monitor directly operates on the real computer 100. The guest OS 400 operates on the virtual machine 300 simulated by the virtual machine monitor 210b.

Also in this embodiment, it is assumed that the para-virtualization technology is applied to the virtual machine monitor 210b and the guest OS 400.
Since the para-virtualization technology has been described in the first embodiment, the description thereof is omitted here.

FIG. 18 is a block configuration diagram of the virtual machine system 805 according to the present embodiment.
A virtual computer system 805 according to the present embodiment is a system using the hypervisor virtual machine monitor 210b described above.

FIG. 18 is a diagram corresponding to FIG. 8 described in the second embodiment, and the difference from the second embodiment is that the virtual machine monitor 210b is a hypervisor type virtual machine monitor. The virtual machine monitor 210b includes a back-end driver 220b, and an H / W failure information setting unit 320 is mounted on the back-end driver 220b. The functional configurations of the back-end driver 220a and the H / W failure information setting unit 320 are the same as those in the second embodiment.
Furthermore, as a point different from the second embodiment, the virtual machine system 805 according to the present embodiment uses the H / W failure operation tool 310 in addition to the guest OS 400 to be tested as an H / W failure. The guest OSu 400u for managing the virtual machine monitor 210b is arranged on the virtual machine monitor 210b.

The guest OSu 400u is provided with an H / W failure operation tool 310 as an application, and serves as a user interface for H / W failure operation.
Other configurations are the same as those in the second embodiment except that the host OS 200 does not exist.

FIG. 19 is a sequence diagram showing the operation of the H / W failure simulation method of the virtual machine system 805 according to this embodiment.
FIG. 19 shows a sequence from when a failure generation instruction is given to the H / W failure operation tool 310 until the H / W failure information 441 is set in the shared memory 430.

First, in S800, when a failure generation instruction is given to the H / W failure operation tool 310, the H / W failure operation tool 310 generates the failure to the H / W failure information setting unit 320 of the virtual machine monitor 210b. The contents about the H / W failure are instructed.
In this case, the method of inter-OS communication between the guest OS and the guest OS 1 is not particularly mentioned, but for example, packet communication is used.

In step S <b> 801, the H / W failure information setting unit 320 that has received an instruction to generate an H / W failure sets the H / W failure information 441 for the shared memory 430 and raises a virtual interrupt for the guest OS 400.
The subsequent sequence is the same as that in the first embodiment, and is the sequence shown in FIGS.
The sequence of S802 to S803 is the same as the sequence of S402 to S403 shown in FIG.

As described above, the H / W failure simulation method of the virtual computer system 804 according to the present embodiment is the H / W failure simulation method of the virtual computer system 805 using the hypervisor type virtual machine monitor 210b. The H / W failure simulation method of the virtual computer system 805 includes the following means (a) to (e). In addition, on the virtual computer system 805 that is a computer, an H / W failure simulation program including the following procedures (a) to (e) is executed.
(A) A shared memory 430 in which an H / W failure information table 440 for simulating an H / W failure is stored.
(B) An H / W failure information setting unit 320 for registering and updating the H / W failure information table 440.
(C) A failure determination unit 450 that branches processing in the para-virtualized driver of the guest OS 400 based on the H / W failure information table 440.
(D) A failure simulation unit 451 that simulates an H / W failure based on the H / W failure information table 440.
(E) A failure notification unit 452 that notifies the guest OS 400 or the guest APP 500 of an H / W failure.

As described above, according to the H / W failure simulation method of the virtual computer system 805 according to the present embodiment, even in a virtual environment in which the virtual machine monitor 210b directly operates on the real computer 100, para-virtualization is performed. It is possible to detect and notify an H / W failure on the guest OS 400 to which the technology is applied.
This makes it possible to check the operation of the guest OS 400 or the guest APP 500 when an H / W failure occurs even in a virtual environment using the hypervisor type virtual machine monitor 210b to which the para-virtualization technology is applied.

  The virtual machine system (virtual machine fault simulation system, virtual machine fault simulation method, and virtual machine fault simulation program) according to Embodiments 1 to 6 is information on H / W faults in a shared memory that can be referenced from the guest OS and host OS. Is stored, and the H / W failure is detected and notified on the guest OS in accordance with information on the H / W failure set in the shared memory from the host OS side. With this configuration, a hardware failure simulated in the virtual machine monitor can be detected from the guest OS device driver in the virtual machine environment to which the para-virtualization technology is applied, and the guest OS device driver can detect the hardware failure. Can be notified to the guest OS or guest application. This makes it possible to check the operation of the guest application when a hardware failure occurs on the virtual machine environment to which the para-virtualization technology is applied.

  The virtual computer system (virtual computer failure simulation system, virtual computer failure simulation method, and virtual computer failure simulation program) according to the first to sixth embodiments is a virtualization environment including a device driver for a semi-virtualization method. Any configuration having a means for giving a fault simulation instruction can be realized regardless of the difference in the construction method of the virtual environment. For example, the present invention can be applied not only to a host OS embedded type virtual machine monitor, but also to a type of virtual machine monitor that operates the host OS as an application, or a hypervisor type virtual machine monitor that directly operates on hardware.

  In the description of the first to sixth embodiments, for example, the “H / W failure information setting unit”, “failure determination unit”, “failure simulation unit”, “failure notification unit”, and “normal processing unit” are independent of each other. It is configured as a functional block. However, it is not limited to this. For example, "Fault determination unit", "Fault simulation unit" and "Fault notification unit" are realized with one functional block, and "Normal processing unit" is realized with one functional block. You may do it. Alternatively, these functional blocks may be configured in any other combination.

  As mentioned above, although embodiment of this invention was described, you may implement in combination of 2 or more among these embodiment. Alternatively, one of these embodiments may be partially implemented. Alternatively, two or more of these embodiments may be partially combined. In addition, this invention is not limited to these embodiment, A various change is possible as needed.

  100 real machine, 200 host OS, 210, 210a, 210b virtual machine monitor, 220 back-end driver, 230 virtual machine monitor management API, 300 virtual machine, 310 H / W failure operation tool, 320 H / W failure information setting unit , 400 guest OS, 420 front-end driver, 430 shared memory, 440 H / W failure information table, 441 H / W failure information, 450 failure determination unit, 451 failure simulation unit, 452 failure notification unit, 453 normal processing unit, 500 Guest APP, 800, 801, 802, 803, 804, 805 Virtual computer system, 901 LCD, 902 keyboard, 903 mouse, 904 FDD, 905 CDD, 906 printer, 911 CPU, 912 bus, 913 ROM, 914 RAM, 915 communication board, 920 HDD, 921 operating system, 922 window system, 923 programs, 924 files.

Claims (11)

In a virtual computer system in which a guest computer that is realized using a para-virtualization method by a virtual computer monitor and the guest computer to which virtual hardware is allocated by the virtual computer monitor operates,
A fault simulation request for requesting simulation of a fault of the virtual hardware, comprising a fault simulation request input unit for inputting a fault simulation request including fault definition information in which fault information for which simulation is requested is defined;
The guest computer is
A guest side driver for operating the virtual hardware,
The guest driver is
A failure information table stored in a storage device, the failure information table in which the failure definition information included in the failure simulation request input by the failure simulation request input unit is set;
A failure determination unit that determines whether or not the failure definition information is set in the failure information table by a processing device;
When the failure determination unit determines that the failure definition information is set in the failure information table, the failure of the virtual hardware is determined based on the failure definition information set in the failure information table. A virtual computer system comprising a failure simulation unit to simulate. The failure simulation request input unit
The failure definition information includes failure type information for specifying the type of failure, and failure content information for specifying the content of the failure,
The obstacle simulation part
Simulating a failure specified by the failure type information and the failure content information included in the failure definition information set in the failure information table,
The guest side driver further includes:
A failure for notifying information including the failure type information and the failure content information included in the failure definition information when the failure determination unit determines that the failure definition information is set in the failure information table The virtual machine system according to claim 1, further comprising a notification unit. The virtual machine system is
A failure information setting unit that inputs the failure definition information included in the failure simulation request input by the failure simulation request input unit and writes the input failure definition information in the failure information table is provided. Item 3. The virtual computer system according to Item 1 or 2. The guest driver is
A shared storage area shared with the virtual machine monitor,
The failure information table is
Stored in the shared storage area,
The virtual machine monitor is
A monitor-side driver that operates the virtual hardware assigned to the guest computer and is equipped with the failure information setting unit,
The virtual computer system further includes:
A host computer having the virtual computer monitor incorporated therein;
The host computer
The failure simulation request is input from the failure simulation request input unit, and the input failure simulation request is input to the failure information setting unit mounted on the monitor driver of the virtual machine monitor,
The failure information setting unit
4. The virtual computer system according to claim 3, wherein the failure definition information included in the inputted failure simulation request is set in the failure information table stored in the shared storage area of the guest side driver. . The host computer
An interface unit for inputting the failure simulation request input from the failure simulation request input unit to the virtual machine monitor;
The failure information setting unit
5. The virtual computer system according to claim 4, wherein the failure simulation request input from the failure simulation request input unit is input via the interface unit of the host computer. The guest driver is
A failure information storage area for storing the failure information table is provided, and the failure information setting unit is mounted.
The failure information setting unit
The failure simulation request is input from the failure simulation request input unit, and the failure definition information included in the input failure simulation request is set in the failure information table stored in the failure information storage area. The virtual computer system according to claim 3. The guest computer is
A failure setting module including the failure information setting unit;
The guest driver is
A failure information storage area for storing the failure information table;
The failure information setting unit
The fault simulation request is input from the fault simulation request input unit, and the fault definition information included in the input fault simulation request is set in the fault information table provided in the guest side driver. 3. The virtual computer system according to 3. The guest driver is
A shared storage area shared with the virtual machine monitor,
The failure information table is
Stored in the shared storage area,
The virtual machine monitor is
A monitor-side driver that operates the virtual hardware assigned to the guest computer and is equipped with the failure information setting unit,
The virtual computer system further includes:
The virtual machine monitor and the failure simulation request input unit comprise a host computer that operates as an application program,
The host computer
The fault simulation request input by the fault simulation request input unit is input to the virtual machine monitor,
The failure information setting unit installed in the monitor side driver of the virtual machine monitor is:
4. The failure definition information included in the failure simulation request input from the host computer is set in the failure information table stored in the shared storage area of the guest driver. Virtual computer system. The guest driver is
A shared storage area shared with the virtual machine monitor,
The failure information table is stored in the shared storage area,
The virtual machine monitor is
A monitor-side driver that operates the virtual hardware assigned to the guest computer and is equipped with the failure information setting unit,
The virtual computer system further includes:
An input computer for operating the fault simulation request input unit;
The input computer is
The failure simulation request input unit inputs the failure simulation request, and the input failure simulation request is input to the virtual machine monitor,
The failure information setting unit installed in the monitor side driver of the virtual machine monitor is:
4. The failure definition information included in the failure simulation request input from the input computer is set in the failure information table stored in the shared storage area of the guest side driver. The virtual computer system described. In a virtual machine system fault simulation method in which a guest computer that is realized by using a para-virtualization method by a virtual computer monitor and the guest computer to which virtual hardware is allocated by the virtual computer monitor operates,
The failure simulation request input unit is a failure simulation request for requesting simulation of a failure of the virtual hardware, and inputs a failure simulation request including failure definition information in which information on a failure to be simulated is defined,
The failure information setting unit inputs the failure definition information included in the failure simulation request input by the failure simulation request input unit, and sets the input failure definition information in a failure information table included in the guest computer. ,
The failure determination unit determines whether or not the failure definition information is set in the failure information table,
When the failure simulation unit determines that the failure definition information is set in the failure information table by the failure determination unit, based on the failure definition information set in the failure information table, the virtual simulation unit A fault simulation method for a virtual machine system, characterized by simulating a hardware fault. In a guest computer that is realized by a virtual computer monitor using a para-virtualization method, a computer simulation program in which a virtual computer system on which a guest computer to which virtual hardware is allocated by the virtual computer monitor operates is installed,
A fault simulation request input unit is a fault simulation request for requesting simulation of a fault of the virtual hardware, and inputs a fault simulation request including fault definition information in which information of a fault that is required to be simulated is defined Request input processing,
The failure information setting unit inputs the failure definition information included in the failure simulation request input by the failure simulation request input process, and sets the input failure definition information in a failure information table included in the guest computer Fault information setting processing,
A failure determination unit that determines whether the failure definition information is set in the failure information table;
When the failure simulation unit determines that the failure definition information is set in the failure information table by the failure determination process, the failure simulation unit performs the virtual processing based on the failure definition information set in the failure information table. A failure simulation program that causes a computer on which the virtual computer system is mounted to execute a failure simulation process that simulates a hardware failure.

Images