Skip to content

Commit

Permalink
Postsubmit site update from 378049b
Browse files Browse the repository at this point in the history
Signed-off-by: kubevirt-bot <[email protected]>
  • Loading branch information
kubevirt-bot committed Sep 17, 2024
1 parent 82899b4 commit 4a8757b
Show file tree
Hide file tree
Showing 4 changed files with 101 additions and 97 deletions.
22 changes: 13 additions & 9 deletions compute/live_migration/index.html
Original file line number Diff line number Diff line change
Expand Up @@ -3431,16 +3431,20 @@ <h2 id="migration-timeouts">Migration timeouts<a class="headerlink" href="#migra
assumed that the instance will write to the free pages and blocks
(pollute the pages) at a lower rate than these are being copied.</p>
<h3 id="completion-time">Completion time<a class="headerlink" href="#completion-time" title="Permanent link">&para;</a></h3>
<p>In some cases the virtual machine can write to different memory pages /
disk blocks at a higher rate than these can be copied, which will
prevent the migration process from completing in a reasonable amount of
time. In this case, live migration will be aborted if it is running for
a long period of time. The timeout is calculated base on the size of
the VMI, it's memory and the ephemeral disks that are needed to be
<p>In some cases the virtual machine can have a high dirty-rate, which
means it will write to different memory pages / disk blocks at a
higher rate than these can be copied over.
This situation will prevent the migration process from completing
in a reasonable amount of time.</p>
<p>In this case, a timeout can be defined so that live migration will
either be aborted or switched to post-copy mode (if it's enabled)
if it is running for a long period of time.</p>
<p>The timeout is calculated based on the size of
the VMI, its memory and the ephemeral disks that are needed to be
copied. The configurable parameter <code>completionTimeoutPerGiB</code>, which
defaults to 800s is the time for GiB of data to wait for the migration
to be completed before aborting it. A VMI with 8Gib of memory will time
out after 6400 seconds.</p>
defaults to 800s, is the maximum amount of time per GiB of data allowed before the migration
gets aborted / switched to post-copy mode.
For example, with the default value, a VMI with 8GiB of memory will time-out after 6400 seconds.</p>
<h3 id="progress-timeout">Progress timeout<a class="headerlink" href="#progress-timeout" title="Permanent link">&para;</a></h3>
<p>Live migration will also be aborted when it will be noticed that copying
memory doesn't make any progress. The time to wait for live migration to
Expand Down
2 changes: 1 addition & 1 deletion search/search_index.json

Large diffs are not rendered by default.

Loading

0 comments on commit 4a8757b

Please sign in to comment.