# US 2012/0254667 A1 · Performing network core dump without drivers

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2012/0254667 A1
- Document ID: US20120254667A1
- Status: Published application
- Kind: A1
- Application number: 13/078,156
- Filed: 2011-04-01
- Published: 2012-10-04
- Earliest claimed: 2011-04-01
- Assignees: VMware, Inc.
- Inventors: Ronghua ZHANG; Saleem ABDULRASOOL; Mallik MAHALINGAM; Boon Seong ANG
- Web page: https://patentgrep.com/patent/US20120254667A1

## CPC

- G06F 11/0778: {Dumping, i.e. gathering error/state information after a fault for later diagnosis}
- G06F 11/0748: {in a remote unit communicating with a single-box computer node experiencing an error/fault (remote testing G06F11/2294)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Core dump is performed over a network without relying on network device drivers. Instead of network device drivers, firmware of network devices that is typically used during boot is preserved in memory post-boot, and one or more application program interfaces of the firmware are invoked to perform the network core dump. For ease of implementation, a network bootstrap program that has standard application program interfaces for calling into the firmware of network devices may be invoked when performing core dump over the network.

## Claims

### Claim 1

A method of transferring diagnostic data for a computing device over a network using a network device, comprising:
prior to loading of system software for the computing device into memory, loading application programming interfaces (APIs) for the network device into a protected memory region, the contents of which are preserved after booting of the system software and after execution control of the computing device has been transferred to the system software; and
after booting of the system software and after the execution control of the computing device has been transferred to the system software, invoking at least one of the APIs to transfer the diagnostic data over the network using the network device.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
receiving a network bootstrap program using the APIs through the network device;
storing the network bootstrap program in the protected memory region;
retrieving the system software from a network boot server using the network bootstrap program;
loading the system software into another memory region; and
transferring execution control of the computing device to the system software.

### Claim 3 (depends on 1)

The method of claim 1, further comprising:
determining that a condition for transferring the diagnostic data over the network is met; and
copying one or more portions of the diagnostic data from a first memory region that is not accessible by the network bootstrap program to a second memory region that is accessible by the network bootstrap program,
wherein the one or more APIs are invoked by the network bootstrap program to transfer the diagnostic data stored in the second memory region over the network.

### Claim 4 (depends on 3)

The method of claim 3, wherein the condition for transferring the diagnostic data over the network is an error in the system software.

### Claim 5 (depends on 1)

The method of claim 1, further comprising:
determining an error condition in the system software; and
resetting the network device,
wherein the one or more APIs are invoked by the network bootstrap program to transfer the diagnostic data stored in the second memory region over the network.

### Claim 6 (depends on 1)

The method of claim 1, wherein the contents of the protected memory region are preserved by excluding mappings to the protected memory region in page tables maintained by the system software, and disallowing direct memory accesses into the protected memory region.

### Claim 7 (depends on 1)

The method of claim 1, wherein the system software includes a kernel of an operating system.

### Claim 8 (depends on 1)

The method of claim 1, wherein the system software includes a kernel of hypervisor.

### Claim 9

A non-transitory computer readable storage medium comprising instructions for causing a computer device to carry out a method that includes the steps of:
prior to loading of system software for the computing device into memory, loading application programming interfaces (APIs) for the network device into a protected memory region, the contents of which are preserved after booting of the system software and after execution control of the computing device has been transferred to the system software; and
after booting of the system software and after the execution control of the computing device has been transferred to the system software, invoking one or more APIs to transfer the diagnostic data over the network using the network device.

### Claim 10 (depends on 9)

The non-transitory computer readable storage medium of claim 9, wherein the method further includes the steps of:
receiving a network bootstrap program using the APIs through the network device;
storing the network bootstrap program in the protected memory region;
retrieving the system software from a network boot server using the network bootstrap program;
loading the system software into another memory region; and
transferring execution control of the computing device to the system software.

### Claim 11 (depends on 9)

The non-transitory computer readable storage medium of claim 9, wherein the method further includes the steps of:
determining that a condition for transferring the diagnostic data over the network is met; and
copying one or more portions of the diagnostic data from a first memory region that is not accessible by the network bootstrap program to a second memory region that is accessible by the network bootstrap program,
wherein the one or more APIs are invoked by the network bootstrap program to transfer the diagnostic data stored in the second memory region over the network.

### Claim 12 (depends on 11)

The non-transitory computer readable storage medium of claim 11, wherein the condition for transferring the diagnostic data over the network is an error in the system software.

### Claim 13 (depends on 9)

The non-transitory computer readable storage medium of claim 9, wherein the method further includes the steps of:
determining an error condition in the system software; and
resetting the network device,
wherein the one or more APIs are invoked by the network bootstrap program to transfer the diagnostic data stored in the second memory region over the network.

### Claim 14 (depends on 9)

The non-transitory computer readable storage medium of claim 9, wherein the contents of the protected memory region are preserved by excluding mappings to the protected memory region in page tables maintained by the system software, and disallowing direct memory accesses into the protected memory region.

### Claim 15 (depends on 9)

The non-transitory computer readable storage medium of claim 9, wherein the system software includes a kernel of an operating system.

### Claim 16 (depends on 9)

The non-transitory computer readable storage medium of claim 9, wherein the system software includes a kernel of hypervisor.

### Claim 17

A computing device having one or more applications being executed therein on top of system software for the computing device, the computing device comprising:
a processing unit under control of the system software that is executing instructions from the one or more applications;
a network device having firmware stored therein; and
a system memory having stored therein a copy of the firmware of the network device.

### Claim 18 (depends on 17)

The computing device of claim 17, wherein the system memory further has stored therein a copy of a network bootstrap program that includes application programming interfaces that call into the firmware of the network device.

### Claim 19 (depends on 18)

The computing device of claim 18, wherein the network bootstrap program includes instructions for carrying out a network boot according to a PXE standard.

### Claim 20 (depends on 19)

The computing device of claim 19, wherein the firmware of the network device includes universal network device interface application programming interfaces.

### Claim 21 (depends on 18)

The computing device of claim 18, wherein a memory region of the system memory in which the copy of the firmware of the network device and the network bootstrap program are stored, are addressable by the processing mode operating in a real mode.

### Claim 22 (depends on 21)

The computing device of claim 21, wherein the processing unit is programmed to prohibit memory mappings to said memory region and direct memory accesses into said memory region.

### Claim 23 (depends on 18)

The computing device of claim 18, wherein the processing unit is programmed to carry out a network dump using the copy of the firmware of the network device and the network bootstrap program when the system software abnormally terminates.

### Claim 24 (depends on 17)

The computing device of claim 17, wherein the system software is an operating system.

### Claim 25 (depends on 17)

The computing device of claim 17, wherein the system software is a hypervisor and the one or more applications are virtual machines.
