| /qemu/docs/system/ |
| H A D | vm-templating.rst | 1 QEMU VM templating
4 This document explains how to use VM templating in QEMU.
6 For now, the focus is on VM memory aspects, and not about how to save and
7 restore other VM state (i.e., migrate-to-file with ``x-ignore-shared``).
12 With VM templating, a single template VM serves as the starting point for
16 Conceptually, the VM state is frozen, to then be used as a basis for new
18 new VMs are able to read template VM memory; however, any modifications
19 stay private and don't modify the original template VM or any other
20 created VM.
25 When effectively cloning VMs by VM templating, hardware identifiers
[all …]
|
| H A D | images.rst | 38 VM snapshots
41 VM snapshots are snapshots of the complete virtual machine including CPU
43 order to use VM snapshots, you must have at least one non removable and
47 Use the monitor command ``savevm`` to create a new VM snapshot or
51 Use ``loadvm`` to restore a VM snapshot and ``delvm`` to remove a VM
58 ID TAG VM SIZE DATE VM CLOCK
63 A VM snapshot is made of a VM state info (its size is shown in
64 ``info snapshots``) and a snapshot of every writable disk image. The VM
74 you can always make VM snapshots, but they are deleted as soon as you
77 VM snapshots currently have the following known limitations:
|
| H A D | managed-startup.rst | 4 In system mode emulation, it's possible to create a VM in a paused
7 to execute VM code but VCPU threads are not executing any code. The VM
13 code loaded by QEMU in the VM's RAM and with incoming migration
19 allowing VM code to run.
22 that affect initial VM creation (like: ``-smp``/``-m``/``-numa`` ...) or
24 allows pausing QEMU before the initial VM creation, in a "preconfig" state,
|
| H A D | barrier.rst | 8 there is no way to provide the keyboard and mouse inputs to the VM
30 -object input-barrier,id=barrier0,name=VM-1
32 where VM-1 is the name the display configured in the Barrier server
44 (qemu) object_add input-barrier,id=barrier0,name=VM-1
|
| H A D | replay.rst | 23 the memory, state of the hardware devices, clocks, and screen of the VM.
74 from HDD or memory of the VM). Saving only non-deterministic events makes
81 simulated hardware, memory of VM, software interrupts, and execution of
118 New VM snapshots may be created in replay mode. They can be used later
119 to recover the desired VM state. All VM states created in replay mode
121 After recovering the VM state replay will start from that position.
149 for storing VM snapshots. Here is the example of the command line for this:
157 for VM snapshots only.
|
| H A D | monitor.rst | 12 - Freeze/unfreeze the Virtual Machine (VM) and save or restore its
15 - Inspect the VM state without an external debugger.
|
| /qemu/docs/system/i386/ |
| H A D | nitro-enclave.rst | 11 for cryptographic attestation. The parent instance VM always has CID 3 while
12 the enclave VM gets a dynamic CID. Enclaves use an EIF (`Enclave Image Format`_)
45 Running a nitro-enclave VM
50 VM to the host machine and the forward-listen (port numbers separated by '+') is used
51 for forwarding connections from the host machine to the enclave VM::
58 Now run the necessary applications on the host machine so that the nitro-enclave VM
59 applications' vsock communication works. For example, the nitro-enclave VM's init
61 parent VM know that it booted expecting a heartbeat (0xB7) response. So you must run
63 after it receives the heartbeat for enclave VM to boot successfully. You should run all
65 VM for successful communication with the enclave VM.
[all …]
|
| H A D | microvm.rst | 63 ``virtio-mmio`` as its transport, a microvm-based VM needs to be run
67 Running a microvm-based VM
71 legacy and non-legacy devices. In this example, a VM is created
93 This is an example of a VM with all optional legacy features
116 ACPI register, doesn't have any effect in the VM.
119 generating a ``triple-fault``, which will cause the VM to initiate a
|
| /qemu/docs/devel/migration/ |
| H A D | CPR.rst | 5 VM is migrated to a new QEMU instance on the same host. It is
7 that run the VM, such as QEMU or even the host kernel. At this time,
15 CPR unconditionally stops VM execution before memory is saved, and
21 In this mode, QEMU stops the VM, and writes VM state to the migration
32 software before restarting QEMU and resuming the VM. Further, if
50 to be saved in place. Otherwise, after QEMU stops the VM, all guest
67 * If the VM was running when the outgoing ``migrate`` command was
68 issued, then QEMU automatically resumes VM execution.
79 VM status: running
84 VM status: paused (postmigrate)
[all …]
|
| H A D | mapped-ram.rst | 35 Mapped-ram migration is best done non-live, i.e. by stopping the VM on
47 immediately restored on the destination VM\ [#alternatives]_. These could be
53 If the use case requires a VM to be stopped before taking a snapshot,
58 Note: if a snapshot is taken of a running VM, but the VM will be
65 If the use case requires that the VM keeps running during and after
76 100s of GiBs), specially if the VM has been stopped beforehand.
|
| /qemu/tests/qemu-iotests/ |
| H A D | 261.out | 16 VM state size: 0
24 VM state size: 0
34 VM state size: 0
41 VM state size: 0
49 VM state size: 0
69 VM state size: 0
76 VM state size: 0
84 VM state size: 0
96 VM state size: 0
103 VM state size: 0
[all …]
|
| H A D | 218 | 77 with iotests.VM() as vm:
91 with iotests.VM() as vm:
109 with iotests.VM() as vm:
125 with iotests.VM() as vm:
141 with iotests.VM() as vm, \
|
| H A D | 286.out | 7 (snapshot ID) (snapshot name) (VM state size value) (VM state size unit) (snapshot date) (snapshot …
|
| H A D | 281 | 39 self.vm = iotests.VM()
79 self.vm_src = iotests.VM(path_suffix='src')
89 self.vm_tgt = iotests.VM(path_suffix='tgt')
144 self.vm = iotests.VM()
201 self.vm = iotests.VM()
252 self.vm = iotests.VM()
|
| H A D | 280.out | 1 === Launch VM ===
2 Enabling migration QMP events on VM...
13 VM is now stopped:
36 === Resume the VM and simulate a write request ===
|
| H A D | 255.out | 4 === Create backing chain and start VM ===
17 Closing the VM while a job is being cancelled
20 === Create images and start VM ===
|
| H A D | 283 | 74 vm = iotests.VM()
106 vm = iotests.VM()
|
| H A D | 091.out | 10 === VM 1: Migrate from VM1 to VM2 ===
16 === VM 2: Post-migration, write to disk, verify running ===
|
| H A D | 262.out | 1 Launching destination VM...
4 Launching source VM...
|
| /qemu/qapi/ |
| H A D | run-state.json | 6 # = VM run state
12 # An enumeration of VM run states.
36 # @restore-vm: guest is paused to restore VM state
40 # @save-vm: guest is paused to save the VM state
52 # @colo: guest is paused to save/restore VM state under colo
53 # checkpoint, VM can not get into this state unless colo
105 # Information about VM run state
120 # Query the run status of the VM
122 # Returns: @StatusInfo reflecting the VM
334 # @reset: Reset the VM
[all …]
|
| /qemu/tests/qemu-iotests/tests/ |
| H A D | backing-file-invalidation | 40 vm_s: Optional[iotests.VM] = None
41 vm_d: Optional[iotests.VM] = None
102 self.vm_s = iotests.VM(path_suffix='a') \
104 self.vm_d = iotests.VM(path_suffix='b') \
|
| H A D | mirror-top-perms | 37 self.vm = iotests.VM()
91 self.vm_b = iotests.VM(path_suffix='b')
|
| /qemu/docs/system/devices/ |
| H A D | ivshmem-flat.rst | 1 Inter-VM Shared Memory Flat Device
13 notification via HW interrupts and Inter-VM shared memory. This allows the
15 between, for instance, an aarch64 VM (using the traditional ivshmem device and
16 running Linux), and an arm VM (using the ivshmem-flat device and running Zephyr
27 specified for the device it is disabled, preventing the VM from notifying or
|
| /qemu/docs/ |
| H A D | COLO-FT.txt | 13 Virtual machine (VM) replication is a well known technique for providing
18 Both primary VM (PVM) and secondary VM (SVM) run in parallel. They receive the
21 immediately. Otherwise, a VM checkpoint (on demand) is conducted.
47 | Primary VM | +-----------+-----------+ +-----------+------------+ |Secondary VM|
54 | | | | VM Checkpoint +-------------->+ VM Checkpoint | | | |
71 | VM Monitor | | | | | | VM Monitor |
94 When primary VM writes data into image, the colo disk manager captures this data
95 and sends it to secondary VM's which makes sure the context of secondary VM's
96 image is consistent with the context of primary VM 's image.
101 to make sure the state of VM in Secondary side is always consistent with VM in
[all …]
|
| H A D | block-replication.txt | 11 for COLO (COarse-grain LOck-stepping) where the Secondary VM is running.
13 where the Secondary VM is not running.
19 consecutive checkpoints. The VM state of the Primary and Secondary VM is
20 identical right after a VM checkpoint, but becomes different as the VM
22 the modified disk contents in the Secondary VM must be buffered, and are
86 runs the secondary VM. The read pattern (fifo) for quorum can be extended
93 3) The secondary disk receives writes from the primary VM through QEMU's
101 that is modified by the primary VM. It should also start as an empty disk,
137 This interface is called after all VM state is transferred to
|