WO2012137239A1 - Système informatique - Google Patents

Système informatique Download PDF

Info

Publication number
WO2012137239A1
WO2012137239A1 PCT/JP2011/001992 JP2011001992W WO2012137239A1 WO 2012137239 A1 WO2012137239 A1 WO 2012137239A1 JP 2011001992 W JP2011001992 W JP 2011001992W WO 2012137239 A1 WO2012137239 A1 WO 2012137239A1
Authority
WO
WIPO (PCT)
Prior art keywords
machine
guest
dump
host machine
area
Prior art date
Application number
PCT/JP2011/001992
Other languages
English (en)
Japanese (ja)
Inventor
成昊 金
英児 西島
Original Assignee
株式会社日立製作所
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社日立製作所 filed Critical 株式会社日立製作所
Priority to PCT/JP2011/001992 priority Critical patent/WO2012137239A1/fr
Publication of WO2012137239A1 publication Critical patent/WO2012137239A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0706—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment
    • G06F11/0712—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation the processing taking place on a specific hardware platform or in a specific software environment in a virtual computing platform, e.g. logically partitioned systems
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G06F11/0778—Dumping, i.e. gathering error/state information after a fault for later diagnosis

Definitions

  • the present invention relates to an information processing apparatus having a virtualization function and a failure analysis information acquisition method applied to the apparatus.
  • a virtualization system can be easily constructed on a computer such as a personal computer.
  • Patent Document 1 the contents (data) of a memory for a guest machine operating on a virtual machine monitor (corresponding to a host machine) are periodically acquired and stored, and the latest memory stored when a failure occurs is stored.
  • a method for recovering memory contents using contents is disclosed. This method turns off the writable bit in the page table, generates a memory protection interrupt when the processor tries to update the page data, and reserves the page contents in advance in the interrupt processing routine. It is to save in the memory area.
  • Non-Patent Document 1 when trying to acquire and save the memory contents of the virtual machine monitor using the conventional memory dump technology (Non-Patent Document 1), it is necessary to stop the virtual machine monitor. It is necessary to stop other guest machines operating on the virtual machine monitor, which gives a large overhead to the other guest machines.
  • a technology is provided to acquire and store information necessary for failure analysis of the guest machine without giving a large overhead to other guest machines.
  • the computer has a plurality of guest machines, each of which is a virtual calculation statement having an operation system, and a host machine having an operation system different from the plurality of guest machines and controlling the plurality of guest machines.
  • the computer system further includes a processor for executing the operation system of each of the plurality of guest machines and the operation system of the host machine, and a memory.
  • the memory includes a memory area for the host machine allocated to the host machine, data And a save memory area. Data stored in the host machine memory area is updated by processing executed by the guest machine.
  • the host machine uses the area in the host machine memory area associated with the failure as a dump acquisition area and prohibits writing to the dump acquisition area.
  • the host machine When the host machine receives a write request to the dump acquisition area from a guest machine other than the guest machine where the failure occurred, the host machine copies the data stored in the dump acquisition area to the data save memory area. Then, write to the dump acquisition area is permitted and data is written according to the write request.
  • FIG. 1 is a configuration diagram of a computer system 10 according to this embodiment.
  • FIG. 2 is a diagram showing in detail the configuration in the host computer (also called host machine) 110 of the computer system 10.
  • host computer also called host machine
  • the computer system 10 has a configuration in which a memory 190, one or more processors 170, and a communication interface 180 are connected by a communication path such as a bus.
  • the computer system 10 may include an output device such as a display and an input device such as a keyboard.
  • An external storage device 200 is connected to the communication interface 180.
  • the memory 190 of the computer system 10 stores a program to be executed by the processor 170, and is provided with a later-described saving memory section 160.
  • the processor 170 is a multi-core processor equipped with a plurality of processor cores (hereinafter also referred to as CPU cores or simply cores).
  • the computer system (hereinafter also referred to as a physical machine) 10 creates a virtual environment on the physical machine by executing a virtualization program (also referred to as a virtualization mechanism) 113, and one or a plurality of guest machines on the physical machine It is a computer system that constitutes (also called a virtual machine).
  • the memory 190 of the computer system 10 includes a host cluster program 112, a host OS (Operating System) 111, a virtualization program (hereinafter also referred to as a virtualization mechanism) 113, and for each guest machine.
  • Application program 152, guest cluster program, and guest OS 150 are examples of guest machines.
  • the functional configuration realized by the host cluster program 112, the host OS (Operating System) 111, and the virtualization program 113 is the host machine 110, the application program 152 prepared for each virtual machine, the guest cluster program, and the guest OS 150.
  • the realized functional configuration is called a guest machine 140.
  • the execution of processing may be described with each program as the subject. This indicates that the processing is executed by the processor 170 executing the program.
  • the save memory section 160 is used as a save destination for memory contents to be described later.
  • the save memory section 160 is outside the memory area used by the host machine and the guest machine, and is reserved in advance when the system is booted.
  • the save memory section 160 may be an external memory (SRAM) instead of the memory mounted in the computer system 10.
  • guest machines 140A and 140B are configured by the virtualization mechanism 113 of the host machine 110, and the save memory partition 160 is provided on the system memory 190.
  • Guest machine A140A and guest machine A140B have the same configuration, and each includes guest OS 150A and guest OS 150B, and application program A 152A and application program B 152B.
  • FIG. 2 shows a detailed configuration example of the host machine 110.
  • the host OS 111 has a probe point management table 120 (details will be described later with reference to FIG. 3) for managing a memory address of a probe point to be inserted into the guest machine A 140A and a scenario number at the time of dumping, which will be described later.
  • Dump scenario management table 121 for managing areas (details will be described later with reference to FIG. 5)
  • dump area management table 122 for managing save memory partition 160 (details will be described later with reference to FIG. 6)
  • dump request bitmap table 123 (details will be described later with reference to FIG. 8)
  • probe handler processing (details will be described later with reference to FIG. 11), and a memory saving fault process 125 for performing dump acquisition (details will be described later with reference to FIG. 12).
  • a program for executing the dump writing process 126 (details will be described later with reference to FIG. 13). Equipped.
  • the host cluster program 112 detects a probe insertion program 130 (details will be described later with reference to FIG. 4) for inserting a probe (also referred to as a probe code) into the guest machine A 140A described above, when a failure occurs in the guest machine A 140A.
  • a guest machine failure detection program 131 is provided.
  • the guest OS 150A executes the probe code inserted into the guest OS 150A by the probe point insertion program 130 described above, and notifies the host machine 110 of the failure from the guest machine A 140A. This is to detect abnormalities.
  • Pattern 2 indicates that when the host machine 110 performs a survival check such as a heartbeat with respect to the guest machine A 140A at a certain interval and the survival check cannot be performed (there is no response from the guest machine A 140A), the host machine 110 An abnormality is detected.
  • a survival check such as a heartbeat with respect to the guest machine A 140A at a certain interval and the survival check cannot be performed (there is no response from the guest machine A 140A)
  • FIG. 3 is a diagram illustrating a configuration example of the probe point management table 120.
  • the probe point management table 120 pairs of probe point addresses and scenario numbers are registered.
  • the probe point address stores a memory address value on the guest machine A140A where the probe is inserted.
  • the probe point is set for each subsystem (virtual functional configuration) of the guest machine.
  • the virtualization mechanism 113 of the host machine 110 has a conversion table between a memory address on the host machine and an address on the guest machine.
  • the host machine 110 executes the probe insertion program 130, the host machine 110 uses the conversion table to convert the probe point address specified in the probe point management table 120 into a memory address on the host machine 110, and then the guest machine A 140A. Insert the probe.
  • the scenario number stores an identification number of a scenario managed by a dump scenario management table 121 described later.
  • the probe point management table 120 stores the probe insertion address and scenario number in advance. After the guest machine A 140A loads the guest OS 150A onto the memory, the guest OS 150A notifies the host OS 111 of the end of loading, and stops operating until a notification is received from the host machine 110.
  • the host OS 111 that has received the notification of completion of loading refers to the probe point management table 120, executes the probe insertion program 130, and performs probe insertion processing. After the probe insertion process is completed, the guest OS 150A resumes operation.
  • the probe insertion process can also be performed on the guest machine A 140A, and the probe insertion program 130 and the dump scenario management table 121 may be provided on the guest OS 150A of the guest machine A 140A. In this case, after the guest machine A 140A loads the guest OS 150A, the probe insertion program 130 is executed to perform the probe insertion process.
  • the guest machine A 140A executes the probe insertion process
  • the guest machine A 140A executes the probe insertion program 130 without stopping the operation of the guest machine A 140A. Therefore, an error occurs until the probe insertion process is completed. Cannot be dumped.
  • the host machine 110 can execute the probe insertion program 130 according to this update, thereby inserting a new probe into the guest machine while the system is operating. I can do it.
  • FIG. 4 is a diagram for explaining processing for inserting a probe in accordance with the description of the probe point management table 120. This process is performed by executing the probe insertion program 130.
  • the probe is inserted on the guest machine by the probe insertion program 130 (S401).
  • the probe point described in the probe point management table 120 is specifically the address address of the memory on the guest machine A 140A managed by the guest OS 150A as described above.
  • the probe insertion program 130 on the host OS 111 converts the probe point from the guest machine address to the host machine address using the host machine address / guest machine address conversion table, and inserts the probe at the address.
  • the address value on the host machine of the probe point is obtained for each guest machine, and the probe is inserted at the obtained address for each guest machine.
  • the insertion process is repeatedly executed until all the probes are inserted (S402).
  • FIG. 5 is a diagram illustrating a configuration example of the dump scenario management table 121.
  • the dump location is information for specifying a memory area that is a dump acquisition target (hereinafter also referred to as a dump target), and at least one or more data in the kernel memory space used by the kernel subsystem in the memory space of the host OS 111 The area is specified as the dump target area.
  • the host machine 110 refers to the probe point management table 120 and obtains a scenario number corresponding to the probe point at which the probe is inserted.
  • the memory area specified by the scenario No. is set as the dump target area.
  • the dump target area is a memory area reserved for the host machine 110.
  • the processing of the guest machine is stopped, but another guest machine configured on the same host machine can continue to operate.
  • the memory area for the host machine 110 is rewritten by the processing of another guest machine that continues to operate, the data stored in the memory for the host machine 110 when the failure occurs cannot be restored. It cannot be used for analysis.
  • the data stored in the area is saved in the save memory. A technique for evacuating to the section 160 is provided.
  • Non-Patent Document 2 kdump (see Non-Patent Document 2), which is a conventional dump technology.
  • the host machine 110 may detect a failure other than the failure of the guest machine A 140A by means other than the execution of the probe by the guest machine A 140A (for example, by the method of pattern 2 described above). In this case, it is desirable to dump all data areas in the kernel memory space used by the kernel subsystem in the memory space of the host machine 110. Therefore, no scenario is prepared as a scenario for this case.
  • the dump target area is the entire data area of the kernel memory space, but the other code areas are excluded from the dump target. This is because the data area is changed by the system operation, and the code area is unchanged.
  • the scenario number is selected depending on which subsystem of the kernel (virtual functional configuration of the guest machine) the bug function (probe code) is executed.
  • a bug function is not always executed and fails. In that case, the host machine 110 cannot know which subsystem the guest machine A 140A has failed during execution. Therefore, even if the host machine 110 detects a failure of the guest OS 150A at a time other than the execution of the probe inserted into the guest OS 150A by the probe insertion program 130, all subsystems use it as “no applicable scenario”. Data area to be dumped.
  • FIG. 6 is a diagram illustrating a configuration example of the dump management area table 122.
  • the dump management area table 112 a dump factor for storing the identification information of the guest machine in which the failure has occurred among a plurality of operating guest machines, and the probe executed when the guest machine 140 notifies the failure are stored.
  • the dump location is equivalent to the dump location of the dump scenario management table 121.
  • the dump destination offset is a value representing a difference from the head address of the save memory partition 160, and data is saved in a memory area after the address indicated by the dump destination offset.
  • the value of the dump destination offset is set so that the address value obtained by adding the data area length represented by the dump location to the address value of the dump destination offset falls within the area of the save memory partition 160.
  • FIG. 7 is a diagram illustrating an example of dump locations in the memory area of the host machine 110 when a failure occurs in the guest machine A 140A.
  • the guest machine A140A executes the probe inserted in the code section (for example, BUG_ON () function used in Linux OS) that is executed when a fatal bug exists in the network subsystem in the kernel space of the guest machine A140A.
  • the dump location will be described using an example in which the host machine 110 detects a failure.
  • the memory area used by the network subsystem of the host machine 110 becomes important. . This is because, for example, when packet transmission or the like is performed from the guest machine A 140A, this processing is performed via the network subsystem of the host machine 110.
  • the memory subsystem is dumped as a dump target location regardless of the subsystem in which the failure has occurred, considering that the memory subsystem is always used.
  • the data area 703a of the network subsystem and the data area 703b of the memory subsystem of the host machine 110 are set as dump target locations.
  • conventional dumping there is no way to dump a specific part of the host machine in response to the faulty part of the guest machine.
  • the useless part is dumped.
  • dump processing has caused the overhead of the entire system.
  • the dump target location can be kept to the minimum necessary, and the overhead due to dump processing can be minimized.
  • FIG. 7 illustrates the case where a failure occurs in the memory area 702 used by the network subsystem of the guest machine, the same applies when a failure occurs in the usage area of another subsystem.
  • FIG. 8 is a diagram illustrating a configuration example of the dump request bitmap table 123.
  • the dump request bit table 123 determines the page numbers (page frame numbers) of all pages used by the host machine 110 and whether each page is requested to be dumped (is a dump acquisition target). Dump request flag information is stored.
  • the page is a unit used by the host machine 110 to manage a memory area used by the host machine. That is, the host machine 110 manages the memory area used by the host machine 110 as a collection of a plurality of pages.
  • the dump request flag indicates whether it is a write-protected state set for acquiring a dump or a write-protected state set for other memory management reasons. Used to judge.
  • the value of the dump request flag is 1 when there is a dump request (when it is a dump acquisition target), and 0 when there is no dump request (when it is not a dump acquisition target).
  • FIG. 9 is a diagram for explaining the processing flow of the entire nonstop dump.
  • the guest machine failure detection program 130 of the host cluster program 112 detects an error in the guest machine A 140A based on the notification from the guest machine A 140A that has executed the probe (S501).
  • the host OS 111 analyzes the failure information provided from the guest machine A 140A and determines whether or not the failure detection is due to the execution of the probe (S502). Specifically, the information notified from the guest machine A140A is the bug code head address in the memory area managed by the guest machine A140A.
  • the host machine 110 that has received this calculates the memory address on the host machine 110 using the conversion table between the memory address on the host machine 110 and the memory address on the guest machine A140A, and which probe is in accordance with the probe point management table 120. Determine if it has been executed. When the determined address does not correspond to any of the probe point management tables 120, it is determined that the dump scenario management table 121 does not correspond.
  • the host OS 111 executes probe handler processing 124, and first identifies which probe was executed on the guest machine A 140A from the failure information.
  • the host OS 111 refers to the dump scenario management table 121 for the dump location (that is, the dump target area) associated with the scenario number managed in the dump scenario management table 121 in association with the probe point of this probe. Identify. Then, the host OS 111 prohibits storage writing in the host machine memory including the specified dump location (S504). Specifically, writing is prohibited for all pages including the specified dump location (dump target area).
  • the entire data area in the memory area used by the host machine 110 is write-protected (S503). Specifically, writing is prohibited for all pages included in the data area.
  • an MMU memory management unit
  • This write request is not issued from the failed guest machine A140A, but issued from another guest machine such as the guest machine B140B.
  • the guest machine A140A in which a normal failure has occurred does not issue a write request because the processing is interrupted after the failure has occurred.
  • other guest machines B140B running on the same host machine 110 as the guest machine A140A can continue the processing regardless of the failure of the guest machine A140A. Therefore, a write request may be issued from the other guest machine B 140B to the host machine memory area.
  • the COW (copy on write) method ensures that the kernel secures a new physical page, stores the data requested to be written here, and maps the area where writing has been performed. Change to correspond to this new physical page.
  • the host OS 111 executes the memory saving fault process 125.
  • the memory saving fault process 125 first, a physical page is secured in the saving memory partition 160, and the data currently stored in the page to be written is saved (S505). After that, the page to be written, which has been set to write-inhibited by the processing of S503 or S504, is changed to writable, and the data of the page is updated according to the write request (S506).
  • the data saved in the save memory partition is data stored in the memory area of the host machine 110 when an error occurs.
  • this data can be used as a dump, the system (and processing of other guest machines) can be performed. A dump can be obtained without stopping.
  • FIG. 10 is a diagram for explaining the error detection method in S501 of FIG. 9 and the flow of the probe handler process 124 that occurs after detection. As a premise of this process, it is assumed that the probe point insertion process of FIG. 4 has already been executed and a probe has been inserted into the guest machine A140A.
  • FIG. 11 is a diagram for explaining the probe handler process 124 executed in S510 of FIG.
  • the moment of entering S510 (that is, the moment when the probe handler process 124 is trajected) is the state where the CPU core executing the guest OS 150A has reached the probe point, that is, in the memory area of the guest OS 150A executing the core. An error has occurred.
  • the probe handler process 124 all the cores other than the core that executed the probe are temporarily put to sleep (S513).
  • scenario identification number scenario No
  • the dump scenario management table 121 the dump location linked to the scenario identification number is specified, the page including this dump location (dump target area) is specified, and this page is write-inhibited.
  • FIG. 12 is a diagram for explaining the details of the memory saving fault process 125.
  • the memory saving fault process 125 is executed. As described above, the write request is issued from a guest machine other than the guest machine in which the failure has occurred.
  • the host OS 111 When there is a write to the write protected area (S516), the host OS 111 refers to the dump request bitmap table 123 and determines whether the dump request flag “1” is set in the write target page (S517). ).
  • the host OS determines that the data stored in the page is a dump target, and saves the data stored in the page to be written The page is saved by copying to the memory partition 160 (S520).
  • the dump area management table 122 is created, and the identification information of the guest machine 140 that executed the probe is registered in “dump factor”, and the identification number of the scenario specified in the above process is registered in “scenario No”. Furthermore, the current time information is “dump time”, the dump source page identification information is “dump location”, and the start address information of the copy destination area (offset from the start address of the save memory partition 160 indicating the start address) Is written as “dump destination offset” (S521).
  • the host OS clears the dump request flag in the dump request bitmap table 123 corresponding to the saved page (“0”) (S522), makes the page writable, and writes to the page.
  • the written contents are reflected by writing the data according to the request (S523).
  • the host OS determines that the page is not a dump target. In this case, the host OS executes normal page fault processing. For example, if the host OS uses an operating system that uses the COW (copy-on-write) method, the data stored in the write-inhibited area is copied to the newly secured page frame and newly secured. The page frame is made writable and data is written (S519).
  • COW copy-on-write
  • FIG. 13 is a diagram for explaining the details of the dump writing process 126 for writing the dump saved in the saving memory partition 160 by the memory saving fault process 124 to the external storage area 200.
  • the dump is written to the external storage device 200 connected using the communication interface 180 provided in the computer system 10.
  • the host OS identifies the scenario number from the dump area management table 122 (S524). Then, the host OS refers to the dump scenario management table 121 and identifies the dump location associated with the scenario No acquired in S524, thereby identifying the page including the dump location (S525).
  • the host OS reads the value of the dump request flag in the dump request bitmap table 123 for the page specified in S525 (S526), and whether the dump request flag is set (that is, whether the value of the flag is “1”). Is determined (S527).
  • a specific area is write-protected, and data stored in the page in the save memory partition 160 is dumped page by page when a write request is made. If there is no write request, the data of the page is not dumped to the save memory partition 160.
  • This process is performed for all pages specified in S525 (S531), and the process ends when data is written to the external storage device 200 for all pages.
  • the data writing destination in the dump writing process 126 is not limited to the external storage device 200 but may be the save memory partition 160. In this case, the processing of S528 is eliminated, and the external storage device 200 of S529 is changed to the save memory partition 160.
  • system configuration uses a virtual environment as an embodiment, but can be applied to a non-virtual environment by replacing a guest machine with a process.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Mathematical Physics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention porte sur un système informatique qui rend possible d'obtenir et de sauvegarder des informations de vidage abondantes comprenant un contenu de mémoire d'un gestionnaire de machine virtuelle lui-même possiblement nécessaire dans l'analyse du problème, sans arrêter le système, lorsqu'un problème survient dans un système d'exploitation fonctionnant sur le gestionnaire de machine virtuelle. Le système informatique, dans lequel une machine invitée fonctionne à l'aide d'un système de virtualisation sur une machine hôte, comprend : une unité de traitement d'insertion de point d'instrumentation pour insérer un point d'instrumentation de la machine hôte à la machine invitée ; une table de gestion de point d'instrumentation pour associer des points d'instrumentation à des scénarios de vidage correspondants ; une table de gestion de scénario de vidage pour limiter des emplacements de vidage pour chaque scénario ; et un programme de détection de problème de machine invitée pour détecter la survenue d'un problème dans la machine invitée. Au moment auquel un problème survient, le contenu de mémoire du gestionnaire de machine virtuelle est vidé sans arrêter le système, et une région de mémoire soumise au vidage est limitée en fonction du type de problème.
