Not sure where to begin here, this has been working for a very long time and even on 6.0.0, but I just upgraded to 6.0.3 and it's not coming up. When I am SSHd into the Eisy, I can poweroff and when I start in interactive mode, it goes through what seems to be a BIOS boot type of screen/sequence then goes to a screen that says Booting Slot A (OK=1 TRY=1) and just has a flashing cursor and never moves. Not sure what to do or where to go from here.

Additional info, hoping someone can help here.

sudo vm list output:

NAME           DATASTORE  LOADER  CPU  MEMORY  VNC  AUTO     STATE

homeassistant  default    uefi    2    1G      -    Yes [1]  Locked (eisy)

/etc/rc.conf file still looks like it contains the correct parameters from the 6.0.0 install.

vm_enable="YES"

vm_dir="zfs:storage/vms"

vm_list="homeassistant"

my eisy never came back after upgrade
put my polisy bak in but all kinds of prolems since
willhavt to deal with after holidays

Well after many hours of screwing around with it and a support ticket later, it's still not working and the solution is to blow away the VM and start over with hoping the HA backup works after getting it back up.

I've dug through the bhyve logs, enabled debugging and nothing is helping determine why it's just hanging upon boot. Nothing in the main log that would suggest why, nothing in the debug log either, just hangs and doesn't finish booting.

I've decided now after 2 OS updates (when I updated to 6.0.0 initially and now with 6.0.3) and a 2/2 record or breaking this HA VM, I'm moving it off of the Eisy and will build it in a Proxmox environment and move on with my life... not worth the annoyance or headache it creates. For me there are no critical automations running, I just like the dashboards I've built and overall interface way better.

2 hours ago, RCopsetta02 said:

my eisy never came back after upgrade
put my polisy bak in but all kinds of prolems since
willhavt to deal with after holidays

Well my Eisy came back up updated, so this was not my issue... it was that the VM has somehow become unhappy, even with my NVMe drive in mirror mode which you would hope might help, but I guess not. Good luck with yours, I can only imagine.