RHHI-V VM Failed to start no bootable device

Latest response

Similar error to https://access.redhat.com/solutions/3024861 but resolution did not help.

Deployed on RHHI-V for single node using RHHI-V
Using Glusterfs 3.12.2 for hyper convergence

Successfully deployed Glusterfs and Hosted engine has been installed and VM is functioning. Gluster created three associated volumes for data, vmstore and engine.

gluster volume info | grep -i Name Volume Name: data Volume Name: engine Volume Name: vmstore

Storage domains are all active (see attached image) and logical network was created for gluster traffic (Section 5.1 "Create the logical network for gluster traffic" of deploying RHHI-V on a single node).

When creating a VM, a Virtio-SCSI drive is selected from the "data" storage domain and is checked as bootable, similarly a nic is selected for the default ovirtmgmt network bridge. The VM is successfully created and a new storage disk is correctly added and listed in Storage->disks with a status "OK"

The VM launches successfully and a console is downloadable however the VM operating system does not work and the terminal displays:

Booting from Hard Disk . . . Boot failed: not a bootable disk No bootable device."

I suspect I'm missing some configuration for the gluster storage network and somehow creating an interface on that storage network which is exposed to the VM? I tried changing the gluster storage network's profile to enable "VM network" and adding an interface to that network but that didn't help either.


I think this can sometimes happen when the bootable disk isn't listed first in the VM's boot order. Try editing the VM's boot order, under Advanced Options on the Details pane.

Thanks for responding Laura. I've only created a single drive for the VM using the cockpit console and I've ensured that the drive is bootable and selected first in the boot order under advanced options. I also enabled the menu to select boot device which correctly lists a virtio disk PCI:00:06.0 as the first boot device so I'd assume that the virtio-block device is being created correctly by Gluster and is listed in Storage->Disks unfortunately when trying to start the VM it still fails to boot and reports that the drive is not a bootable disk.

With Redhat virtualization host does it automatically download/provide the operating system images (e.g for Rhel 7.6) to be used for the VMs? I was wondering if perhaps I need to upload my own images...

Ah, yes, that's probably the problem. I think you'll need to upload an image for the VM to use and then install it, but looking at the documentation there doesn't seem to be a direct statement about that. I'll get in touch with the docs team and see what I can do.

In the meantime, the instructions I have are here: https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.3/html-single/virtual_machine_management_guide/index#Installing_Red_Hat_Enterprise_Linux_Virtual_Machines

Jaco, I believe that you're right about needing to first upload an OS image to a storage domain (try a data domain) before you can select that OS when creating a virtual machine. We're looking into it now.

There are several possible approaches to creating a VM with a bootable OS.

  • Creating a Cloned Virtual Machine Based on a Template
  • Create a new VM with a local boot disk managed by RHV that contains the OS and application binaries. (recommended)
  • Create a VM. Then use Run Once to boot the VM from an ISO file in the ISO library (Use the Attach CD option with the ISO file) or data domain.

I will be updating our documentation to make the two last bullets clearer.

Based on your current RHV cluster, do you prefer a particular approach? If so, I'll focus on providing that information first.

I usually boot my VMs from PXE images available on the network. So this is another option here.