iPXE discussion forum
BUG in undionly.kpxe - Printable Version

+- iPXE discussion forum (https://forum.ipxe.org)
+-- Forum: iPXE user forums (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: BUG in undionly.kpxe (/showthread.php?tid=7215)

BUG in undionly.kpxe - Alphakarem - 2014-02-26 00:37

I have came across a bug in undionly.kpxe ( the latest version ) and would like to draw your attention to it if I may, here is the situation :

OS : Centos 6.5 as a KVM Host
Hardawre : DELL Poweredge 2950

OS : Centos 6.5 as a KVM Host
Hardawre : SuperMicro

issue :
When trying to boot a VM from iPXE on the DELL it causes the VM to enter a Paused state where it will not be reset.

Troubleshooting steps :
1-) New VM was created with new HDD on both hosts.
2-) Trying boot from the SuperMicro Host ( Issue DOESN'T exist )
3-) Trying to boot from the DELL Host ( Issue EXISTS )
4-) Booting from the older version of undionly.kpxe on both hosts works well.
5-) Booting from VMware Workstation ( Issue DOESN'T Exist )

Please look into this issue and let me know what is it and how to remedy it.
right now I am just using the older version of undionly.com

Thank you

RE: BUG in undionly.kpxe - robinsmidsrod - 2014-02-28 08:58

Have you tried using ipxe.pxe instead of undionly.kpxe? It could be a problem in your BIOS PXE implementation, which undionly.kpxe is using. If so, you should verify you're using the latest BIOS firmware on the machines. You should also try to go through the checklist at http://ipxe.org/dev/driver to ensure the driver you're using actually works consistently. The link tests can be a bit tricky to do on VMs.

RE: BUG in undionly.kpxe - Alphakarem - 2014-02-28 14:35

Thank you for your response, I should have mentioned that both hosts are on the latest firmware.

Also, if this was an issue with the BIOS or drivers or such ... why would the older version work and the newer one doesn't ?

RE: BUG in undionly.kpxe - robinsmidsrod - 2014-03-03 11:15

There was a fix to a regression issue on the DNS code updated a few days ago. Have you retried with the latest head of the master branch?