Detecting a guest operating system crash on a virtual computing instance

US10430261B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-10430261-B2
Application numberUS-201715677691-A
CountryUS
Kind codeB2
Filing dateAug 15, 2017
Priority dateAug 15, 2017
Publication dateOct 1, 2019
Grant dateOct 1, 2019

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

The subject matter described herein is generally directed towards detection and remediation of virtual computing instance (VCI) failure on host devices. Monitoring is performed to detect suspected failures of different guest operating systems, identify failure information, and perform remediation to provide high availability for the VCI.

First claim

Opening claim text (preview).

What is claimed is: 1. A system for detecting a guest operating system (OS) crash of a virtual computing instance (VCI), said system comprising: at least one physical processor; and at least one memory comprising computer program code, the at least one memory and the computer program code configured to, with the at least one physical processor, cause the physical processor to at least: detect, by a hypervisor executing on a host, failure of the guest OS of the VCI, the VCI executing on the host in a cluster that has been configured for high availability, wherein detecting comprises: intercepting a command from the guest OS to create a core dump of the guest OS, the guest OS issuing the command in response to failure of the guest OS by intercepting a hypercall from the guest OS to the hypervisor to create a reserved partition in the guest operating system for storage of the core dump, the hypercall occurring when the guest OS crashes, or recognizing failure screen display information generated by the guest OS; in response to detecting the failure of the guest OS, notify a high availability process on the hypervisor; and perform, by the high availability process on the hypervisor, remediation for the VCI. 2. The system of claim 1 , wherein the computer program code is configured to intercept the command from the guest OS to create the core dump by intercepting a command from the guest OS to write the core dump to a file system mounted on the VCI. 3. The system of claim 1 , wherein the computer program code is configured to intercept the command from the guest OS to create the core dump by intercepting a command from the guest OS to write the core dump to firmware. 4. The system of claim 1 , wherein the computer program code is configured to recognize failure screen display information by: detecting a display switch to a video graphics array (VGA) format, the guest OS displaying content in the VGA format; and performing pattern matching by comparing selected portions of the displayed content in the VGA format to known display content that is displayed upon failure of the guest OS to identify a match, the selected portions including strings with values. 5. The system of claim 1 , wherein the computer program code is configured to detect failure of the guest OS by: identifying a guest OS version; and based on the identifying guest OS version, determining whether to intercept the command from the guest OS to create a core dump, or recognize the failure screen display information generated by the guest OS. 6. The system of claim 1 , wherein the computer program code is configured to perform remediation for the VCI by one or more of the following: resetting or powering off the VCI, waiting for the core dump to complete and then resetting or powering off the VCI, and restoring a state of the VCI by reverting the VCI to a previously-saved snapshot of the VCI. 7. A method for detecting a guest operating system (OS) crash of a virtual computing instance (VCI), said method comprising: detecting, by a hypervisor executing on a host, failure of the guest OS of the VCI, the VCI executing on the host in a cluster that has been configured for high availability, wherein detecting comprises: intercepting a command from the guest OS to create a core dump of the guest OS, the guest OS issuing the command in response to failure of the guest OS by intercepting a hypercall from the guest OS to the hypervisor to create a reserved partition in the guest operating system for storage of the core dump, the hypercall occurring when the guest OS crashes, or recognizing failure screen display information generated by the guest OS; in response to detecting the failure of the guest OS, notifying a high availability process on the hypervisor; and performing, by the high availability process on the hypervisor, remediation for the VCI. 8. The method of claim 7 , wherein intercepting a command from the guest OS to create a core dump comprises intercepting a command from the guest OS to write the core dump to a file system mounted on the VCI. 9. The method of claim 7 , wherein intercepting a command from the guest OS to create a core dump comprises intercepting a command from the guest OS to write the core dump to firmware. 10. The method of claim 7 , wherein recognizing failure screen display information comprises: detecting a display switch to a video graphics array (VGA) format, the guest OS displaying content in the VGA format; and performing pattern matching by comparing selected portions of the displayed content in the VGA format to known display content that is displayed upon failure of the guest OS to identify a match, the selected portions including strings with values. 11. The method of claim 7 , wherein detecting failure of the guest OS comprises: identifying a guest OS version; and based on the identifying guest OS version, determining whether to intercept the command from the guest OS to create a core dump, or recognize the failure screen display information generated by the guest OS. 12. The method of claim 7 , wherein performing remediation for the VCI comprises one or more of the following: resetting or powering off the VCI, waiting for the core dump to complete and then resetting or powering off the VCI, and restoring a state of the VCI by reverting the VCI to a previously-saved snapshot of the VCI. 13. One or more non-transitory computer storage media having computer-executable instructions that, upon execution by a processor, cause the processor to at least perform operations comprising: detecting, by a hypervisor executing on a host, failure of the guest OS of the VCI, the VCI executing on the host in a cluster that has been configured for high availability, wherein detecting comprises: intercepting a command from the guest OS to create a core dump of the guest OS, the guest OS issuing the command in response to failure of the guest OS by intercepting a hypercall from the guest OS to the hypervisor to create a reserved partition in the guest operating system for storage of the core dump, the hypercall occurring when the guest OS crashes, or recognizing failure screen display information generated by the guest OS; in response to detecting the failure of the guest OS, notifying a high availability process on the hypervisor; and performing, by the high availability process on the hypervisor, remediation for the VCI. 14. The one or more non-transitory computer storage media of claim 13 , wherein intercepting a command from the guest OS to create a core dump comprises intercepting a hypercall from the guest OS to the hypervisor to create a reserved partition for storage of the core dump, the hypercall occurring when the guest OS crashes. 15. The one or more non-transitory computer storage media of claim 13 , wherein intercepting a command from the guest OS to create a core dump comprises intercepting a command from the guest OS to write the core dump to firmware. 16. The one or more non-transitory computer storage media of claim 13 , wherein recognizing failure screen display information comprises: detecting a display switch to a video graphics array (VGA) format, the guest OS displaying content in the VGA format; and performing pattern matching by comparing selected portions of the displayed content in the VGA format to known display content that is displayed upon failure of the guest OS to identify a match, the selected portions including strings with values. 17. The one or more non-transitory computer storage media of claim 13 , wherein detecting failure of the gu

Assignees

Inventors

Classifications

  • Restarting or rejuvenating · CPC title

  • Guest-host, i.e. hypervisor is an application program itself, e.g. VirtualBox · CPC title

  • in a virtual computing platform, e.g. logically partitioned systems · CPC title

  • Dumping, i.e. gathering error/state information after a fault for later diagnosis · CPC title

  • by exceeding limits · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US10430261B2 cover?
The subject matter described herein is generally directed towards detection and remediation of virtual computing instance (VCI) failure on host devices. Monitoring is performed to detect suspected failures of different guest operating systems, identify failure information, and perform remediation to provide high availability for the VCI.
Who is the assignee on this patent?
Vmware Inc
What technology area does this patent fall under?
Primary CPC classification G06F11/0712. Mapped technology areas include Physics.
When was this patent published?
Publication date Tue Oct 01 2019 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 2 related publications on this page (citations in our corpus or others sharing the same primary CPC).