New-PveNodesStartall
Start all VMs and containers located on this node (by default only those with onboot=1).
API: POST /nodes/{node}/startall, Proxmox VE API viewer
Syntax
Section titled “Syntax”New-PveNodesStartall [-PveTicket <PveTicket>] [-Force <bool>] [-MaxWorkers <int>] -Node <string> [-Vms <string>] [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Force |
bool |
No | Issue start command even if virtual guest have ‘onboot’ not set or set to off. |
-MaxWorkers |
int |
No | Defines the maximum number of tasks running concurrently. If not set, uses ‘max_workers’ from datacenter.cfg, and if that’s not set, the available CPU threads, clamped to a maximum of 8, are used. |
-Node |
string |
Yes | The cluster node name. |
-Vms |
string |
No | Only consider guests from this comma separated list of VMIDs. |
Every parameter also binds by property name from the pipeline, so an object with node and vmid properties (the output of Get-PveGuest, for one) fills -Node and -Vmid. Without -PveTicket the cmdlet uses the last connection, see Connection.
Output
Section titled “Output”A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.
