Abstract: An image of a virtualization software and firmware in a plurality of hosts are upgraded by: retrieving metadata of a base image based on a first input that specifies a version of the base image, metadata of an add-on image based on a second input that specifies a server of an original equipment manufacturer (OEM) in which the virtualization software is to be installed, and metadata of drivers and agents based on a third input that specifies a firmware package for the server of the OEM; validating a desired image of the virtualization software by extracting dependencies and conflicts defined in metadata of all payloads of the desired image of the virtualization software, and confirming there are no violations of the extracted dependencies and conflicts; and upgrading the current image of the virtualization software to the desired image and upgrading the current version of the firmware to the desired version.

Abstract: Techniques that enable a hypervisor to (1) maintain shared memory pages and (2) handle memory accounting for VMs that are suspended to and resumed from the volatile memory of a host system are provided. Regarding (1), the hypervisor can maintain shared memory pages in volatile memory across the suspend-to-memory and resume-from-memory operations, without having to save their reference counts. Regarding (2), the hypervisor can keep track of the volatile memory reserved and consumed by VMs as they are suspended and resumed, without erroneously double counting that memory.

Abstract: An example method of hypervisor lifecycle management in a virtualized computing system having a cluster of hosts is described. The method includes: obtaining, by remediation software executing in a host of the hosts, a host state document from a distributed key-value store, the host state document defining a desired state of software in the host, the software including a hypervisor; and performing, by the remediation software in coordination with other hosts of the hosts through the distributed key-value store, a lifecycle operation on the software of the host in response to determining that a current state of the software does not match the desired state.

Abstract: TPM attestation for soft reboots is described herein. One embodiment includes instructions to receive a request to perform a soft reboot of a computing device executing an existing OS instance and having a TPM, and perform a soft reboot process on the computing device responsive to receiving the request. The soft reboot process can include loading a new kernel and boot modules associated with a new OS instance into a memory of the computing device, measuring the boot modules into PCRs of the TPM, generating entries in an event log of the TPM corresponding to the boot modules and the new kernel, exporting the event log and a metadata file associated with the existing OS instance to storage, importing the event log from storage to the new kernel, copying the metadata file from storage to a server, and storing a new metadata file created from manifests of the new OS instance at the server.

Abstract: The disclosure provides an approach for a non-disruptive system upgrade. Embodiments include installing an upgraded version of an operating system (OS) on a computing system while a current version of the OS continues to run. Embodiments include entering a maintenance mode on the computing system, including preventing the addition of new applications and modifying the handling of storage operations on the computing system for the duration of the maintenance mode. Embodiments include, during the maintenance mode, configuring the upgraded version of the OS. Embodiments include, after configuring the upgraded version of the OS, suspending a subset of applications running on the computing system, transferring control over resources of the computing system to the upgraded version of the OS, and resuming the subset of the applications running on the computing system. Embodiments include exiting the maintenance mode on the computing system.

Abstract: An image of a virtualization software and firmware in a plurality of hosts are upgraded by: retrieving metadata of a base image based on a first input that specifies a version of the base image, metadata of an add-on image based on a second input that specifies a server of an original equipment manufacturer (OEM) in which the virtualization software is to be installed, and metadata of drivers and agents based on a third input that specifies a firmware package for the server of the OEM; validating a desired image of the virtualization software by extracting dependencies and conflicts defined in metadata of all payloads of the desired image of the virtualization software, and confirming there are no violations of the extracted dependencies and conflicts; and upgrading the current image of the virtualization software to the desired image and upgrading the current version of the firmware to the desired version.

Abstract: Systems and methods are described for improved error logging during system boot and shutdown. A hardware initialization firmware on a computing device can include a logging module. When errors occur during early system booting or late system shutdown, the firmware can create error logs. The logging module can receive the error logs and prioritize them according to a set of rules. The logging module can select error logs of the highest priority up to a predetermined maximum amount. The logging module can modify the error logs using a shorthand form and write them to nonvolatile random-access memory. The firmware can initialize runtime services and launch an operating system. A system logger on the operating system can retrieve the error logs, save them to a file, and erase them from the memory.

Abstract: The disclosure provides an approach for a non-disruptive system upgrade. Embodiments include installing an upgraded version of an operating system (OS) on a computing system while a current version of the OS continues to run. Embodiments include entering a maintenance mode on the computing system, including preventing the addition of new applications and modifying the handling of storage operations on the computing system for the duration of the maintenance mode. Embodiments include, during the maintenance mode, configuring the upgraded version of the OS. Embodiments include, after configuring the upgraded version of the OS, suspending a subset of applications running on the computing system, transferring control over resources of the computing system to the upgraded version of the OS, and resuming the subset of the applications running on the computing system. Embodiments include exiting the maintenance mode on the computing system.

Abstract: An image of a virtualization software and firmware in a plurality of hosts are upgraded by performing the steps of: validating a desired image of the virtualization software by extracting dependencies and conflicts defined in metadata of all payloads of the desired image of the virtualization software, and confirming there are no violations of the extracted dependencies and conflicts; performing a pre-check of the desired image of the virtualization software against a current image of the virtualization software and a pre-check of the desired version of the firmware against a current version of the firmware; and upon determining from results of the pre-check that the virtualization software can be upgraded to the desired image and the firmware can be upgraded to the desired version, upgrading the current image of the virtualization software to the desired image and upgrading the current version of the firmware to the desired version.

Abstract: A method of restarting execution of a virtual machine (VM) on a host, after an upgrade of a virtualization software for the VM, wherein prior to the upgrade, page mapping data for mapping memory pages of the VM to first page frames located in a first region of a physical memory of the host was copied into second page frames located in a second region of the physical memory of the host includes the steps of: restarting execution of the VM on the host after the upgrade while the page mapping data for mapping the memory pages of the VM to the first page frames, are stored in the second page frames; and during said execution of the VM after the upgrade, copying a portion of the page mapping data stored in the second page frames into a third page frame located in the first region of the physical memory.

