File: MigrationFault.rst

package info (click to toggle)
python-pyvmomi 5.5.0-2014.1.1-3
  • links: PTS, VCS
  • area: main
  • in suites: stretch
  • size: 14,348 kB
  • ctags: 497
  • sloc: python: 6,594; makefile: 12
file content (24 lines) | stat: -rw-r--r-- 1,647 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
.. _vim.fault.VimFault: ../../vim/fault/VimFault.rst


vim.fault.MigrationFault
========================
    :extends:

        `vim.fault.VimFault`_

  Base object type for issues that can occur when reassigning the execution host of a virtual machine using migrate or relocate. These issues are typically used as argument in the MigrationEvent. When a MigrationFault is used as a value in a MigrationEvent, the type of MigrationEvent determines if the issue is a warning or an error (for example, MigrationHostWarningEvent or MigrationHostErrorEvent). When thrown as an exception, the fault is an error.Issues are categorized as errors or warnings according to the following criteria:If the virtual machine is powered on:
   * Error for fatal problems with the VMotion interfaces or licensing.
   * Error if VMotion would fail.
   * Error if VMotion would in any way interrupt the continuous and consistent operation of the virtual machine.
   * Warning for potential performance or connectivity problems between the source and destination VMotion interfaces.
   * Warning if the virtual machine's currently disconnected devices may not be connectable after VMotion.If the virtual machine is powered off or suspended:
   * Error if the destination host cannot access all the files that comprise the virtual machine (including virtual disks).
   * Error if aspects of the virtual machine are not supported by the destination host's hardware or software.
   * Warning if problems would occur when powering on or resuming the virtual machine, if the usage/configuration of the destination host were to remain in its current state.

Attributes: