search

churchers / vm-bhyve

Shell based, minimal dependency bhyve manager
BSD 2-Clause "Simplified" License
806 stars 168 forks source link

Issue booting HomeAssistant EFI qcow2 image #383

Open Drizzt321 opened 3 years ago

Drizzt321 commented 3 years ago

So I'm trying to get the HomeAssistant qcow2 image (https://www.home-assistant.io/hassio/installation/) to boot up fully. I'm running FreeBSD 12.1p2, latest version of all packages.

I managed to get it to start booting with the below:

vm img https://github.com/home-assistant/operating-system/releases/download/4.12/hassos_ova-4.12.qcow2.gz
vm create -t debian -c 4 -m 4GB -s 200G -i hassos_ova-4.12.qcow2 home-assistant

Edit the home-assistant/home-assistant.config and change the loader="grub" to uefi="yes" and boot.

However based on the initial output it looks like there's some kind of problem reading the partition table or the like. 


barebox 2020.04.0 #1 Thu Aug 6 20:37:21 UTC 2020

Board: barebox EFI payload
EFI v2.40 by BHYVE v65536
EFI Event timer too slow freq = 100 Hz
acpi2: Found XSDT (OEM: BHYVE BV) with 5 entries
efi-fs handle-00000000bf055698: mounted on /boot
efi-block-io handle-00000000bf282418: Cannot read MBR/partition table
malloc space: 0x30000000 -> 0x3fffffff (size 256 MiB)
state: New state registered 'state'
state: No meta data header found
state: No meta data header found
state: No meta data header found
state: Failed to find any valid state copy in any bucket
state: Failed to read state with format raw, -2
Failed to load persistent state, continuing with defaults, -2
description: EFI Hard Drive
path: pci_root(0)/Pci(0x4,0x0)/Sata(0x0,0x0,0x0)
description: EFI Network
path: pci_root(0)/Pci(0x5,0x0)/Mac(589cfc005f49,1)
description: EFI Internal Shell
path: mem_map(11,0xbfc1c000,0xbffbbfff)/Path(132,6,0x83a5047c3e9e1c4fad65e05268d0b4d100000000ffff0800)
environment load /efivars/barebox-env-5b91f69c-8b88-4a2b-9269-5f1d802b5175: No such file or directory
Maybe you have to create the partition.
running /env/bin/init...
- Hit m for menu or wait for autoboot -
Booting entry 'bootchooser'
Booting entry 'system0'
ext4 ext40: EXT2 rev 1, inode_size 128, descriptor size 32

Loading MS-DOS executable '/mnt/system/bzImage'

Here's a screen capture of it booting normally and successfully in VirtualBox home-assistant virtualbox boot

Any ideas that I poke into? Or additional logging or anything else?

Drizzt321 commented 3 years ago

Innnnteresting. Looks like it's got some weird configuration, the console output is somehow not going to the VM output, but after I changed to be based off of the Windows VNC graphics output, seems that things are now working. Weird.

Is there any way to add any kind of indicator or something that could indicate that a VNC framebuffer output would be advisable? Or is there basically no way to know that without trying it first?