
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
27 lines
652 B
ReStructuredText
27 lines
652 B
ReStructuredText
.. _vim.vm.FlagInfo: ../../../vim/vm/FlagInfo.rst
|
|
|
|
.. _virtualMmuUsage: ../../../vim/vm/FlagInfo.rst#virtualMmuUsage
|
|
|
|
.. _vim.vm.FlagInfo.VirtualMmuUsage: ../../../vim/vm/FlagInfo/VirtualMmuUsage.rst
|
|
|
|
vim.vm.FlagInfo.VirtualMmuUsage
|
|
===============================
|
|
Set of possible values for `virtualMmuUsage`_ .
|
|
:contained by: `vim.vm.FlagInfo`_
|
|
|
|
:type: `vim.vm.FlagInfo.VirtualMmuUsage`_
|
|
|
|
:name: off
|
|
|
|
values:
|
|
--------
|
|
|
|
on
|
|
Use nested paging hardware support if the physical hardware supports it.
|
|
|
|
automatic
|
|
Determine automatically whether to use nested page table hardware support.
|
|
|
|
off
|
|
Do not use nested page table hardware support.
|