PCT/JP2011/001992 2011-04-04 2011-04-04 Système informatique WO2012137239A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/JP2011/001992 WO2012137239A1 (fr) 2011-04-04 2011-04-04 Système informatique

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/JP2011/001992 WO2012137239A1 (fr) 2011-04-04 2011-04-04 Système informatique

Publications (1)

Publication Number Publication Date
WO2012137239A1 true WO2012137239A1 (fr) 2012-10-11

Family

ID=46968690

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2011/001992 WO2012137239A1 (fr) 2011-04-04 2011-04-04 Système informatique

Country Status (1)

Country Link
WO (1) WO2012137239A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014203360A1 (fr) * 2013-06-19 2014-12-24 富士通株式会社 Dispositif de traitement d'informations, procédé de traitement d'informations et programme de traitement d'informations
US10210035B2 (en) 2014-10-08 2019-02-19 Hitachi, Ltd. Computer system and memory dump method
US11663064B1 (en) * 2019-09-02 2023-05-30 Virtuozzo International Gmbh System and method for generating a guest operating system crash dump

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05189254A (ja) * 1992-01-14 1993-07-30 Fujitsu Ltd 仮想計算機の制御情報収集装置および方法
JPH05250194A (ja) * 1992-03-06 1993-09-28 Nec Field Service Ltd サービスプロセッサ
JPH10154087A (ja) * 1996-11-25 1998-06-09 Mitsubishi Electric Corp メモリ内容ダンプ処理方法
JP2001318806A (ja) * 2000-05-11 2001-11-16 Nec Corp プログラムの障害解析データ作成方法
JP2008186378A (ja) * 2007-01-31 2008-08-14 Ipride Co Ltd 例外に対処するためのプログラム

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH05189254A (ja) * 1992-01-14 1993-07-30 Fujitsu Ltd 仮想計算機の制御情報収集装置および方法
JPH05250194A (ja) * 1992-03-06 1993-09-28 Nec Field Service Ltd サービスプロセッサ
JPH10154087A (ja) * 1996-11-25 1998-06-09 Mitsubishi Electric Corp メモリ内容ダンプ処理方法
JP2001318806A (ja) * 2000-05-11 2001-11-16 Nec Corp プログラムの障害解析データ作成方法
JP2008186378A (ja) * 2007-01-31 2008-08-14 Ipride Co Ltd 例外に対処するためのプログラム

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2014203360A1 (fr) * 2013-06-19 2014-12-24 富士通株式会社 Dispositif de traitement d'informations, procédé de traitement d'informations et programme de traitement d'informations
US10210035B2 (en) 2014-10-08 2019-02-19 Hitachi, Ltd. Computer system and memory dump method
US11663064B1 (en) * 2019-09-02 2023-05-30 Virtuozzo International Gmbh System and method for generating a guest operating system crash dump

Similar Documents

Publication Publication Date Title
US10649853B2 (en) Tracking modifications to a virtual machine image that occur during backup of the virtual machine
US9058195B2 (en) Virtual machines failover
US20140181359A1 (en) Information processing apparatus and method of collecting memory dump
JP4783392B2 (ja) 情報処理装置および障害回復方法
US9792208B2 (en) Techniques for logging addresses of high-availability data via a non-blocking channel
US20120304184A1 (en) Multi-core processor system, computer product, and control method
US9519502B2 (en) Virtual machine backup
US10339009B2 (en) System for flagging data modification during a virtual machine backup
US9430382B2 (en) Logging addresses of high-availability data
US8898413B2 (en) Point-in-time copying of virtual storage
US9904567B2 (en) Limited hardware assisted dirty page logging
WO2012137239A1 (fr) Système informatique
US8892838B2 (en) Point-in-time copying of virtual storage and point-in-time dumping
CN115576734B (zh) 一种多核异构日志存储方法和系统
JP6356822B2 (ja) 計算機システム及びメモリダンプ方法
JP5832408B2 (ja) 仮想計算機システム及びその制御方法

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11863005

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11863005

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP