Operating-system: Stuck at boot menu when using VMDK image and QEMU

[move[bot]]

@pjones commented on Aug 6, 2018, 8:56 PM UTC:

I have seen a few other people asking about this issue but none have been answered.

I'm trying to boot the virtual appliance with QEMU (using OVMF for UEFI). Booting stops at the HassOS-boot menu. The only option that works is the shell option. When I try booting one of the two systems manually I get all sorts of errors:

Is there a way to get more details about why this is failing to boot? Missing file system devices?

This issue was moved by pvizeli from home-assistant/hassio#630.

[pvizeli]

Look like your kernel partition is defect and he can't load the kernel

[pvizeli]

Is that issue on last vmdk image?

[pjones]

I've tried 1.6 through 1.8 with the same results.

[chyzp]

Deleted the CDrom drive and chose option 2 in the HassOS boot menu

[pvizeli]

We need handling the disk dynamic with UEFI...

[dgz]

I ran into the same issue with a VirtualBox VM with both 1.9 and the 2.1 dev version. Deleting the CDROM drive and IDE controller that VirtualBox created by default also solved the issue for me.

Dynamic handling of connected drives sounds like a good long term fix but in the short term a note in ova.md under the Virtual Machine requirements would be helpful. Something like "vmdk must be the first attached disk on the first storage controller, delete any automatically created CDROM drives and controllers".

[bagobones]

It's not possible to remove some devices on platforms like Synology Virtualization station which has a GUI on top of KVM / QEMU.

To support virtualization, some more common disk controller, network and maybe USB drivers will be needed as well as some flexibility in the disk configuration / device configuration without failure.

[leandroscarneiro]

Hello! I've successfully booted the ova, I'm using QEMU / KVM on Fedora 27.
Here what you have to do:
1 - Install edk2-ovmf to be able to boot as UEFI
2 - Convert the VMDK to "raw":
qemu-img convert -f vmdk -O raw hassos_ova-1.11.vmdk hassos_ova-1.11.img
3 - Use the XML bellow. Note: I have a bridge interface named "br0" and my "hassos_ova-1.11.img" is placed in "/opt/HDs", you may have to adapt it to your environment.

<domain type='kvm'>
  <name>HassOS</name>
  <uuid>98390bd2-2e14-40a7-3a90-e9ab06e8abcd</uuid>
  <memory unit='KiB'>3145728</memory>
  <currentMemory unit='KiB'>3145728</currentMemory>
  <vcpu placement='static'>2</vcpu>
  <os>
    <type arch='x86_64' machine='pc-i440fx-2.10'>hvm</type>
    <bootmenu enable='yes'/>
    <loader readonly='yes' type='rom'>/usr/share/edk2/ovmf/OVMF_CODE.fd</loader>
  </os>
  <features>
    <acpi/>
    <pae/>
  </features>
  <cpu mode='host-model' check='partial'>
    <model fallback='allow'/>
  </cpu>
  <clock offset='localtime'/>
  <on_poweroff>destroy</on_poweroff>
  <on_reboot>restart</on_reboot>
  <on_crash>preserve</on_crash>
  <devices>
    <emulator>/usr/bin/qemu-kvm</emulator>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/opt/HDs/hassos_ova-1.11.img'/>
      <target dev='hda' bus='ide'/>
      <boot order='2'/>
      <address type='drive' controller='0' bus='0' target='0' unit='0'/>
    </disk>
    <controller type='usb' index='0' model='piix3-uhci'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x2'/>
    </controller>
    <controller type='pci' index='0' model='pci-root'/>
    <controller type='ide' index='0'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x01' function='0x1'/>
    </controller>
    <interface type='bridge'>
      <mac address='52:54:00:be:82:70'/>
      <source bridge='br0'/>
      <model type='e1000'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/>
    </interface>
    <input type='mouse' bus='ps2'/>
    <input type='keyboard' bus='ps2'/>
    <graphics type='vnc' port='-1' autoport='yes' listen='0.0.0.0'>
      <listen type='address' address='0.0.0.0'/>
    </graphics>
    <sound model='ac97'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
    </sound>
    <video>
      <model type='vga' vram='16384' heads='1' primary='yes'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/>
    </video>
    <memballoon model='virtio'>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/>
    </memballoon>
  </devices>
</domain>

[MwC-Trexx]

It's not possible to remove some devices on platforms like Synology Virtualization station which has a GUI on top of KVM / QEMU.

To support virtualization, some more common disk controller, network and maybe USB drivers will be needed as well as some flexibility in the disk configuration / device configuration without failure.

I am also running into the same issue with QNAP's Virtualization Station (KVM/QEMU) w/the latest 1.11 build.

UPDATE
I figured out a work around for this. 1st install and configure the VMDK image in VirtualBox w/EFI bios. Then export the VM from VirtualBox and import into QNAP's Virtualization Station. This will resolve the EFI bios boot issue.

Other ISSUE:

Due to lack of virtio Storage driver, cannot make a LIVE backup of the VM.

[bagobones]

Looks like it is possible to boot now in 1.12 of hassos however that is using the IDE or SATA drive emulator.. For somereason the VirtIO network driver works but it would not boot with the VirtIO disk controller. More testing needed but it might be usable now for testing.

Also appears to correctly detect the USB 3 hardware if enabled.

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.