New-PveNodesStopall

Stop all VMs and Containers.

API: POST /nodes/{node}/stopall, Proxmox VE API viewer

Syntax

New-PveNodesStopall
    [-PveTicket <PveTicket>]
    [-ForceStop <bool>]
    [-MaxWorkers <int>]
    -Node <string>
    [-Timeout <int>]
    [-Vms <string>]
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-ForceStop	bool	No	Force a hard-stop after the timeout.
-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.
-Timeout	int	No	Timeout for each guest shutdown task. Depending on force-stop, the shutdown gets then simply aborted or a hard-stop is forced.
-Vms	string	No	Only consider Guests with these IDs.

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

A PveResponse: the data returned by Proxmox VE is in .Response.data, the outcome in .IsSuccessStatusCode. See Results and Errors.