From 9f708aad8a667066aa189ffcadbd1be72510397a Mon Sep 17 00:00:00 2001
From: "cortex-ai-agents[bot]"
 <279748396+cortex-ai-agents[bot]@users.noreply.github.com>
Date: Mon, 17 Aug 2026 06:21:34 +0000
Subject: [PATCH] docs: fix inaccurate live migration bullet in CR reservations

Signed-off-by: cortex-ai-agents[bot] <279748396+cortex-ai-agents[bot]@users.noreply.github.com>
---
 docs/reservations/committed-resource-reservations.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/reservations/committed-resource-reservations.md b/docs/reservations/committed-resource-reservations.md
index 4c3f448be..ae0b1f68c 100644
--- a/docs/reservations/committed-resource-reservations.md
+++ b/docs/reservations/committed-resource-reservations.md
@@ -178,7 +178,7 @@ The `spec_only_unblocked` term exists because an InFlightReservation on the same
 **Corner cases worth noting:**
 - Confirmed VMs exceed reservation size (e.g. after resize): clamp `remaining` to 0, never negative
 - Spec-only VM larger than remaining slot: block `spec_only_unblocked` — those resources will land when the VM starts
-- Live migration within a reservation: handled implicitly by `hv.Status.Allocation`, which libvirt reports on both source and target during migration; no special logic needed
+- Live migration within a reservation: when a confirmed VM disappears from its expected host, the controller scans all hypervisors. If the VM is the sole allocation and the new host has capacity, the reservation follows the VM; otherwise the VM is removed from the reservation.
 
 ### InFlightReservation