pve_mapping_pci_update
Update an existing PCI cluster mapping. Supports dry-run planning and optional config digest for optimistic concurrency checks.
Instructions
MUTATION: update a PCI cluster mapping. Dry-run by default (reads current config into the PLAN); confirm=True executes and returns {"status": "ok", "result": null} (no further payload). MEDIUM risk — a running VM holding this mapping may need a restart to pick up the new device path. No snapshot primitive; re-apply the captured config to revert, or use pve_mapping_pci_delete to remove the mapping outright.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| map | No | PCI device map string(s) defining the physical device(s) covered by this mapping | |
| digest | No | Optional config digest for optimistic-concurrency check against the current config | |
| confirm | No | False (default) returns a dry-run PLAN only; True executes the update | |
| mapping_id | Yes | ID of the existing PCI cluster mapping to update | |
| description | No | Optional free-text description to set on the mapping | |
| proximo_target | No | Which configured Proxmox target to run this call against — a target name from your multi-target config (a specific PVE/PBS/PMG/PDM box). Omit to use the single/default target from the environment; the selection applies only to this call. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |