2016-05-05, 16:43
Hi,
When trying to PXE boot a (Windows 7) guest on an oVirt host, I get:
'nslookup: command not found
Could not boot image: Exec format error (http://ipxe.org/2e022001)'
The Windows entry works fine when using a Xen or VMWare hypervisor, so I suspect it is something wrong with how oVirt does it, but I'm not quite sure what could cause this. I can PXE boot Linux VMs via the same method on the oVirt host without issue, however, they do not require the nslookup or chain functions in iPXE.
In my 'default' file on my kickstart host, the entry that is failing for Windows is:
nslookup wds <?php echo $wdroot."\n"; ?>
set net0/next-server ${wds}
chain tftp://${wds}/boot\\x86\\wdsnbp.com || goto failed
goto start
An example Linux host that boots fine from the same menu:
:sl6.7-lvm
set kernel ${boot-root}/sysimages/sl6/6.7/vmlinuz
set initrd ${boot-root}/sysimages/sl6/6.7/initrd.img
set ksname /boot/kickstarts/sl6.7-lvm.ks
set imgargs ${sl6-imgargs}
goto execboot
Thanks for any pointers.
-Cam
When trying to PXE boot a (Windows 7) guest on an oVirt host, I get:
'nslookup: command not found
Could not boot image: Exec format error (http://ipxe.org/2e022001)'
The Windows entry works fine when using a Xen or VMWare hypervisor, so I suspect it is something wrong with how oVirt does it, but I'm not quite sure what could cause this. I can PXE boot Linux VMs via the same method on the oVirt host without issue, however, they do not require the nslookup or chain functions in iPXE.
In my 'default' file on my kickstart host, the entry that is failing for Windows is:
nslookup wds <?php echo $wdroot."\n"; ?>
set net0/next-server ${wds}
chain tftp://${wds}/boot\\x86\\wdsnbp.com || goto failed
goto start
An example Linux host that boots fine from the same menu:
:sl6.7-lvm
set kernel ${boot-root}/sysimages/sl6/6.7/vmlinuz
set initrd ${boot-root}/sysimages/sl6/6.7/initrd.img
set ksname /boot/kickstarts/sl6.7-lvm.ks
set imgargs ${sl6-imgargs}
goto execboot
Thanks for any pointers.
-Cam