Get-PveNodesCapabilitiesQemuCpuFlags
List of available VM-specific CPU flags. Returns an empty list for ‘aarch64’ as no VM-specific flags are defined for it yet.
API: GET /nodes/{node}/capabilities/qemu/cpu-flags, Proxmox VE API viewer
Syntax
Section titled “Syntax”Get-PveNodesCapabilitiesQemuCpuFlags [-PveTicket <PveTicket>] [-Accel <string>] [-Arch <string>] -Node <string> [<CommonParameters>]Parameters
Section titled “Parameters”| Parameter | Type | Required | Description |
|---|---|---|---|
-PveTicket |
PveTicket |
No | Ticket data connection. |
-Accel |
string |
No | Acceleration type to check node compatibility for. Values: kvm, tcg. |
-Arch |
string |
No | Virtual processor architecture. Defaults to the host architecture. Values: x86_64, aarch64. |
-Node |
string |
Yes | The cluster node name. |
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.