Abstract: The disclosure provides an approach for a non-disruptive system upgrade. Embodiments include installing an upgraded version of an operating system (OS) on a computing system while a current version of the OS continues to run. Embodiments include entering a maintenance mode on the computing system, including preventing the addition of new applications and modifying the handling of storage operations on the computing system for the duration of the maintenance mode. Embodiments include, during the maintenance mode, configuring the upgraded version of the OS. Embodiments include, after configuring the upgraded version of the OS, suspending a subset of applications running on the computing system, transferring control over resources of the computing system to the upgraded version of the OS, and resuming the subset of the applications running on the computing system. Embodiments include exiting the maintenance mode on the computing system.

Abstract: Examples described herein include systems and methods for retaining information about bad memory pages across an operating system reboot. An example method includes detecting, by a first instance of an operating system, an error in a memory page of a non-transitory storage medium of a computing device executing the operating system. The operating system can tag the memory page as a bad memory page, indicating that the memory page should not be used by the operating system. The operating system can also store tag information indicating memory pages of the storage medium that are tagged as bad memory pages. The example method can also include receiving an instruction to reboot the operating system, booting a second instance of the operating system, and providing the tag information to the second instance of the operating system. The operating system can use the tag information to avoid using the bad memory pages.

Abstract: The disclosure provides an approach for a non-disruptive system upgrade. Embodiments include installing an upgraded version of an operating system (OS) on a computing system while a current version of the OS continues to run. Embodiments include entering a maintenance mode on the computing system, including preventing the addition of new applications and modifying the handling of storage operations on the computing system for the duration of the maintenance mode. Embodiments include, during the maintenance mode, configuring the upgraded version of the OS. Embodiments include, after configuring the upgraded version of the OS, suspending a subset of applications running on the computing system, transferring control over resources of the computing system to the upgraded version of the OS, and resuming the subset of the applications running on the computing system. Embodiments include exiting the maintenance mode on the computing system.

Abstract: Techniques that enable a hypervisor to (1) maintain shared memory pages and (2) handle memory accounting for VMs that are suspended to and resumed from the volatile memory of a host system are provided. Regarding (1), the hypervisor can maintain shared memory pages in volatile memory across the suspend-to-memory and resume-from-memory operations, without having to save their reference counts. Regarding (2), the hypervisor can keep track of the volatile memory reserved and consumed by VMs as they are suspended and resumed, without erroneously double counting that memory.

Abstract: Techniques that enable a hypervisor to (1) maintain shared memory pages and (2) handle memory accounting for VMs that are suspended to and resumed from the volatile memory of a host system are provided. Regarding (1), the hypervisor can maintain shared memory pages in volatile memory across the suspend-to-memory and resume-from-memory operations, without having to save their reference counts. Regarding (2), the hypervisor can keep track of the volatile memory reserved and consumed by VMs as they are suspended and resumed, without erroneously double counting that memory.

Abstract: An example method of hypervisor lifecycle management in a virtualized computing system having a cluster of hosts is described. The method includes: obtaining, by remediation software executing in a host of the hosts, a host state document from a distributed key-value store, the host state document defining a desired state of software in the host, the software including a hypervisor; and performing, by the remediation software in coordination with other hosts of the hosts through the distributed key-value store, a lifecycle operation on the software of the host in response to determining that a current state of the software does not match the desired state.

Abstract: The disclosure provides an approach for a non-disruptive system upgrade. Embodiments include installing an upgraded version of an operating system (OS) on a computing system while a current version of the OS continues to run. Embodiments include entering a maintenance mode on the computing system, including preventing the addition of new applications and modifying the handling of storage operations on the computing system for the duration of the maintenance mode. Embodiments include, during the maintenance mode, configuring the upgraded version of the OS. Embodiments include, after configuring the upgraded version of the OS, suspending a subset of applications running on the computing system, transferring control over resources of the computing system to the upgraded version of the OS, and resuming the subset of the applications running on the computing system. Embodiments include exiting the maintenance mode on the computing system.

Abstract: An example method of managing a lifecycle of virtualization software in a host is described. The method includes: obtaining, by an initiator in a current version of the virtualization software, a software installation bundle (SIB) from an image repository for a target version of the virtualization software, the SIB including a patcher; verifying, by the initiator, authenticity of the SIB; mounting at least one payload of the SIB in a root filesystem of the virtualization software, and initiating, by the initiator, the patcher in the at least one payload as mounted to perform at least one check operation.

Abstract: Systems and methods are described for improved error logging during system boot and shutdown. A hardware initialization firmware on a computing device can include a logging module. When errors occur during early system booting or late system shutdown, the firmware can create error logs. The logging module can receive the error logs and prioritize them according to a set of rules. The logging module can select error logs of the highest priority up to a predetermined maximum amount. The logging module can modify the error logs using a shorthand form and write them to nonvolatile random-access memory. The firmware can initialize runtime services and launch an operating system. A system logger on the operating system can retrieve the error logs, save them to a file, and erase them from the memory.

Abstract: An example method of managing a lifecycle of virtualization software in a host is described. The method includes: obtaining, by an initiator in a current version of the virtualization software, a software installation bundle (SIB) from an image repository for a target version of the virtualization software, the SIB including a patcher; verifying, by the initiator, authenticity of the SIB; mounting at least one payload of the SIB in a root filesystem of the virtualization software, and initiating, by the initiator, the patcher in the at least one payload as mounted to perform at least one check operation.