New-PveNodesStorageContent
Allocate disk images.
API: POST /nodes/{node}/storage/{storage}/content, Proxmox VE API viewer
Syntax
Section titled “Syntax”New-PveNodesStorageContent [-PveTicket <PveTicket>] -Filename <string> [-Format <string>] -Node <string> -Size <string> -Storage <string> -Vmid <int> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Filename |
string |
Yes | The name of the file to create. |
-Format |
string |
No | Format of the image. Values: raw, qcow2, subvol, vmdk. |
-Node |
string |
Yes | The cluster node name. |
-Size |
string |
Yes | Size in kilobyte (1024 bytes). Optional suffixes ‘M’ (megabyte, 1024K) and ‘G’ (gigabyte, 1024M) |
-Storage |
string |
Yes | The storage identifier. |
-Vmid |
int |
Yes | Specify owner 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.
