Lines Matching full:hibernation
9 Hibernation is sometimes called suspend-to-disk, as it writes a memory
11 state. Upon resume from hibernation, the hardware is restarted and the
13 where it left off. See the "Hibernation" section of
16 Hibernation is usually done on devices with a single user, such as a
17 personal laptop. For example, the laptop goes into hibernation when
19 Hibernation and resume happen on the same hardware, and Linux kernel
20 code orchestrating the hibernation steps assumes that the hardware
23 Hibernation can be initiated within Linux by writing "disk" to
29 Considerations for Guest VM Hibernation
36 running might also be hibernated using hibernation functionality in
37 the Windows host, host hibernation and its impact on guest VMs is not
42 configuration between the hibernation and resume. Even when the resume
52 hibernation to succeed after such a move, there are challenges. See
61 done when resuming execution in the hibernation image. If a VM is
63 model or Hyper-V version, settings recorded in the hibernation image
65 mismatches when resuming the hibernation image, undefined behavior
69 Enabling Guest VM Hibernation
71 Hibernation of a Hyper-V guest VM is disabled by default because
72 hibernation is incompatible with memory hot-add, as provided by the
75 resumes from hibernation, Hyper-V gives the VM only the originally
78 To enable a Hyper-V VM for hibernation, the Hyper-V administrator must
84 prioritizes Linux hibernation in the VM over hot-add, so the Hyper-V
87 enablement is also visible in /sys/bus/vmbus/hibernation. See function
91 guest VM hibernation is not available on Hyper-V for arm64.
93 Initiating Guest VM Hibernation
95 Guest VMs can self-initiate hibernation using the standard Linux
104 hibernation.
106 Handling VMBus Devices During Hibernation & Resume
110 Linux orchestration of hibernation and of resuming from hibernation.
114 hibernation image. This approach allows any state associated with the
115 device to be persisted across the hibernation/resume. When the VM
117 the data structures that already exist in the resumed hibernation
122 Documentation/virt/hyperv/vmbus.rst.) Upon resume from hibernation,
125 hibernation. Having the same class/instance GUIDs allows the offered
127 the memory of the now resumed hibernation image. If any devices are
130 primary VMBus channels that exist in the resumed hibernation image are
141 VMBus sub-channels are not persisted in the hibernation image. Each
143 prior to hibernation. Closing a sub-channel causes Hyper-V to send a
154 hibernation. The guest can't force closing the host end of the socket,
159 "restore" phases. See the "Entering Hibernation" section of
163 Detailed Hibernation Sequence
166 hibernation by freezing user space processes and allocating
167 memory to hold the hibernation image.
175 4. Linux PM disables non-boot CPUs, creates the hibernation image in
177 The hibernation image contains the memory data structures for the
190 hibernation image from memory to disk.
195 S4. Hibernation is now complete.
202 involve hibernation.
203 2. Linux PM hibernation code reads swap space is to find and read
204 the hibernation image into memory. If there is no hibernation
206 3. If this is a resume from hibernation, the "freeze" phase is used
209 and 3 in the hibernation sequence.
211 read-in hibernation image. In the now-running hibernation image,
214 from the hibernation sequence. The top-level VMBus connection is
218 6. Linux PM exits the hibernation resume sequence and the VM is now
219 running normally from the hibernation image.
228 phase of hibernation, so the hibernation image contains the re-created
249 hibernation first handles DDA devices as VMBus devices in order to
251 devices using the hibernation functions implemented by their native
261 rebooted, as happens in Steps 3 and 5 in the Detailed Hibernation
272 suspend and resume operations needed for hibernation. If a VMBus
285 hibernation image must work in that new VM.
290 would cause the resume from hibernation to fail, so several things are
317 from hibernation on a newly created VM. Consequently, Azure does
318 not support hibernation for VMs that have DDA devices such as
320 VF from the VM before it hibernates so that the hibernation image
323 that is present in the hibernation image. Because Azure must
324 remove any VFs before initiating hibernation, Azure VM
325 hibernation must be initiated externally from the Azure Portal or
327 tell Linux to do the hibernation. If hibernation is self-initiated
328 within the Azure VM, VFs remain in the hibernation image, and are
333 hibernation to work for most general-purpose Azure VMs sizes. While