Skip to content

New-PveNodesQemuClone

Create a copy of virtual machine/template.

API: POST /nodes/{node}/qemu/{vmid}/clone, Proxmox VE API viewer

Aliases: Copy-PveQemu

New-PveNodesQemuClone
[-PveTicket <PveTicket>]
[-Bwlimit <int>]
[-Description <string>]
[-Format <string>]
[-Full <bool>]
[-Name <string>]
-Newid <int>
-Node <string>
[-Pool <string>]
[-Snapname <string>]
[-Storage <string>]
[-Target <string>]
-Vmid <int>
[<CommonParameters>]
Parameter Type Required Description
-PveTicket PveTicket No Ticket data connection.
-Bwlimit int No Override I/O bandwidth limit (in KiB/s).
-Description string No Description for the new VM.
-Format string No Target disk format. Only valid for full clone. If the target storage does not support the format, the storage’s default format is used instead. Values: raw, qcow2, vmdk.
-Full bool No Create a full copy of all disks. This is always done when you clone a normal VM. For VM templates, we try to create a linked clone by default.
-Name string No Set a name for the new VM.
-Newid int Yes VMID for the clone.
-Node string Yes The cluster node name.
-Pool string No Add the new VM to the specified pool.
-Snapname string No The name of the snapshot.
-Storage string No Target storage for full clone.
-Target string No Target node. Only allowed if the original VM is on shared storage.
-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.

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