CN111240898A - Hypervisor-based black box implementation method and system - Google Patents
Hypervisor-based black box implementation method and system Download PDFInfo
- Publication number
- CN111240898A CN111240898A CN202010023263.XA CN202010023263A CN111240898A CN 111240898 A CN111240898 A CN 111240898A CN 202010023263 A CN202010023263 A CN 202010023263A CN 111240898 A CN111240898 A CN 111240898A
- Authority
- CN
- China
- Prior art keywords
- guest
- hypervisor
- black box
- area
- memory
- Prior art date
- Legal status (The legal status 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 status listed.)
- Granted
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/14—Error detection or correction of the data by redundancy in operation
- G06F11/1402—Saving, restoring, recovering or retrying
- G06F11/1415—Saving, restoring, recovering or retrying at system level
- G06F11/1441—Resetting or repowering
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3003—Monitoring arrangements specially adapted to the computing system or computing system component being monitored
- G06F11/3037—Monitoring arrangements specially adapted to the computing system or computing system component being monitored where the computing system component is a memory, e.g. virtual memory, cache
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F11/00—Error detection; Error correction; Monitoring
- G06F11/30—Monitoring
- G06F11/3065—Monitoring arrangements determined by the means or processing involved in reporting the monitored data
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Abstract
The invention discloses a black box implementation method based on Hypervisor, which comprises the following steps: s1: the Hypervisor creates a plurality of Guest OSs according to user configuration, then pre-allocates a memory area for storing black box data for each Guest OS, and records the address information of the memory area; s2: the Hypervisor pre-allocates a block of storage address space for storing the black box on the permanent storage device, and the like. In the invention, after the Guest OS running on the Hypervisor generates abnormal reset, the recording and monitoring functions like a black box are realized, the method is very practical and convenient for troubleshooting the reasons of abnormal generation of each Guest OS in the virtualization system, and has wider coverage and stronger applicability.
Description
Technical Field
The invention belongs to the technical field of computer operating systems, and particularly relates to a black box implementation method and system based on Hypervisor.
Background
Hypervisor, called a Virtual Machine Monitor, is an operating system that runs other operating systems. The Hypervisor runs an intermediate operating system between the physical hardware and the operating system, which allows multiple operating systems and applications to share a set of basic physical hardware, and the operating system running on the Hypervisor is called a Guest operating system (Guest OS).
Since Hypervisor can run a variety of Guest OSs, Guest OSs may employ a multitasking, preemptible operating system like the Linux kernel. For Linux kernel code, the code amount of the Linux kernel code in the 4.20 version reaches 2500 ten thousand lines, the code is huge and cannot be simplified, and once an abnormal breakdown condition occurs, debugging and tracking are difficult to perform.
Hypervisor has been used in the server field before, but with the development of embedded systems, it is considered as the next leading field of embedded systems to solve the problem of the limited resource utilization of embedded systems by increasingly complex application scenarios. The Hypervisor provides flexibility for bearing heterogeneous operating systems on the same multi-core processor, and realizes good reliability and fault control mechanism to ensure the safe separation between key tasks, hard real-time application programs and general-purpose and untrusted user application programs. For example, in the current intelligent cockpit of an automobile, the Hypervisor technology is utilized to simultaneously realize the display of a full liquid crystal instrument and the display of a central control entertainment system on a single board, wherein the full liquid crystal instrument runs on Guest OS which selects Linux or QNX, and the central control entertainment system runs on Guest OS which selects Android.
Currently, a general Guest OS provides a log system in an operating system, such as a logcat of Android or a journal log of linux, and an engineer can perform fault analysis on the Guest OS through the log. In addition, the Guest OS can also configure a serial port through the Hypervisor, and the abnormal debugging information of the Guest OS is printed and output to the serial port in real time, so that the Guest OS state can be checked in real time through the pc access serial port.
In a multi-system environment based on Hypervisor, especially for operating Hypervisor in an embedded system, although abnormal debugging information can be checked through a serial port, since no serial port is accessed in an actual operating environment, such as an intelligent cabin system of an automobile, after the system is mounted, the output of the serial port is removed, and field information of Guest OS at an abnormal moment can not be captured through the serial port. Meanwhile, a log system provided by the Guest OS depends on a storage function provided by an operating system of the Guest OS, and because the kernel of the Guest OS is abnormally crashed, the Guest OS does not have the storage capacity any more at this moment, and the Guest OS log system cannot be used, the scene of the collapse moment of the Guest OS cannot be recorded, and the specific reason of the generation of the abnormity cannot be accurately known. For example, in the running process of an automobile, the Guest OS for displaying the liquid crystal instrument is abnormal, so that the black screen is restarted, the abnormal site cannot be known through the existing means, and the reason for restarting cannot be clearly obtained, so that high difficulty is brought to subsequent fault analysis of engineers. Therefore, if the Guest OS running on the Hypervisor does not have the black box function, the abnormal crash field information of each client operating system cannot be effectively recorded, and the analysis and the investigation of the reasons for the abnormal system are not facilitated.
Therefore, there is a need to provide a black box implementation method and system based on Hypervisor to solve the above problems.
Disclosure of Invention
The invention aims to provide a black box implementation method and system based on Hypervisor, wherein Guest OS running on Hypervisor realizes the same recording and monitoring functions of the black box after abnormal reset is generated, and the black box implementation method and system are very practical and convenient for troubleshooting of reasons of abnormal generation of each Guest OS in a virtualization system, and have wider coverage and stronger applicability.
In order to achieve the purpose, the technical scheme adopted by the invention is as follows:
a black box implementation method based on Hypervisor comprises the following steps:
s1: the Hypervisor creates a plurality of Guest OSs according to user configuration, then pre-allocates a memory area for storing black box data for each Guest OS, and records the address information of the memory area;
s2: the Hypervisor pre-allocates a storage address space for storing the black box on the permanent storage device, the storage address space of the whole black box is partitioned according to the number of Guest OSs, namely one Guest OS corresponds to one storage address space, and each partition is divided into a non-rolling area, a rolling area and an internal storage-transfer storage area according to different stored information; wherein, the non-rolling area records a part of data of Guest OS and can not be covered, and the data is not recorded after the non-rolling area is fully written; the rolling area is rolled to the head part for continuous recording in a circulating recording mode after the data in the recording area is fully written; the memory dump area is used for storing data of Guest OS memory dump;
s3: the Hypervisor starts a Guest OS, enters the Guest OS to run and executes corresponding services; when the Guest OS is in collapse restart, the Hypervisor judges whether the current Guest OS is in abnormal restart according to the flag bit, and if the current Guest OS is in abnormal restart, the site information used when the Guest OS is in abnormal is written into the memory area in the step S1;
s4: the Hypervisor provides a command to inquire the field information and outputs the field information stored in the memory area to a serial port or transmits the field information to a remote server through a network;
s5: the Hypervisor judges whether the field information stored in the memory area in the step S3 needs to be written into the permanent storage device according to the configuration, and if the judgment result is that the field information needs to be written into the permanent storage device, the field information is solidified and written into the non-rolling area of the black box storage address space.
Preferably, the permanent storage device includes one or more of eMMC, SD card, and solid state disk.
Preferably, the field information includes one or more of general purpose registers, system registers, and stacks.
Preferably, the step of writing the Guest OS into the rolling area of the storage address space in real time in step S2 is as follows:
s201: the Guest OS collects data to be recorded, calls a black box data writing interface provided by the Hypervisor, and transmits the data to a black box management system of the Hypervisor;
s202: the Hypervisor black box management system receives the data of Guest OS, finds the black box storage address space corresponding to Guest OS on the permanent storage equipment through Guest OS information, and writes the data into the rolling area of the black box storage address space of the permanent storage equipment;
s203: after the data write is completed, Hypervisor returns to Guest OS to continue running.
Preferably, the method further comprises a Guest OS memory dump step, and the specific content is as follows:
the Guest OS memory is dumped through configuration or commands provided by Hypervisor, the file of Guest OS memory dump is compressed by adopting LZO compression algorithm or LZMA compression algorithm, and after the compression is finished, the data is written into a black box memory dump storage area.
A black box implementation system based on Hypervisor comprises:
memory area allocation device: the system comprises a Hypervisor, a memory area and a data processing module, wherein the Hypervisor is used for pre-allocating a memory area for storing black box data for each Guest OS when the Hypervisor creates a plurality of Guest OSs according to user configuration, and recording address information of the memory area;
the storage address space allocation device: the method comprises the steps that a storage address space for storing a black box is pre-allocated to a permanent storage device by the Hypervisor;
memory address space partitioning means: the device comprises a storage address space, a non-rolling area, a rolling area and an internal storage and transfer storage area, wherein the storage address space of the whole black box is partitioned according to the number of Guest OSs, namely one Guest OS corresponds to one storage address space, and each partition is divided into the non-rolling area, the rolling area and the internal storage and transfer storage area according to different stored information; wherein, the non-rolling area records a part of data of Guest OS and can not be covered, and the data is not recorded after the non-rolling area is fully written; the rolling area is rolled to the head part for continuous recording in a circulating recording mode after the data in the recording area is fully written; the memory dump area is used for storing data of Guest OS memory dump;
an abnormality determination device: when the Guest OS is crashed and restarted, judging whether the current Guest OS is abnormally restarted or not according to the flag bit;
an abnormality information storage device: when the Guest OS is abnormally restarted, writing field information used when the Guest OS is abnormally restarted into the memory area;
an abnormal information inquiry device: inquiring the field information by providing a command through a Hypervisor, and outputting the field information stored in the memory area to a serial port or transmitting the field information to a remote server through a network;
permanent storage device of field information: and judging whether the field information stored in the memory area needs to be written into the permanent storage equipment or not through the Hypervisor according to the configuration, and if the judgment result is that the field information needs to be written into the permanent storage equipment, solidifying and writing the field information into a non-rolling area of a storage address space of the black box.
Preferably, the system further comprises a Guest OS memory dump device: the method is used for dumping Guest OS memory through configuration or commands provided by Hypervisor, compressing files dumped by Guest OS memory by adopting LZO compression algorithm or LZMA compression algorithm, and writing data into a memory transfer storage area in the black box after compression is completed.
The beneficial technical effects of the invention are as follows: for Guest OS running on Hypervisor, after abnormal reset is generated, the recording and monitoring functions like a black box are realized, the method is very practical and convenient for troubleshooting the reasons of abnormal generation of each Guest OS in the virtualization system, and has wider coverage and stronger applicability.
Drawings
FIG. 1 is a flow chart showing steps of embodiment 1 of the present invention.
Fig. 2 is a flow chart illustrating a step of partitioning a memory address space according to embodiment 1 of the present invention.
FIG. 3 is a flowchart illustrating a procedure of writing black box data into a rolling area according to embodiment 1 of the present invention.
Fig. 4 is a schematic structural diagram of embodiment 2 of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to fig. 1 to 4 of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example 1:
as shown in fig. 1, in step 1, Hypervisor creates a Guest operating system (Guest OS) according to user configuration, and then pre-allocates a memory area for storing black box data for each Guest OS, and records address information of the memory area;
and 3, the Hypervisor starts a Guest OS, enters the Guest OS to run and executes corresponding services. The Guest OS is crashed and restarted, for example, the Guest OS kernel accesses an illegal pointer to cause the system to be abnormally restarted, the system exits from the Guest OS to the Hypervisor at the moment, the Hypervisor judges whether the current Guest OS is abnormally restarted or not according to the flag bit, if the current Guest OS is abnormally restarted, and field information such as a general register, a system register, a stack and the like used when the Guest OS is abnormal is written into the memory address space in the step 1;
step 4, the Hypervisor provides a command to inquire fault information, and outputs the abnormal information stored in the memory address space to a serial port or transmits the abnormal information to a remote server through a network for an engineer to perform fault tracking analysis;
and 5, the Hypervisor judges whether the abnormal field information stored in the memory in the step 3 needs to be written into a permanent storage device (such as an eMMC, an SD card, a solid state disk and the like) according to the configuration, and the abnormal field information is solidified on a local storage device to prevent the fault information from being incapable of being inquired after power failure. For scenes which are not easy to protect the field environment or scenes which do not have debugging access to the field environment, such as the fact that serial ports cannot be accessed to check printing information, and the solidification of abnormal field information to the local is favorable for analyzing and tracking problems, the abnormal field information is very critical and needs to be solidified and written into a non-rolling area of a black box of the storage device;
step 6, Hypervisor provides a memory dump function for Guest OS, Guest OS memory is dumped through configuration or a command provided by Hypervisor, the file size of Guest OS memory dump is equal to the total amount of memory used by Guest OS under the condition of no compression, the file size of Guest OS memory dump is considered to be larger, LZO compression algorithm or LZMA compression algorithm can be adopted to compress the file of Guest OS memory dump, data are written into a black box memory transfer storage area after the compression is completed, and therefore a development engineer can take out corresponding dump data from the black box memory transfer storage area and perform abnormal analysis by using corresponding tools (such as GDB, Crash);
in addition, the invention also provides a set of black box data writing interface in the Hypervisor, which is used for Guest OS to write the key data into the rolling area of the black box in real time through the interface, as shown in FIG. 3.
and 2, the Hypervisor black box management system receives the data of the Guest OS, finds a black box storage area corresponding to the Guest OS on the permanent storage equipment through Guest OS information, and writes the data into a rolling area of the black box on the storage equipment.
And 3, after the data writing is finished, returning the Hypervisor to the Guest OS for continuous operation.
Example 2:
as shown in fig. 4, a black box implementation system based on Hypervisor includes:
memory area allocation device: the system comprises a Hypervisor, a memory area and a data processing module, wherein the Hypervisor is used for pre-allocating a memory area for storing black box data for each Guest OS when the Hypervisor creates a plurality of Guest OSs according to user configuration, and recording address information of the memory area;
the storage address space allocation device: the method comprises the steps that a storage address space for storing a black box is pre-allocated to a permanent storage device by the Hypervisor;
memory address space partitioning means: the device comprises a storage address space, a non-rolling area, a rolling area and an internal storage and transfer storage area, wherein the storage address space of the whole black box is partitioned according to the number of Guest OSs, namely one Guest OS corresponds to one storage address space, and each partition is divided into the non-rolling area, the rolling area and the internal storage and transfer storage area according to different stored information; wherein, the non-rolling area records a part of data of Guest OS and can not be covered, and the data is not recorded after the non-rolling area is fully written; the rolling area is rolled to the head part for continuous recording in a circulating recording mode after the data in the recording area is fully written; the memory dump area is used for storing data of Guest OS memory dump;
an abnormality determination device: when the Guest OS is crashed and restarted, judging whether the current Guest OS is abnormally restarted or not according to the flag bit;
an abnormality information storage device: when the Guest OS is abnormally restarted, writing field information used when the Guest OS is abnormally restarted into the memory area;
an abnormal information inquiry device: inquiring the field information by providing a command through a Hypervisor, and outputting the field information stored in the memory area to a serial port or transmitting the field information to a remote server through a network;
permanent storage device of field information: and judging whether the field information stored in the memory area needs to be written into the permanent storage equipment or not through the Hypervisor according to the configuration, and if the judgment result is that the field information needs to be written into the permanent storage equipment, solidifying and writing the field information into a non-rolling area of a storage address space of the black box.
Preferably, the system further comprises a Guest OS memory dump device: the method is used for dumping Guest OS memory through configuration or commands provided by Hypervisor, compressing files dumped by Guest OS memory by adopting LZO compression algorithm or LZMA compression algorithm, and writing data into a memory transfer storage area in the black box after compression is completed.
Claims (7)
1. A black box implementation method based on Hypervisor is characterized by comprising the following steps:
s1: the Hypervisor creates a plurality of Guest OSs according to user configuration, then pre-allocates a memory area for storing black box data for each Guest OS, and records the address information of the memory area;
s2: the Hypervisor pre-allocates a storage address space for storing the black box on the permanent storage device, the storage address space of the whole black box is partitioned according to the number of Guest OSs, namely one Guest OS corresponds to one storage address space, and each partition is divided into a non-rolling area, a rolling area and an internal storage-transfer storage area according to different stored information; wherein, the non-rolling area records a part of data of Guest OS and can not be covered, and the data is not recorded after the non-rolling area is fully written; the rolling area is rolled to the head part for continuous recording in a circulating recording mode after the data in the recording area is fully written; the memory dump area is used for storing data of Guest OS memory dump;
s3: the Hypervisor starts a Guest OS, enters the Guest OS to run and executes corresponding services; when the Guest OS is crashed and restarted, the Hypervisor judges whether the current Guest OS is abnormally restarted or not according to the flag bit, and if the current Guest OS is abnormally restarted, the site information used when the Guest OS is abnormal is written into the memory area in the step S1;
s4: the Hypervisor provides a command to inquire the field information and outputs the field information stored in the memory area to a serial port or transmits the field information to a remote server through a network;
s5: the Hypervisor judges whether the field information stored in the memory area in the step S3 needs to be written into the permanent storage device according to the configuration, and if the judgment result is that the field information needs to be written into the permanent storage device, the field information is solidified and written into the non-rolling area of the storage address space of the black box.
2. The Hypervisor-based black box implementation method of claim 1, wherein the persistent storage device comprises one or more of an eMMC, an SD card, and a solid state disk.
3. The Hypervisor-based black box implementation method of claim 1, wherein the field information comprises one or more of general purpose registers, system registers, and stacks.
4. The black box implementation method based on Hypervisor of claim 1, wherein the step of writing the Guest OS into the rolling area of the storage address space in real time in step S2 is as follows:
s201: the Guest OS collects data to be recorded, calls a black box data writing interface provided by the Hypervisor, and transmits the data to a black box management system of the Hypervisor;
s202: the Hypervisor black box management system receives the data of Guest OS, finds the black box storage address space corresponding to Guest OS on the permanent storage equipment through Guest OS information, and writes the data into the rolling area of the black box storage address space of the permanent storage equipment;
s203: after the data write is completed, Hypervisor returns to Guest OS to continue running.
5. The black box implementation method based on Hypervisor according to any one of claims 1 to 4, further comprising a Guest OS memory dump step, which specifically comprises the following contents:
the Guest OS memory is dumped through configuration or commands provided by Hypervisor, the file dumped by the Guest OS memory is compressed by adopting an LZO compression algorithm or an LZMA compression algorithm, and after the compression is finished, the data is written into a memory transfer storage area in the black box.
6. A black box implementation system based on Hypervisor is characterized by comprising:
memory area allocation device: the system comprises a Hypervisor, a memory area and a data processing module, wherein the memory area is used for pre-allocating a memory area for storing black box data for each Guest OS when the Hypervisor creates a plurality of Guest OSs according to user configuration, and recording address information of the memory area;
the storage address space allocation device: the method comprises the steps that a storage address space for storing a black box is pre-allocated on a permanent storage device by the Hypervisor;
memory address space partitioning means: the device comprises a storage address space, a non-rolling area, a rolling area and a memory transfer storage area, wherein the storage address space of the whole black box is partitioned according to the number of Guest OSs, namely one Guest OS corresponds to one storage address space, and each partition is divided into the non-rolling area, the rolling area and the memory transfer storage area according to different stored information; wherein, the non-rolling area records a part of data of Guest OS and can not be covered, and the data is not recorded after the non-rolling area is fully written; the rolling area is rolled to the head part for continuous recording in a circulating recording mode after the data in the recording area is fully written; the memory dump area is used for storing data of Guest OS memory dump;
an abnormality determination device: when the Guest OS is crashed and restarted, judging whether the current Guest OS is abnormally restarted or not according to the flag bit;
an abnormality information storage device: when the Guest OS is abnormally restarted, writing field information used when the Guest OS is abnormally restarted into the memory area;
an abnormal information inquiry device: inquiring the field information by providing a command through a Hypervisor, and outputting the field information stored in the memory area to a serial port or transmitting the field information to a remote server through a network;
permanent storage device of field information: and judging whether the field information stored in the memory area needs to be written into the permanent storage equipment or not through the Hypervisor according to the configuration, and if so, solidifying and writing the field information into a non-rolling area of the storage address space of the black box.
7. The Hypervisor-based black box implementation system according to claim 6, further comprising a Guest OS memory dump device: the method is used for dumping the Guest OS memory through configuration or a command provided by Hypervisor, compressing a file dumped by the Guest OS memory by adopting an LZO compression algorithm or an LZMA compression algorithm, and writing data into a memory transfer storage area in the black box after compression is completed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010023263.XA CN111240898B (en) | 2020-01-09 | 2020-01-09 | Method and system for realizing black box based on Hypervisor |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010023263.XA CN111240898B (en) | 2020-01-09 | 2020-01-09 | Method and system for realizing black box based on Hypervisor |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111240898A true CN111240898A (en) | 2020-06-05 |
| CN111240898B CN111240898B (en) | 2023-08-15 |
Family
ID=70864963
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010023263.XA Active CN111240898B (en) | 2020-01-09 | 2020-01-09 | Method and system for realizing black box based on Hypervisor |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111240898B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297029A (en) * | 2021-04-21 | 2021-08-24 | 惠州市德赛西威智能交通技术研究院有限公司 | QNX end operation information management system and method for dual-system intelligent cockpit |
Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101042681A (en) * | 2006-03-23 | 2007-09-26 | 联想(北京)有限公司 | Digital data transparency protected safety read-write system and method |
| CN102243571A (en) * | 2011-07-08 | 2011-11-16 | 西安交通大学 | Embedded Hypervisor-oriented multi-window display virtual operation method |
| CN102799480A (en) * | 2012-06-21 | 2012-11-28 | 华为技术有限公司 | Method and device for closing interrupt in virtualization system |
| CN104331359A (en) * | 2014-11-03 | 2015-02-04 | 大唐移动通信设备有限公司 | Recording method and device of abnormal information |
| US20150058580A1 (en) * | 2012-04-03 | 2015-02-26 | Google Inc. | Method and system for memory oversubscription for virtual machines |
| CN104463492A (en) * | 2014-12-23 | 2015-03-25 | 国家电网公司 | Operation management method of electric power system cloud simulation platform |
| CN104899111A (en) * | 2015-06-09 | 2015-09-09 | 烽火通信科技股份有限公司 | Method and system for dealing with kernel panic of home gateway system |
| US20160055097A1 (en) * | 2014-08-19 | 2016-02-25 | Yang Seok KI | Heterogeneous unified memory |
| CN106569904A (en) * | 2015-10-09 | 2017-04-19 | 中兴通讯股份有限公司 | Information storage method and device and server |
| CN106844008A (en) * | 2017-01-03 | 2017-06-13 | 华为技术有限公司 | A kind of method of data manipulation, equipment and system |
| CN107450962A (en) * | 2017-07-03 | 2017-12-08 | 北京东土科技股份有限公司 | Abnormality eliminating method, apparatus and system under a kind of virtualization running environment |
| CN108073507A (en) * | 2016-11-17 | 2018-05-25 | 联芯科技有限公司 | A kind of processing method and processing device of Kernel Panic field data |
| CN108228308A (en) * | 2016-12-21 | 2018-06-29 | 中国电信股份有限公司 | The monitoring method and device of virtual machine |
| CN108549591A (en) * | 2018-03-02 | 2018-09-18 | 烽火通信科技股份有限公司 | A kind of black box device and its implementation of embedded system |
| CN109144669A (en) * | 2018-08-15 | 2019-01-04 | 郑州云海信息技术有限公司 | The method for testing pressure and system of NAS virtual machine system under a kind of MCS system |
| CN109271206A (en) * | 2018-08-24 | 2019-01-25 | 晶晨半导体(上海)股份有限公司 | A kind of memory compression and store method that exception is live |
| CN109284178A (en) * | 2017-07-21 | 2019-01-29 | 中兴通讯股份有限公司 | A kind of interruption transmitting method and device based on KVM virtualization |
-
2020
- 2020-01-09 CN CN202010023263.XA patent/CN111240898B/en active Active
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101042681A (en) * | 2006-03-23 | 2007-09-26 | 联想(北京)有限公司 | Digital data transparency protected safety read-write system and method |
| CN102243571A (en) * | 2011-07-08 | 2011-11-16 | 西安交通大学 | Embedded Hypervisor-oriented multi-window display virtual operation method |
| US20150058580A1 (en) * | 2012-04-03 | 2015-02-26 | Google Inc. | Method and system for memory oversubscription for virtual machines |
| CN102799480A (en) * | 2012-06-21 | 2012-11-28 | 华为技术有限公司 | Method and device for closing interrupt in virtualization system |
| US20160055097A1 (en) * | 2014-08-19 | 2016-02-25 | Yang Seok KI | Heterogeneous unified memory |
| CN104331359A (en) * | 2014-11-03 | 2015-02-04 | 大唐移动通信设备有限公司 | Recording method and device of abnormal information |
| CN104463492A (en) * | 2014-12-23 | 2015-03-25 | 国家电网公司 | Operation management method of electric power system cloud simulation platform |
| CN104899111A (en) * | 2015-06-09 | 2015-09-09 | 烽火通信科技股份有限公司 | Method and system for dealing with kernel panic of home gateway system |
| CN106569904A (en) * | 2015-10-09 | 2017-04-19 | 中兴通讯股份有限公司 | Information storage method and device and server |
| CN108073507A (en) * | 2016-11-17 | 2018-05-25 | 联芯科技有限公司 | A kind of processing method and processing device of Kernel Panic field data |
| CN108228308A (en) * | 2016-12-21 | 2018-06-29 | 中国电信股份有限公司 | The monitoring method and device of virtual machine |
| CN106844008A (en) * | 2017-01-03 | 2017-06-13 | 华为技术有限公司 | A kind of method of data manipulation, equipment and system |
| CN107450962A (en) * | 2017-07-03 | 2017-12-08 | 北京东土科技股份有限公司 | Abnormality eliminating method, apparatus and system under a kind of virtualization running environment |
| CN109284178A (en) * | 2017-07-21 | 2019-01-29 | 中兴通讯股份有限公司 | A kind of interruption transmitting method and device based on KVM virtualization |
| CN108549591A (en) * | 2018-03-02 | 2018-09-18 | 烽火通信科技股份有限公司 | A kind of black box device and its implementation of embedded system |
| CN109144669A (en) * | 2018-08-15 | 2019-01-04 | 郑州云海信息技术有限公司 | The method for testing pressure and system of NAS virtual machine system under a kind of MCS system |
| CN109271206A (en) * | 2018-08-24 | 2019-01-25 | 晶晨半导体(上海)股份有限公司 | A kind of memory compression and store method that exception is live |
Non-Patent Citations (1)
| Title |
|---|
| 王皓: "基于异步检查点的动态软件升级系统", 《中国优秀硕士学位论文全文数据库 信息科技辑》, no. 12, pages 138 - 99 * |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113297029A (en) * | 2021-04-21 | 2021-08-24 | 惠州市德赛西威智能交通技术研究院有限公司 | QNX end operation information management system and method for dual-system intelligent cockpit |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111240898B (en) | 2023-08-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| TWI544328B (en) | Method and system for probe insertion via background virtual machine | |
| US10275168B2 (en) | Providing service address space for diagnostics collection | |
| CN111158945B (en) | Kernel fault processing method, device, network security equipment and readable storage medium | |
| CN114595038A (en) | Data processing method, computing device and computer storage medium | |
| CN107368384A (en) | A kind of Linux server abnormal information dump system and method | |
| CN116594796A (en) | Process crash information collection method and device based on eBPF | |
| CN116340053A (en) | Log processing method, device, computer equipment and medium for system crash | |
| EP3534259B1 (en) | Computer and method for storing state and event log relevant for fault diagnosis | |
| CN111240898A (en) | Hypervisor-based black box implementation method and system | |
| CN110764962A (en) | Log processing method and device | |
| CN107249129A (en) | A kind of automatic service kit of set top box | |
| CN111858116A (en) | Information recording method, device, equipment and readable storage medium | |
| CN101751283A (en) | Virtual machine monitor, virtual machine system and client operation system state acquiring method | |
| CN115391106A (en) | Method, system and device for pooling backup resources | |
| CN113986599A (en) | Application processing method, terminal, server, equipment and storage medium | |
| CN107688479A (en) | Android system network cluster and its method built, the method and system of android system network cluster data processing | |
| CN115202803A (en) | Fault processing method and device | |
| CN116932334B (en) | Abnormal reset monitoring method and device for multi-core micro control unit | |
| CN116414722B (en) | Fuzzy test processing method and device, fuzzy test system and storage medium | |
| CN112527192B (en) | Data acquisition method and device and service equipment | |
| CN113094221B (en) | Fault injection method, device, computer equipment and readable storage medium | |
| JP7183841B2 (en) | electronic controller | |
| CN113468020A (en) | Memory monitoring method and device, electronic equipment and computer readable storage medium | |
| CN116954820A (en) | Dump file management method, device, computer equipment and storage medium | |
| CN117971554A (en) | Memory data processing method and computing device |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| CB02 | Change of applicant information | ||
| CB02 | Change of applicant information |
Address after: Room 404-412, 4th Floor, Block B, Building 4, No. 200 Tianfu Fifth Street, High tech Zone, Chengdu, Sichuan, 610041 Applicant after: Zhongling Zhixing (Chengdu) Technology Co.,Ltd. Address before: No. 4, 3rd Floor, Unit 1, Building 2, No. 81 Tuoxin East Street, High tech Zone, Chengdu, Sichuan, 610000 Applicant before: Zhongling Zhixing (Chengdu) Technology Co.,Ltd. |
|
| GR01 | Patent grant | ||
| GR01 | Patent grant |