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
25 lines
1.4 KiB
ReStructuredText
25 lines
1.4 KiB
ReStructuredText
.. _vim.host.AutoStartManager.AutoPowerInfo: ../../../../vim/host/AutoStartManager/AutoPowerInfo.rst
|
|
|
|
.. _vim.host.AutoStartManager.AutoPowerInfo.WaitHeartbeatSetting: ../../../../vim/host/AutoStartManager/AutoPowerInfo/WaitHeartbeatSetting.rst
|
|
|
|
vim.host.AutoStartManager.AutoPowerInfo.WaitHeartbeatSetting
|
|
============================================================
|
|
Determines if the virtual machine should start after receiving a heartbeat, ignore heartbeats and start after the startDelay has elapsed, or follow the system default before powering on. When a virtual machine is next in the start order, the system either waits a specified period of time for a virtual machine to power on or it waits until it receives a successful heartbeat from a powered on virtual machine. By default, this is set to no.
|
|
:contained by: `vim.host.AutoStartManager.AutoPowerInfo`_
|
|
|
|
:type: `vim.host.AutoStartManager.AutoPowerInfo.WaitHeartbeatSetting`_
|
|
|
|
:name: systemDefault
|
|
|
|
values:
|
|
--------
|
|
|
|
yes
|
|
The system waits until receiving a heartbeat before powering on the next machine in the order.
|
|
|
|
systemDefault
|
|
The system uses the default value to determine whether or not to wait to receive a heartbeat before powering on the next machine in the order.
|
|
|
|
no
|
|
The system does not wait to receive a heartbeat before powering on the next machine in the order. This is the default setting.
|