KEkernel

Trigger proactive guest memory reclaim

Changed on

Requests runtime balloon inflation across reclaim-eligible guests. The same planner used by host-pressure reclaim is applied, including protected floors and per-VM step limits.

post/resources/memory/reclaim

Request

  • Base URL
    http://localhost:4973
  • URL
    http://localhost:4973/resources/memory/reclaim
  • Auth
    HTTP bearer

Request body

reclaim_bytesinteger required

Total bytes of guest memory to reclaim across eligible VMs.

hold_forstring

How long to keep the reclaim hold active (Go duration string). Defaults to 5m when omitted.

dry_runboolean

Calculate a reclaim plan without applying balloon changes or creating a hold.

reasonstring

Optional operator-provided reason attached to logs and traces.

Example request

{
  "reclaim_bytes": 536870912,
  "hold_for": "5m",
  "reason": "prepare for another vm start"
}

Response

Reclaim plan and applied results

requested_reclaim_bytesinteger required
planned_reclaim_bytesinteger required
applied_reclaim_bytesinteger required
hold_untilstring date-time

When the current manual reclaim hold expires.

host_available_bytesinteger required
host_pressure_state'healthy' | 'pressure' required

Example response

{
  "actions": [
    {
      "status": "applied"
    }
  ]
}

Changes