ProxmoxMCP-Plus v0.7.2
create_vm and update_vm_config accept optional BIOS, EFI vars disk (efitype=4m),
Secure Boot key enrollment and TPM 2.0 settings. Creation uses the selected
system disk storage. Updates that allocate firmware volumes require a storage
ID and VM.Audit in addition to write and allocation privileges. Updates check
both active and pending configurations and pass the shared configuration digest
to Proxmox. They refuse to overwrite existing EFI or TPM state.
PR #215
Secure Boot keys come from the host's installed firmware template. Verify the
guest firmware state after startup. Changing firmware on an existing guest can
affect boot and disk-encryption recovery. After a failed allocation or timeout,
inspect the configuration before retrying.
Install proxmox-mcp-plus==0.7.2 or pull
ghcr.io/rekklesna/proxmoxmcp-plus:0.7.2. Restart the server and reconnect
clients to refresh the tool schema. Existing configuration and job databases
require no migration.