New-PveNodesLxcStatusStart
Start the container.
API: POST /nodes/{node}/lxc/{vmid}/status/start, Proxmox VE API viewer
Aliases: Start-PveLxc
Syntax
Section titled “Syntax”New-PveNodesLxcStatusStart [-PveTicket <PveTicket>] [-Debug_ <bool>] -Node <string> [-Skiplock <bool>] -Vmid <int> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Debug_ |
bool |
No | If set, enables very verbose debug log-level on start. |
-Node |
string |
Yes | The cluster node name. |
-Skiplock |
bool |
No | Ignore locks - only root is allowed to use this option. |
-Vmid |
int |
Yes | The (unique) ID of the VM. |
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.
