<![CDATA[Enable Maintenance Mode = Host Not Enough Memory]]>Doing some more testing, where I wished to place one Host in maintenance mode. I was then met with HOST_NOT_ENOUGH_FREE_MEMORY.
The pool is a 3 host pool in HA, with load balancing enabled.

My guess is that when trying to enable Maintenance mode. It tries to migrate ALL VMs on that host, to ONE single Host on the receiving end. And then it exhausts the amount of available memory.

What I had to do, was manually disable load balancing. And manually migrate VMs to the two other hosts, to distribute them. This worked.

What I expected to have happened:
The evacuation of the host going into Maintenance mode, would be distributing the VMs in a smarter fashion. So that their workload would fit in the pooled resources available.

Commit: 2f846
XCP-NG: Fully updated as of writing

host.setMaintenanceMode
{
  "id": "<obfuscated>",
  "maintenance": true
}
{
  "code": "HOST_NOT_ENOUGH_FREE_MEMORY",
  "params": [
    "OpaqueRef:<obfuscated>"
  ],
  "task": {
    "uuid": "c3a83a2d-003d-ac0f-48b8-79a905c9e557",
    "name_label": "Async.host.evacuate",
    "name_description": "",
    "allowed_operations": [],
    "current_operations": {},
    "created": "20260929T07:46:40Z",
    "finished": "20260929T07:46:40Z",
    "status": "failure",
    "resident_on": "OpaqueRef:<obfuscated>",
    "progress": 1,
    "type": "<none/>",
    "result": "",
    "error_info": [
      "HOST_NOT_ENOUGH_FREE_MEMORY",
      "OpaqueRef:<obfuscated>"
    ],
    "other_config": {},
    "subtask_of": "OpaqueRef:NULL",
    "subtasks": [],
    "backtrace": "(((process xapi)(filename ocaml/xapi/xapi_host.ml)(line 629))((process xapi)(filename hashtbl.ml)(line 159))((process xapi)(filename hashtbl.ml)(line 165))((process xapi)(filename hashtbl.ml)(line 170))((process xapi)(filename ocaml/xapi/xapi_host.ml)(line 625))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 24))((process xapi)(filename ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml)(line 39))((process xapi)(filename ocaml/xapi/rbac.ml)(line 228))((process xapi)(filename ocaml/xapi/rbac.ml)(line 238))((process xapi)(filename ocaml/xapi/server_helpers.ml)(line 78)))"
  },
  "message": "HOST_NOT_ENOUGH_FREE_MEMORY(OpaqueRef:<obfuscated>)",
  "name": "XapiError",
  "stack": "XapiError: HOST_NOT_ENOUGH_FREE_MEMORY(OpaqueRef:<obfuscated>)
    at XapiError.wrap (file:///opt/xen-orchestra/packages/xen-api/_XapiError.mjs:16:12)
    at default (file:///opt/xen-orchestra/packages/xen-api/_getTaskResult.mjs:13:29)
    at Xapi._addRecordToCache (file:///opt/xen-orchestra/packages/xen-api/index.mjs:1358:24)
    at file:///opt/xen-orchestra/packages/xen-api/index.mjs:1392:14
    at Array.forEach (<anonymous>)
    at Xapi._processEvents (file:///opt/xen-orchestra/packages/xen-api/index.mjs:1382:12)
    at Xapi._watchEvents (file:///opt/xen-orchestra/packages/xen-api/index.mjs:1589:14)"
}

Update: Edited title, since it would suggest Load Balancing was the problem. It isn't. It's the assignment of migration target(s) that is the issue (imho)

]]>https://xcp-ng.org/forum/topic/12498/enable-maintenance-mode-host-not-enough-memoryRSS for NodeTue, 29 Sep 2026 09:04:13 GMTTue, 29 Sep 2026 07:53:25 GMT60<![CDATA[Reply to Enable Maintenance Mode = Host Not Enough Memory on Tue, 29 Sep 2026 08:39:16 GMT]]>@poddingue

Huh.. Good catch.
I set all of the VMs to restart, and now it does make maintenance mode possible, on the host.

However, when we go into licensed/paid production (soon tm). It would be an absolute nightmare to try and find one VM that might not be on the right HA-plan... And it does kind of feel that Maintenance-mode should be compatible with whatever HA-plan is chosen regardless.

Perhaps there could be a way to assign a global/pool-wide HA-plan along with enabling HA alltogether?

]]>https://xcp-ng.org/forum/post/108741https://xcp-ng.org/forum/post/108741Tue, 29 Sep 2026 08:39:16 GMT<![CDATA[Reply to Enable Maintenance Mode = Host Not Enough Memory on Tue, 29 Sep 2026 08:26:33 GMT]]>Your thread looks a lot like https://xcp-ng.org/forum/topic/12321. Same error, same call, HA enabled there too. Olivier's answer on that one was that VMs whose HA restart priority isn't Restart aren't protected, so they never get a real evacuation plan.
His two workarounds were setting those VMs to Restart, or turning HA off for the maintenance window.

It doesn't land for everyone, though. On https://xcp-ng.org/forum/topic/12348 @MajorP93 fixed his by moving every VM from best-effort to restart, and @acebmxer tried the same thing and got HA_OPERATION_WOULD_BREAK_FAILOVER_PLAN instead. Same change, opposite outcome. 🤷

So, what are your VMs set to, restart or best-effort? That would tell us whether you're looking at the same thing or something else entirely.

Upstream there are two PRs off the back of that discussion. 7145 merged on 8 July and only makes the error message clearer. 7146 is the one that changes the evacuation behaviour itself, and it's still open. So if it is the same problem, I don't think there's anything you can pull down yet.

]]>https://xcp-ng.org/forum/post/108740https://xcp-ng.org/forum/post/108740Tue, 29 Sep 2026 08:26:33 GMT