Set-PveClusterMappingPci

Update a hardware mapping.

API: PUT /cluster/mapping/pci/{id}, Proxmox VE API viewer

Syntax

Set-PveClusterMappingPci
    [-PveTicket <PveTicket>]
    [-Delete <string>]
    [-Description <string>]
    [-Digest <string>]
    -Id <string>
    [-LiveMigrationCapable <bool>]
    [-Map <array>]
    [-Mdev <bool>]
    [<CommonParameters>]

Parameters

Parameter	Type	Required	Description
-PveTicket	PveTicket	No	Ticket data connection.
-Delete	string	No	A list of settings you want to delete.
-Description	string	No	Description of the logical PCI device.
-Digest	string	No	Prevent changes if current configuration file has a different digest. This can be used to prevent concurrent modifications.
-Id	string	Yes	The ID of the logical PCI mapping.
-LiveMigrationCapable	bool	No	Marks the device(s) as being able to be live-migrated (Experimental). This needs hardware and driver support to work.
-Map	array	No	A list of maps for the cluster nodes.
-Mdev	bool	No	Marks the device(s) as being capable of providing mediated devices.

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

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