[go: up one dir, main page]

CN111240898B - Method and system for realizing black box based on Hypervisor - Google Patents

Method and system for realizing black box based on Hypervisor Download PDF

Info

Publication number
CN111240898B
CN111240898B CN202010023263.XA CN202010023263A CN111240898B CN 111240898 B CN111240898 B CN 111240898B CN 202010023263 A CN202010023263 A CN 202010023263A CN 111240898 B CN111240898 B CN 111240898B
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.)
Active
Application number
CN202010023263.XA
Other languages
Chinese (zh)
Other versions
CN111240898A (en
Inventor
请求不公布姓名
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Zhongling Zhixing Chengdu Technology Co ltd
Original Assignee
Zhongling Zhixing Chengdu Technology Co ltd
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 Zhongling Zhixing Chengdu Technology Co ltd filed Critical Zhongling Zhixing Chengdu Technology Co ltd
Priority to CN202010023263.XA priority Critical patent/CN111240898B/en
Publication of CN111240898A publication Critical patent/CN111240898A/en
Application granted granted Critical
Publication of CN111240898B publication Critical patent/CN111240898B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/07Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/14Error detection or correction of the data by redundancy in operation
    • G06F11/1402Saving, restoring, recovering or retrying
    • G06F11/1415Saving, restoring, recovering or retrying at system level
    • G06F11/1441Resetting or repowering
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3003Monitoring arrangements specially adapted to the computing system or computing system component being monitored
    • G06F11/3037Monitoring 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
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00Error detection; Error correction; Monitoring
    • G06F11/30Monitoring
    • G06F11/3065Monitoring arrangements determined by the means or processing involved in reporting the monitored data
    • YGENERAL 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
    • Y02TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02DCLIMATE 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/00Energy efficient computing, e.g. low power processors, power management or thermal management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Quality & Reliability (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Computing Systems (AREA)
  • Mathematical Physics (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The invention discloses a black box implementation method based on hypervisors, which comprises the following steps: s1: creating a plurality of Guest OSs by the Hypervisor according to user configuration, pre-distributing a memory area for storing black box data for each Guest OS, and recording address information of the memory area; s2: hypervisor pre-allocates a block of memory address space on persistent storage for storing black boxes, etc. In the invention, for the Guest OS running on the Hypervisor, after abnormal reset is generated, the recording and monitoring functions like the black box are realized, and the method is very practical and convenient for checking the reasons of abnormal generation of each Guest OS in the virtualization system, and has wider coverage and stronger applicability.

Description

Method and system for realizing black box based on Hypervisor
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 a Hypervisor.
Background
Hypervisor, called virtual machine monitor (Virtual Machine Monitor), is an operating system running other operating systems. Hypervisor runs an intermediate layer of operating systems between the physical hardware and the operating system, allowing multiple operating systems and applications to share a set of underlying physical hardware, and the operating system running on top of Hypervisor is referred to as the Guest operating system (Guest OS).
Since multiple Guest OSs may be running on the Hypervisor, guest OSs may employ a multitasking, preemptible operating system such as a Linux kernel. For Linux kernel code, the code quantity of version 4.20 reaches 2500 ten thousand lines, the code is huge and cannot be simplified, and once an abnormal crash condition occurs, debugging and tracking are difficult to carry out.
Hypervisor has been used in the server field before, but with the development of embedded systems, it is considered as the next leading edge field of embedded systems to solve the difficulty in deciding on the utilization of limited resources of embedded systems in increasingly complex application scenarios. Hypervisor provides flexibility to carry heterogeneous operating systems on the same multi-core processor, while it in turn enables good reliability and failure control mechanisms to ensure secure separation between mission-critical, hard real-time applications and general-purpose, untrusted user applications. For example, the intelligent cabin of the current automobile utilizes the Hypervisor technology to 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 operates on a Guest OS selected for Linux or QNX, and the central control entertainment system operates on the Guest OS selected for Android.
At present, general Guest OS can provide log systems, such as log cat of Android or journ logs of linux system, in the operating system, and engineers can perform fault analysis on the Guest OS system through the logs. In addition, the Guest OS can also configure a serial port through the Hypervisor to print out the abnormal debugging information of the Guest OS 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 multisystem environment based on Hypervisor, especially for operating Hypervisor under an embedded system, although abnormal debugging information can be checked through a serial port, because a serial port, such as an intelligent cabin system of an automobile, is not accessed in an actual operating environment, after the system is on-board, serial port output is removed, and therefore field information of abnormal time of a Guest OS cannot be captured through the serial port. Meanwhile, the log system provided by the Guest OS depends on the storage function provided by the Guest OS self operating system, and the Guest OS kernel is abnormally crashed, so that the Guest OS cannot be used at the moment and the site at the time of the Guest OS crash cannot be recorded, and the specific reason for generating the abnormality cannot be accurately known. For example, in the running process of an automobile, the abnormal Guest OS for displaying the liquid crystal instrument causes the restart of a black screen, the acquisition abnormal site cannot be known by the existing means, and the restart reason cannot be clearly acquired, so that the subsequent failure analysis of engineers is very difficult. 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 investigation of the reasons for the system abnormality are not facilitated.
Therefore, there is a strong need to provide a black box implementation method and system based on hypervisors to solve the above problems.
Disclosure of Invention
The invention aims to provide a black box implementation method and a system based on a Hypervisor, wherein a Guest OS running on the Hypervisor realizes the same recording and monitoring functions of the black box after abnormal reset is generated, and is very practical and convenient for checking the reasons of abnormality of each Guest OS in a virtualization system, and has wider coverage and stronger applicability.
In order to achieve the above purpose, the technical scheme adopted by the invention is as follows:
a black box implementation method based on hypervisors comprises the following steps:
s1: creating a plurality of Guest OSs by the Hypervisor according to user configuration, pre-distributing a memory area for storing black box data for each Guest OS, and recording address information of the memory area;
s2: the method comprises the steps that a storage address space of a black box is pre-allocated on a permanent storage device by a Hypervisor, the storage address space of the whole black box is partitioned according to the number of Guest OS, namely one Guest OS corresponds to one storage address space, and each partition is divided into a non-rolling area, a rolling area and a memory transfer area according to different stored information; the non-rolling area records a part of data of the Guest OS, can not be covered, and is not recorded after being fully written; the rolling area is rolled to the head to continue recording after the data of the recording area is fully written in a circulating recording mode; the memory dump area is used for storing data of the Guest OS memory dump;
s3: the Hypervisor starts the Guest OS, enters the Guest OS to run and execute corresponding business; judging whether the current Guest OS is abnormally restarted or not by the Hypervisor according to the flag bit, if so, writing the field information used when the Guest OS is abnormally restarted 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: and judging whether the field information stored in the memory area in the step S3 needs to be written to the permanent storage equipment according to the configuration by the Hypervisor, and if the judgment result shows that the field information needs to be written to the permanent storage equipment, solidifying and writing the field information into a non-rolling area of a black box storage address space.
Preferably, the permanent storage device comprises 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, in step S2, the step of writing the data of the Guest OS into the scrolling region of the storage address space in real time is as follows:
s201: the Guest OS gathers the data to be recorded, calls the black box data writing interface provided by the Hypervisor, and transmits the data to the black box management system of the Hypervisor;
s202: the Hypervisor black box management system receives data of the Guest OS, finds a black box storage address space corresponding to the Guest OS on the permanent storage device through the Guest OS information, and writes the data into a rolling area of the black box storage address space of the permanent storage device;
s203: after the data writing is completed, returning the Hypervisor to the Guest OS to continue running.
Preferably, the method further comprises a Guest OS memory dump step, and the specific contents are as follows:
through configuration or commands provided by hypervisors, the Guest OS memory is dumped, an LZO compression algorithm or an LZMA compression algorithm is adopted to compress files of the Guest OS memory dump, and after compression is completed, data are written into a black box memory transfer area.
A Hypervisor-based black box implementation system, comprising:
memory area allocation means: when the Hypervisor creates a plurality of Guest OSs according to user configuration, pre-distributing a memory area for storing black box data for each Guest OS, and recording address information of the memory area;
memory address space allocation means: the storage address space of a block storage black box is preallocated on the permanent storage device by the Hypervisor;
storage address space partitioning means: 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 a memory transfer area according to different stored information; the non-rolling area records a part of data of the Guest OS, can not be covered, and is not recorded after being fully written; the rolling area is rolled to the head to continue recording after the data of the recording area is fully written in a circulating recording mode; the memory dump area is used for storing data of the Guest OS memory dump;
abnormality determination means: 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 the field information used when the Guest OS is abnormally started into the memory area;
abnormality information inquiry device: inquiring the field information through a Hypervisor providing command, 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 the field information: judging whether the field information stored in the memory area needs to be written to the permanent storage equipment or not according to the configuration by using the Hypervisor, and if the judging result shows that the field information needs to be written to the permanent storage equipment, solidifying and writing the field information into a non-rolling area of a black box storage address space.
Preferably, the method further comprises a Guest OS memory dump device: the method comprises the steps of dumping a Guest OS memory through a command provided by configuration or Hypervisor, compressing files of the Guest OS memory dump by adopting an LZO compression algorithm or an LZMA compression algorithm, and writing data into a black box memory transfer area after compression is completed.
The beneficial technical effects of the invention are as follows: for the Guest OS running on the 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 checking the reasons for abnormal generation of each Guest OS in a virtualization system, and has wider coverage and stronger applicability, the labor cost is higher, meanwhile, the existence time of accumulated water in a track section is reduced, and the occurrence of track construction safety accidents is indirectly reduced.
Drawings
Fig. 1 shows a schematic flow chart of the steps of embodiment 1 of the present invention.
FIG. 2 is a flow chart showing the steps of partitioning a memory address space according to embodiment 1 of the present invention.
Fig. 3 is a flowchart showing a black box data writing procedure of embodiment 1 of the present invention.
Fig. 4 shows a schematic structural diagram of embodiment 2 of the present invention.
Detailed Description
The following description of the embodiments of the present invention will be made more fully with reference to the accompanying drawings 1-4, in which it is evident that the embodiments described are only some, but not all embodiments of the invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
Example 1:
as shown in fig. 1, step 1, creating a client operating system (Guest OS) by using a hypervisor according to user configuration, then pre-allocating a memory area for storing black box data for each Guest OS, and recording address information of the memory area;
and 2, pre-distributing a block of storage address space for storing the black box in a permanent storage device (such as an eMMC (enhanced memory card), an SD (secure digital memory card), a solid state disk and the like) by the Hypervisor, and laying out the storage address space in a mode of FIG. 2, wherein the whole storage address area of the black box is partitioned according to the number of Guest OS (operating system), and each partition is divided into a non-rolling area, a rolling area and a memory transfer area according to the stored information. The non-rolling area records the most critical data of the Guest OS, cannot be covered, and is not recorded after being fully written; the rolling area is rolled to the head to continue recording after the data of the recording area is fully written in a circulating recording mode; the memory dump area is used for storing data of the Guest OS memory dump;
and 3, starting the Guest OS by the Hypervisor, entering the Guest OS to run and executing corresponding services. If the Guest OS is abnormally restarted, the general register, the system register, the stack and other field information used when the Guest OS is abnormal are written into the memory address space in the step 1;
step 4, providing command query fault information by the Hypervisor, outputting the abnormal information stored in the memory address space to a serial port or transmitting the abnormal information to a remote server through a network for carrying out fault tracking analysis by an engineer;
and 5, judging whether the abnormal field information stored in the memory in the step 3 needs to be written into permanent storage equipment (such as an eMMC, an SD card, a solid state disk and the like) according to the configuration by the Hypervisor, and solidifying the abnormal field information onto the local storage equipment to prevent failure information from being inquired after power failure. For scenes which are not easy to protect the field environment or scenes which are not provided with debugging access in the field environment, for example, a serial port cannot be accessed to view printing information, the problem analysis and tracking are locally facilitated by solidifying abnormal field information, and the abnormal field information is required to be solidified and written into a non-rolling area of a storage device black box due to the fact that the abnormal field information is critical;
step 6, providing a storage dumping function of the Guest OS by the Hypervisor, dumping the Guest OS through a command provided by configuration or Hypervisor, and under the condition that compression is not performed, the file size of the storage dumping of the Guest OS is equal to the total amount of the memory used by the Guest OS, considering that the file of the storage dumping of the Guest OS is relatively large, compressing the file of the storage dumping of the Guest OS by adopting an LZO compression algorithm or an LZMA compression algorithm, and writing data into a black box memory transfer storage area after compression is completed, so that a development engineer can take out corresponding dump data from the black box memory dump area and perform anomaly analysis by using corresponding tools (such as GDB and Crash);
in addition, the invention also provides a set of black box data writing interface in the Hypervisor, which is used for the Guest OS to write the key data of the Guest OS into the rolling area of the black box in real time through the interface, as shown in figure 3.
Step 1, a Guest OS gathers key data to be recorded, calls a black box data writing interface provided by a Hypervisor and transmits the data to a black box management system of the Hypervisor;
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 device through the Guest OS information, and writes the data into a rolling area of the black box on the storage device.
And step 3, returning the Hypervisor to the Guest OS to continue running after the data writing is completed.
Example 2:
as shown in fig. 4, a black box implementation system based on hypervisors includes:
memory area allocation means: when the Hypervisor creates a plurality of Guest OSs according to user configuration, pre-distributing a memory area for storing black box data for each Guest OS, and recording address information of the memory area;
memory address space allocation means: the storage address space of a block storage black box is preallocated on the permanent storage device by the Hypervisor;
storage address space partitioning means: 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 a memory transfer area according to different stored information; the non-rolling area records a part of data of the Guest OS, can not be covered, and is not recorded after being fully written; the rolling area is rolled to the head to continue recording after the data of the recording area is fully written in a circulating recording mode; the memory dump area is used for storing data of the Guest OS memory dump;
abnormality determination means: 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 the field information used when the Guest OS is abnormally started into the memory area;
abnormality information inquiry device: inquiring the field information through a Hypervisor providing command, 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 the field information: judging whether the field information stored in the memory area needs to be written to the permanent storage equipment or not according to the configuration by using the Hypervisor, and if the judging result shows that the field information needs to be written to the permanent storage equipment, solidifying and writing the field information into a non-rolling area of a black box storage address space.
Preferably, the method further comprises a Guest OS memory dump device: the method comprises the steps of dumping a Guest OS memory through a command provided by configuration or Hypervisor, compressing files of the Guest OS memory dump by adopting an LZO compression algorithm or an LZMA compression algorithm, and writing data into a black box memory transfer area after compression is completed.

Claims (5)

1. The black box implementation method based on the Hypervisor is characterized by comprising the following steps of:
s1: creating a plurality of Guest OSs by the Hypervisor according to user configuration, pre-distributing a memory area for storing black box data for each Guest OS, and recording address information of the memory area;
s2: the method comprises the steps that a storage address space of a black box is pre-allocated on a permanent storage device by a Hypervisor, 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 a memory transfer area according to different stored information; wherein, the non-rolling area records a part of data of GuestOS and can not be covered, and the data is not recorded after being written up; the rolling area is rolled to the head to continue recording after the data of the recording area is fully written in a circulating recording mode; the memory dump area is used for storing data of GuestOS memory dump;
s3: the Hypervisor starts Guest OS, enters Guest OS to run and execute corresponding business; judging whether the current Guest OS is abnormally restarted or not by the Hypervisor according to the flag bit, if so, writing the field information used when the Guest OS is abnormally restarted 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: judging whether the field information stored in the memory area in the step S3 needs to be written to the permanent storage equipment or not by the Hypervisor according to the configuration, and if the judgment result shows that the field information needs to be written to the permanent storage equipment, solidifying and writing the field information into a non-rolling area of a black box storage address space;
the permanent storage equipment comprises one or more of eMMC, SD card and solid state disk;
the field information includes one or more of general purpose registers, system registers, and stacks.
2. The black box implementation method based on hypervisors of claim 1, wherein the step of the guetosos writing the own data into the scrolling region of the storage address space in real time in step S2 is as follows:
s201: guest OS gathers the data to be recorded, calls the black box data writing interface provided by Hypervisor, and sends the data to the storage device
The data is transmitted to a black box management system of the Hypervisor;
s202: the Hypervisor black box management system receives data of Guest OS, finds a black box storage address space corresponding to Guest OS on the permanent storage device through Guest OS information, and writes the data into a rolling area of the black box storage address space of the permanent storage device;
s203: after the data writing is completed, returning the Hypervisor to Guest OS to continue running.
3. The black box implementation method based on hypervisors according to any one of claims 1-2, further comprising a gueastos memory dump step, which specifically comprises the following steps:
through configuration or commands provided by hypervisors, the Guest OS memory is dumped, an LZO compression algorithm or an LZMA compression algorithm is adopted to compress files of the Guest OS memory dump, and after compression is completed, data are written into a black box memory transfer area.
4. A Hypervisor-based black box implementation system, comprising:
memory area allocation means: when the Hypervisor creates a plurality of Guest OSs according to user configuration, pre-distributing a memory area for storing black box data for each Guest OS, and recording address information of the memory area;
memory address space allocation means: the storage address space of a block storage black box is preallocated on the permanent storage device by the Hypervisor; storage address space partitioning means: the storage address space of the whole black box is partitioned according to the quantity 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 a memory transfer area according to different stored information; wherein, the non-rolling area records a part of data of GuestOS and can not be covered, and the data is not recorded after being written up; the rolling area is rolled to the head to continue recording after the data of the recording area is fully written in a circulating recording mode; the memory dump area is used for storing data of GuestOS memory dump;
abnormality determination means: the Hypervisor starts Guest OS, enters Guest OS to run and execute corresponding business, when Guest OS crashes and restarts, judging whether the current Guest OS is abnormally restarted or not according to the flag bit;
an abnormality information storage device: when Guest OS is abnormally restarted, writing the field information used when Guest OS is abnormal into the memory area;
abnormality information inquiry device: inquiring the field information through a Hypervisor providing command, 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 the field information: judging whether the field information stored in the memory area needs to be written to the permanent storage equipment or not according to the configuration by using the Hypervisor, and if the judging result shows that the field information needs to be written to the permanent storage equipment, solidifying and writing the field information into a non-rolling area of a black box storage address space;
the permanent storage equipment comprises one or more of eMMC, SD card and solid state disk;
the field information includes one or more of general purpose registers, system registers, and stacks.
5. The Hypervisor-based black box implementation system of claim 4, further comprising guetosos memory dump means: the method is used for dumping the Guest OS memory through a command provided by configuration or Hypervisor, compressing files of the Guest OS memory dump by adopting an LZO compression algorithm or an LZMA compression algorithm, and writing data into a black box memory transfer area after compression is completed.
CN202010023263.XA 2020-01-09 2020-01-09 Method and system for realizing black box based on Hypervisor Active CN111240898B (en)

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 CN111240898A (en) 2020-06-05
CN111240898B true 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)

Families Citing this family (3)

* Cited by examiner, † Cited by third party
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
CN113505055A (en) * 2021-04-22 2021-10-15 惠州市德赛西威智能交通技术研究院有限公司 Method and system for conveniently and rapidly capturing log based on Android system
CN113961308B (en) * 2021-10-20 2024-11-12 中瓴智行(成都)科技有限公司 A method and system for implementing peripheral debugging based on Hypervisor

Citations (15)

* Cited by examiner, † Cited by third party
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
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
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

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9501224B2 (en) * 2012-04-03 2016-11-22 Goolge Inc. Method and system for memory oversubscription for virtual machines
US9792227B2 (en) * 2014-08-19 2017-10-17 Samsung Electronics Co., Ltd. Heterogeneous unified memory

Patent Citations (15)

* Cited by examiner, † Cited by third party
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
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)

* Cited by examiner, † Cited by third party
Title
基于异步检查点的动态软件升级系统;王皓;《中国优秀硕士学位论文全文数据库 信息科技辑》(第12期);第I138-99页 *

Also Published As

Publication number Publication date
CN111240898A (en) 2020-06-05

Similar Documents

Publication Publication Date Title
CN111240898B (en) Method and system for realizing black box based on Hypervisor
US7627728B1 (en) System and method for efficient generation of application snapshots
US7433898B1 (en) Methods and apparatus for shared storage journaling
US9396093B1 (en) Virtual execution environment for software delivery and feedback
CN104767643A (en) Disaster recovery backup system based on virtual machine
CN103793258A (en) Hypervisor-based server duplication system and method
US12360709B2 (en) Distributed storage space management method, computing device and storage medium
CN114595038A (en) Data processing method, computing device and computer storage medium
US20200356460A1 (en) Storage-based log file management
CN111198832B (en) Processing method and electronic equipment
CN107368384A (en) A kind of Linux server abnormal information dump system and method
CN103246591B (en) Method and device for signal processing
CN110781133B (en) ROW snapshot method, system, equipment and computer readable storage medium
CN113986599B (en) Application processing method, terminal, server, device and storage medium
JP7183841B2 (en) electronic controller
KR102274668B1 (en) Apparatus and method for controlling updating software of AVN system in vehicle
CN114780208A (en) Method, system, device and storage medium for verifying backup validity of multi-platform virtual machine
CN119311471A (en) Data backup method and device
CN116932334B (en) Abnormal reset monitoring method and device for multi-core micro control unit
JP2007133544A (en) Failure information analysis method and apparatus for implementing the same
CN101751283A (en) Virtual machine monitor, virtual machine system and client operation system state acquiring method
CN107688479A (en) Android system network cluster and its method built, the method and system of android system network cluster data processing
CN111143117A (en) Data storage method and device
CN111435302A (en) Application processing method and device
CN115391106A (en) Method, system and device for pooling backup resources

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