Lines Matching full:-
1 Mapped-ram
4 Mapped-ram is a new stream format for the RAM section designed to
22 -----
25 ``mapped-ram`` capabilities:
29 ``migrate_set_capability mapped-ram on``
35 Mapped-ram migration is best done non-live, i.e. by stopping the VM on
38 For best performance enable the ``direct-io`` parameter as well:
40 ``migrate_set_parameter direct-io on``
42 Use-cases
43 ---------
45 The mapped-ram feature was designed for use cases where the migration
49 non-live.
51 - Non-live snapshot
54 that's the ideal scenario for mapped-ram migration. Not having to
63 - Live snapshot
66 the snapshot operation, then mapped-ram migration can still be used,
68 background-snapshot should be evaluated as well. One benefit of
69 mapped-ram in this scenario is portability since background-snapshot
74 snapshots or the ``file:`` migration alone, mapped-ram provides
79 ------------------
93 Without mapped-ram: With mapped-ram:
95 --------------------- --------------------------------
97 --------------------- --------------------------------
98 | ramblock 2 header | | ramblock 1 mapped-ram header |
99 --------------------- --------------------------------
101 --------------------- | ... |
102 | ramblock n header | --------------------------------
103 --------------------- | ramblock 1 pages |
105 --------------------- --------------------------------
107 | (iter 1) | --------------------------------
108 | ... | | ramblock 2 mapped-ram header |
109 --------------------- --------------------------------
111 --------------------- | ... |
112 | stream of pages | --------------------------------
115 --------------------- --------------------------------
117 --------------------- --------------------------------
119 --------------------------------
121 --------------------------------
124 - ramblock header: the generic information for a ramblock, such as
127 - ramblock mapped-ram header: the information added by this feature:
132 ------------