iPXE discussion forum
AMD Hyper-V fails to load iPXE ISO - Printable Version

+- iPXE discussion forum (https://forum.ipxe.org)
+-- Forum: iPXE user forums (/forumdisplay.php?fid=1)
+--- Forum: General (/forumdisplay.php?fid=2)
+--- Thread: AMD Hyper-V fails to load iPXE ISO (/showthread.php?tid=8011)



AMD Hyper-V fails to load iPXE ISO - jeremyherrmann - 2016-04-05 22:07

Strange question here...

We have 3 Hyper-V Clusters running 2012 R2. Two clusters run Intel Processors and one runs AMD processors. When we try to boot a Hyper-V VM (Gen 1 or Gen 2, Legacy or Standard NIC), the iPXE ISO loads properly. However, when we try the same configuration on the AMD environment it hangs at "iPXE initializing devices....".

We've tried every configuration on the Hyper-V VM that we can think of and we can't get past this. We were able to get a gPXE ISO to boot to a Hyper-V Gen1 VM with a Legacy adapter on the AMD hypervisor.

Any thoughts or suggestions?


RE: AMD Hyper-V fails to load iPXE ISO - mcb30 - 2016-07-10 21:14

(2016-04-05 22:07)jeremyherrmann Wrote:  We have 3 Hyper-V Clusters running 2012 R2. Two clusters run Intel Processors and one runs AMD processors. When we try to boot a Hyper-V VM (Gen 1 or Gen 2, Legacy or Standard NIC), the iPXE ISO loads properly. However, when we try the same configuration on the AMD environment it hangs at "iPXE initializing devices....".

We've tried every configuration on the Hyper-V VM that we can think of and we can't get past this. We were able to get a gPXE ISO to boot to a Hyper-V Gen1 VM with a Legacy adapter on the AMD hypervisor.

This may be worked around by http://git.ipxe.org/ipxe.git/commitdiff/74222cd.

It's a pretty obscure problem: it seems that the emulated RTC interrupt mechanism in Hyper-V is simply broken. The RTC registers show that it is generating IRQ8, but the PIC registers show that nothing is generating IRQ8. Consequently, iPXE locks up waiting indefinitely for IRQ8 to happen. I can't tell if it's a bug in the RTC emulation or a bug in the PIC emulation, and I have no idea why it seems to affect only AMD hardware.

Michael