Applying firmware updates in a system with zero downtime by selectively offlining and onlining hardware using a scale-up hypervisor layer
First Claim
1. A method comprising:
- running a scale-up hypervisor on a server complex including at least one server;
running a single operating system and at least one application on top of the scale-up hypervisor;
identifying a firmware update available for a first hardware component within the server complex;
the scale-up hypervisor removing all workload from the first hardware component; and
applying the identified firmware update to the first hardware component while the first hardware component is idle and the hypervisor continues running the single operating system and the at least one application.
2 Assignments
0 Petitions
Accused Products
Abstract
A method includes running a scale-up hypervisor on a server complex including at least one server and running a single operating system and at least one application on top of the scale-up hypervisor. The method further includes identifying a firmware update available for a first hardware component within the server complex. The scale-up hypervisor removes all workload from the first hardware component, and the identified firmware update is applied to the first hardware component while the first hardware component is idle and the hypervisor continues running the single operating system and the at least one application. Preferably, the method may be used to sequentially apply firmware updates to various hardware components across the plurality of servers without ever shutting down the entire plurality of servers.
-
Citations
20 Claims
-
1. A method comprising:
-
running a scale-up hypervisor on a server complex including at least one server; running a single operating system and at least one application on top of the scale-up hypervisor; identifying a firmware update available for a first hardware component within the server complex; the scale-up hypervisor removing all workload from the first hardware component; and applying the identified firmware update to the first hardware component while the first hardware component is idle and the hypervisor continues running the single operating system and the at least one application. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20)
-
Specification