Summary
Since physically migrating my Proxmox host to a new NUC13i5ANH, Home Assistant Core, which is running in it own VM has been crash-looping with an illegal-instruction fault (SIGILL / signal 4) roughly every 15 minutes to 2 hours, sometimes longer. The VM itself is stable, it’s just HA that keeps restarting. The Supervisor watchdog catches it and restarts Core each time, so the system self-heals, but this has been happening continuously for several days now. I’ve exhausted every fix I can think of and I’m hoping someone has seen this pattern before.
Hardware / Environment
- Host: ASUS NUC13ANBI5 (13th Gen Intel Core i5-1340P, 4 P-cores + 8 E-cores, hybrid architecture)
- 32GB RAM (2× 16GB DDR4-2400)
- Samsung 970 EVO Plus 250GB NVMe
- Proxmox VE 8.4.17
- Guest: Home Assistant OS 18.1, Core 2026.7.2, running as a QEMU/KVM VM (4 vCPU, 16GB RAM, OVMF/UEFI, q35 machine type, VirtIO disk/network)
- BIOS 0044 (latest available), microcode revision 6134 (also latest)
The error, every time, identical:
systemd-coredump: Process XXXX (python3) of user 0 terminated abnormally with signal 4/ILL
Corresponding Supervisor watchdog log shows Core exiting with code 132 (128+4=SIGILL) at the same timestamp, 1:1.
What I’ve tried — all unsuccessful:
- Cold VM stop/start (to rule out stale CPUID caching)
- Three different Proxmox CPU Type settings:
host(full passthrough),x86-64-v2-AES,x86-64-v3— all produced the identical crash pattern at similar frequency - Physical RAM reseated + Memtest86+, 2 full passes on all 32GB — 0 errors
- NVMe SMART health check — clean (no media errors, no critical warnings)
- Fresh Home Assistant Core container rebuild (
ha core rebuild) — crashed again ~15 min later - Full BIOS/microcode update (0038 → 0044, microcode 4124 → 6134) — crashed again within hours
- Built a second, completely fresh HAOS VM from the official OVA image, restored from backup, moved all peripherals over — same identical crash, twice, a few hours apart — this ruled out anything specific to the old OS install/filesystem state
- Disabled a local Whisper STT add-on (in case of AVX-512-related CPU dispatch issues) — no change
- Disabled two flaky Frigate camera streams (in case of a decode-related memory corruption path) — no change
- Switched back to CPU Type
host— longest clean stretch yet (~9 hours overnight), but crashed twice again by morning
Checked the Proxmox host journal for hardware-level evidence: no MCE, no thermal throttling, one ambiguous EDAC/IBECC “memory error” log entry at first boot (matches a known igen6_edac false-positive pattern, not repeated since), and live corrected/uncorrected error counters read 0.
Where I’m at
Every layer I can influence through software, firmware, or config has been tested and ruled out — CPU virtualization settings, RAM, storage, container state, OS install, BIOS/microcode, and even application-level add-ons/cameras that touch CPU-intensive code paths. The crash signature is identical regardless of what changes. At this point it looks like a NUC13 board or CPU-level hardware issue, and I’m in the process of moving Home Assistant to older, non-hybrid-core hardware as a workaround while I pursue this with ASUS support.
Question for the community: has anyone seen SIGILL crashes like this on a hybrid P-core/E-core NUC13 (or similar 13th/14th gen Intel) running HA under Proxmox/KVM? Particularly interested if anyone has hit something similar? I don’t know where to go from here. In the past my HA installs have been rock solid with weeks of uptime.