UPDATE 2:
UPDATE 1:
Although it took much longer the host reboot to occur, but it also happened when HAOS was not running.
ORIGINAL POST:
My Proxmox host reboots randomly, and it is caused by an homeassistant VM. Removed passing of bluetooth chipset and Sonoff Zigbee usb, but that doesn't prevent crashing. Memory usage of VM is approx. 1.9 GB of 2 GB ram, but memory shortage should crash the VM and not the host. CPU is also set to a virtualized one instead of host CPU.
As a side note I had to disable certain features on the Intel nic's of the host to prevent nic's from disconnecting, but that workaround is already in place for years, and I suppose not related.
Macamba
Code:
root@lab:~# journalctl -b -1 -k -p warning
Oct 28 13:27:00 lab kernel: GDS: Mitigation locked. Disable failed.
Oct 28 13:27:00 lab kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Oct 28 13:27:00 lab kernel: nvme nvme1: missing or invalid SUBNQN field.
Oct 28 13:27:00 lab kernel: nvme nvme2: missing or invalid SUBNQN field.
Oct 28 13:27:00 lab kernel: nvme nvme0: missing or invalid SUBNQN field.
Oct 28 13:27:00 lab kernel: spl: loading out-of-tree module taints kernel.
Oct 28 13:27:00 lab kernel: zfs: module license 'CDDL' taints kernel.
Oct 28 13:27:00 lab kernel: Disabling lock debugging due to kernel taint
Oct 28 13:27:00 lab kernel: zfs: module license taints kernel.
Oct 28 13:27:00 lab kernel: faux_driver regulatory: Direct firmware load for regulatory.db failed with error -2
Oct 28 13:27:00 lab kernel: spi-nor spi0.0: supply vcc not found, using dummy regulator
Oct 28 13:27:07 lab kernel: nvme nvme0: using unchecked data buffer
Oct 28 13:27:18 lab kernel: kauditd_printk_skb: 115 callbacks suppressedUPDATE 1:
Although it took much longer the host reboot to occur, but it also happened when HAOS was not running.
ORIGINAL POST:
My Proxmox host reboots randomly, and it is caused by an homeassistant VM. Removed passing of bluetooth chipset and Sonoff Zigbee usb, but that doesn't prevent crashing. Memory usage of VM is approx. 1.9 GB of 2 GB ram, but memory shortage should crash the VM and not the host. CPU is also set to a virtualized one instead of host CPU.
As a side note I had to disable certain features on the Intel nic's of the host to prevent nic's from disconnecting, but that workaround is already in place for years, and I suppose not related.
Macamba
Last edited: