Matter-over-Thread pairing fails with 1.5GB RAM in VM, while Matter-over-Wi-Fi works

[Sparkfog]

Describe the issue you are experiencing

I found what appears to be a memory/resource issue when running Home Assistant in a Linux VM.

When the VM has only 1.5 GB RAM allocated, pairing new Matter-over-Thread devices consistently fails.

However:
Matter-over-Wi-Fi devices pair successfully
Existing devices continue working
Increasing VM RAM to 2.5 GB allows Matter-over-Thread pairing to succeed without any other changes

This makes it seem specific to Thread onboarding/commissioning rather than general Matter pairing.

Matter-over-Thread pairing should work reliably at supported RAM allocations, or minimum requirements should be documented more clearly, or give a according response.

Actual behavior
Matter-over-Thread pairing fails at 1.5 GB RAM
Matter-over-Thread pairing works after increasing RAM to 2.5 GB

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Which app are you reporting an issue with?

OpenThread Border Router

What is the version of the app?

2.16.7

Steps to reproduce the issue

Run Home Assistant in a Linux VM with 1.5 GB RAM
Attempt to pair a new Matter-over-Thread device
Pairing fails
Increase VM RAM allocation to 2.5 GB
Retry Matter-over-Thread pairing
Pairing succeeds
Expected behavior

System Health information

System Information

version	core-2026.4.4
installation_type	Home Assistant OS
dev	false
hassio	true
docker	true
container_arch	amd64
user	root
virtualenv	false
python_version	3.14.2
os_name	Linux
os_version	6.12.77-haos
arch	x86_64
timezone	Europe/Zurich
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.5
Stage	running
Available Repositories	2952
Downloaded Repositories	24

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 17.2
update_channel	stable
supervisor_version	supervisor-2026.04.0
agent_version	1.8.1
docker_version	29.3.1
disk_total	30.8 GB
disk_used	13.1 GB
nameservers	192.168.1.1
healthy	true
supported	true
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization	kvm
board	ova
supervisor_api	ok
version_api	ok
installed_addons	Matter Server (8.4.0), OpenThread Border Router (2.16.7), ESPHome Device Builder (2026.4.3), Cloudflared (7.0.6), Advanced SSH & Web Terminal (23.0.8), Fusion (2024.10.1), Everything Presence Zone Configurator (2.0.12), Studio Code Server (6.0.1), Zigbee2MQTT (2.9.2-1), Mosquitto broker (7.1.0)

Dashboards

dashboards	3
resources	17
views	5
mode	storage

Network Configuration

adapters	lo (disabled), enp1s0 (enabled, default, auto), docker0 (disabled), hassio (disabled), veth41170d0 (disabled), vethbf44412 (disabled), vethd36d8d8 (disabled), veth64015fd (disabled), vethdd6ef39 (disabled), veth41432a3 (disabled), wpan0 (disabled), vethc7e3311 (disabled), vethbf8b5f1 (disabled), veth921e320 (disabled)
ipv4_addresses	lo (127.0.0.1/8), enp1s0 (192.168.1.143/24), docker0 (172.30.232.1/23), hassio (172.30.32.1/23), veth41170d0 (), vethbf44412 (), vethd36d8d8 (), veth64015fd (), vethdd6ef39 (), veth41432a3 (), wpan0 (), vethc7e3311 (), vethbf8b5f1 (), veth921e320 ()
ipv6_addresses	lo (::1/128), enp1s0 (fd17:2f57:91e4:895:a6f5:7ea4:7542:9411/64, fe80::4e68:e83a:85e:c498/64), docker0 (fe80::5cb5:d6ff:fe21:571b/64), hassio (fd0c:ac1e:2100::1/48, fe80::b8b7:d6ff:fe39:9666/64), veth41170d0 (fe80::e009:7bff:fe1a:6859/64), vethbf44412 (fe80::e089:74ff:fe87:ea79/64), vethd36d8d8 (fe80::d0fb:a6ff:fe63:4e40/64), veth64015fd (fe80::a479:29ff:feac:720f/64), vethdd6ef39 (fe80::f81d:d7ff:fecb:72e7/64), veth41432a3 (fe80::50e3:1bff:fe4f:1e1f/64), wpan0 (fd3d:e9f1:d485:a9c3:0:ff:fe00:fc11/64, fd3d:e9f1:d485:a9c3:0:ff:fe00:fc38/64, fdbb:439f:e8e7:1:180e:3740:3b14:ad71/64, fd3d:e9f1:d485:a9c3:0:ff:fe00:fc10/64, fd3d:e9f1:d485:a9c3:0:ff:fe00:2000/64, fd3d:e9f1:d485:a9c3:b31c:e0fd:5e79:2a38/64, fe80::d0bb:a61:4fb5:7c9c/64), vethc7e3311 (fe80::c4ad:1aff:fe45:49a5/64), vethbf8b5f1 (fe80::9053:26ff:feeb:4f21/64), veth921e320 (fe80::28ca:7bff:feea:a93f/64)
announce_addresses	192.168.1.143, fd17:2f57:91e4:895:a6f5:7ea4:7542:9411, fe80::4e68:e83a:85e:c498

Recorder

oldest_recorder_run	15. April 2026 um 18:55
current_recorder_run	27. April 2026 um 21:33
estimated_db_size	675.43 MiB
database_engine	sqlite
database_version	3.49.2

Xiaomi Miot

component_version	1.1.4
can_reach_server	ok
can_reach_spec	ok
logged_accounts	1
total_devices	3

Anything in the Supervisor logs that might be useful for us?

Anything in the app logs that might be useful for us?

Additional information

No response