New-PveNodesQemuMtunnel
Migration tunnel endpoint - only for internal use by VM migration.
API: POST /nodes/{node}/qemu/{vmid}/mtunnel, Proxmox VE API viewer
Syntax
Section titled “Syntax”New-PveNodesQemuMtunnel [-PveTicket <PveTicket>] [-Bridges <string>] -Node <string> [-Storages <string>] -Vmid <int> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Bridges |
string |
No | List of network bridges to check availability. Will be checked again for actually used bridges during migration. |
-Node |
string |
Yes | The cluster node name. |
-Storages |
string |
No | List of storages to check permission and availability. Will be checked again for all actually used storages during migration. |
-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.
