Virtual App Power On V App Task
Starts this vApp.
The virtual machines (or sub vApps) will be started in the order specified in the vApp configuration. If the vApp is suspended (@see vim.VirtualApp.Summary#suspended), all suspended virtual machines will be powered-on based on the defined start-up order.
While a vApp is starting, all power operations performed on sub entities are disabled through the VIM API. They will throw TaskInProgress.
In case of a failure to power-on a virtual machine, the exception from the virtual machine power on is returned, and the power-on sequence will be terminated. In case of a failure, virtual machines that are already started will remain powered-on.
Required privileges: VApp.PowerOn
The unique identifier for the managed object to which the method attaches; the serialized managed object reference for a request has the form moType/moId
, in this case VirtualApp/{moId}
.
The vSphere release schema. The current specification covers vSphere 8.0.2.0 APIs.
OK
{
"_typeName": "string",
"type": "string",
"value": "string"
}
InvalidPowerState: if the vApp is already running
TaskInProgress: if the vApp is busy
NotEnoughLicenses: if there are not enough licenses to power on one or more virtual machines.
NotSupported: if the vApp is marked as a template.
InvalidState: if it fails to power on a virtual machine due to no host availability, or unable to access the configuration file of a VM.
InsufficientResourcesFault: if this operation would violate a resource usage policy.
VmConfigFault: if a configuration issue on the vApp or a virtual machine in the vApp prevents the power-on to complete. Typically, a more specific fault, such as InvalidPropertyType is thrown.
VAppConfigFault: if a configuration issue on a vApp prevents the power-on. Typically, a more specific fault, MissingPowerOnConfiguration, is thrown.
FileFault: if there is a problem accessing the virtual machine on the filesystem.
MissingNetworkIpConfig: if no network configuration exists for the primary network for the vApp.
{
"_typeName": "string",
"faultCause": "MethodFault Object",
"faultMessage": [
{
"_typeName": "string",
"key": "string",
"arg": [
{
"_typeName": "string",
"key": "string",
"value": {
"_typeName": "string"
}
}
],
"message": "string"
}
]
}