Document default FC and disk assignment workflow for ATVM VMs

Update the VMware runbook to describe the default VM attachment workflow for assigning FC passthrough adapters vmhba7 and vmhba8 plus datastore disks atvm-DISK_1.vmdk and atvm-DISK_2.vmdk, with mandatory live verification, pre-action summary, explicit approval, and no-substitution behavior unless the operator specifies alternatives.
This commit is contained in:
2026-03-18 19:40:32 -04:00
parent 51d782d964
commit d989c8a071
2 changed files with 40 additions and 0 deletions

View File

@@ -30,6 +30,20 @@ This folder contains the VMware/vCenter + MigrateOps runbook for CDS MCP workflo
- Unless user explicitly asks otherwise, scope VM lookup/list responses to cluster `QACL-ATVMCypressONLY`.
- For vCenter VM lookup requests, always include datastore name and VM notes/annotation in the response.
## VM Disk And FC Assignment Requirement
- For requests to assign disks and PCI passthrough FC adapters to a VM, use the workflow in `esxvm-guide.md`.
- Always verify the VM, live ESXi host, and datastore first.
- Default expected host is `192.168.1.165`, but verify live placement before planning.
- Unless the operator explicitly specifies alternatives, default to planning these FC adapters:
- `vmhba7` (`0000:85:00.0`)
- `vmhba8` (`0000:85:00.1`)
- Unless the operator explicitly specifies alternatives, default to planning these existing datastore disks:
- `atvm-DISK_1.vmdk`
- `atvm-DISK_2.vmdk`
- The disks must be located in the same datastore as the VM under the `atvm-DISKS` directory.
- If the default or operator-specified adapters or disks are missing, do nothing and report that no assignment will be performed.
- Always provide a read-only summary of findings and planned assignment, then wait for explicit approval before any change.
## Update Rules
- Update `esxvm-guide.md` only when workflow/rules/default behavior changes.
- Update `esxvm-runs.md` only when a run reveals a new learning/failure pattern/required check.