#@benish I converted your message into a

1 messages · Page 1 of 1 (latest)

sour sorrel
#

Please also share some information about your VM host system, like free/used memory and the VM info like memory aallocated to it and such.

Does this screen capture have the info you're talking about: https://go.benish.io/lg4h0HjN
?

#

I'd recommend you check the last few lines of the last boot log:

ha host logs -b -1 has this at the end:

2024-06-04 22:23:16.602 homeassistant kernel: Sending NMI from CPU 2 to CPUs 1:
2024-06-04 22:23:16.602 homeassistant systemd[1]: systemd-udevd.service: Processes still around after final SIGKILL. Entering failed mode.
2024-06-04 22:23:16.603 homeassistant systemd[1]: systemd-udevd.service: Failed with result 'watchdog'.
2024-06-04 22:23:16.603 homeassistant systemd[1]: systemd-udevd.service: Unit process 156 (systemd-udevd) remains running after unit stopped.
2024-06-04 22:23:16.611 homeassistant systemd[1]: systemd-udevd.service: Consumed 16.365s CPU time.
2024-06-04 22:23:16.611 homeassistant systemd[1]: systemd-udevd.service: Scheduled restart job, restart counter is at 1.
2024-06-04 22:23:16.611 homeassistant systemd[1]: systemd-udevd.service: Found left-over process 156 (systemd-udevd) in control group while starting unit. Ignoring.
2024-06-04 22:23:16.611 homeassistant systemd[1]: systemd-udevd.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
#

I'm not totally sure if that's the relevant one – here's the other things I see from ha host logs boots:

  "-1": 99139d90943e4e67846b5b699b1c85ea
  "-2": 75d9f98eaa9a457f9376de690e2c0fb1
  "-3": 417f8891a9e34ad4a6e0a10119509956
  "-4": 0ab8cccd91cd489bab5ef314dea8ad6d
  "-5": e51ba4bc523f4b07bc33547e33143edb
  "-6": 11054d09e45c433bb440d479eb9bc12b
  "-7": 245cfd9b1c7d4e8a8ba645cfc99ecc85
  "0": 802b99de64b94de1b318a3f06ee6f13a
#

I'm guessing 0 is the most recent and -1 is the one before, which should've been in the midst of the problem (assuming that reverting Z-Wave JS UI resolved it)

#

but I have no idea what I'm doing, if that's not obvious 🙃

topaz rivet
#

It should be but I'm not sure why it's formatted/ordered that weird.

#

You'll only see something in the log if the VM wasn't killed very harshly. You might be able to tell by the time.

#

Wow. 32G is totally overkill. 4G is more than enough.

#

How much memory does the host system have? The one that's running the VM.

sour sorrel
#

How much memory does the host system have?
It's an old MacPro with 64 GB of memory; nowadays the machine's sole purpose is Home Assistant, an NVR (Security Spy), and a Plex server (rarely used). So I probably gave it an absurd amount of memory because I could. ¯_(ツ)_/¯

#

I still have 18 GB of memory available, even with the absurd amount allocated to VirtualBox / Home Assistant