For clarification, I'm running Version 4.2.3.5-1.el7.centos of oVirt.
Foreman is using oVirt as a compute resource and creating the VM for me.
By default it sets the first boot device as *Network (PXE)* and the second
as *Hard Disk*. Additionally, when I disable my dhcp server and allow iPXE
to timeout, it still says "No bootable device". If I switch the boot order
in the vm settings, having it boot from Hard Disk first, there are no
issues and the system boots.
This leads me to believe that oVirt/qemu is not honoring the Second boot
device. And suggestions on how to remedy this?
Sorry for the lack of detail (thank you Yedidyah) in my initial message.
Regards,
Mike
On Wed, Jul 11, 2018 at 12:19 AM, Michael Deffenbaugh <mike(a)zeroent.net>
wrote:
Hey all,
Provisioning a host with Foreman 1.17.1/Katello 3.6. The host
kickstarts fine but when it goes to reboot, iPXE fails to load the local
disk when the Foreman local boot kickstart menu (
https://github.com/
theforeman/community-templates/blob/develop/provisioning_templates/
snippet/pxelinux_chainload.erb, line 4-10) sends the command "LOCALBOOT
0". It simply fails and says "No more network devices. No bootable
device."
Is this a bug in iPXE? Any input would be greatly appreciated!
Regards,
Mike