15f7be9a52
This external documentation for pyVmomi was generated using Googly Docs (aka Google Standard Documentation) which renders very cleanly in GitHub. Internal documentation for a class should be done in Sphinx format because tools like pyCharm and Eclipse can use that documentation as a hint for code completion. Note: External docs as Googly Docs, internal docs as Sphinx. Closes bug#15
34 lines
1.1 KiB
ReStructuredText
34 lines
1.1 KiB
ReStructuredText
.. _vim.vm.device.VirtualDiskOption: ../../../../vim/vm/device/VirtualDiskOption.rst
|
|
|
|
.. _vim.vm.device.VirtualDiskOption.DiskMode: ../../../../vim/vm/device/VirtualDiskOption/DiskMode.rst
|
|
|
|
vim.vm.device.VirtualDiskOption.DiskMode
|
|
========================================
|
|
The list of known disk modes.The list of supported disk modes varies by the backing type. The "persistent" mode is supported by every backing type.
|
|
:contained by: `vim.vm.device.VirtualDiskOption`_
|
|
|
|
:type: `vim.vm.device.VirtualDiskOption.DiskMode`_
|
|
|
|
:name: append
|
|
|
|
values:
|
|
--------
|
|
|
|
independent_persistent
|
|
Same as persistent, but not affected by snapshots.
|
|
|
|
persistent
|
|
Changes are immediately and permanently written to the virtual disk.
|
|
|
|
independent_nonpersistent
|
|
Same as nonpersistent, but not affected by snapshots.
|
|
|
|
undoable
|
|
Changes are made to a redo log, but you are given the option to commit or undo.
|
|
|
|
nonpersistent
|
|
Changes to virtual disk are made to a redo log and discarded at power off.
|
|
|
|
append
|
|
Changes are appended to the redo log; you revoke changes by removing the undo log.
|