Fog setup on Hyper-V



  • Good morning everyone. I have to setup Fog in an Hyper-V environment. I installed Ubuntu Server 14.04-4 LTS and Fog 7009. The web interface is working fine. I am able to boot PXE but i am getting these message…

    • Station IP adress is x.x.x.x
    • Server IP is x.x.x.x
    • NBP filename is undionly.kpxe
    • NBP filesize is 92249 Bytes
    • Succesfully downloaded NBP file.
    • Boot Failed. EFI network. Failed Secure boot Verification
    • Boot failed. EFI SCSI Device.
    • No Operating System was loaded…
      In the past, I installed Fog server on a Physical machine, On VirtualBox and ESXi without any problem. Any help on my problem? Is is compatible? I saw many post about performance issue with Hyper-V. So i assume it is compatible? Thanks!


  • Good morning everyone! I appoligise for not replying any sooner. I did some testing and this i was able to solve my problem. I realized that i was able to PXE boot from a physical machine. Just not with a virtual machine with Windows 7 X64 in Hyper-V. I found a post that explain to use a legacy network card. I did the change and i was able to register my VM in FOG. Thank you all for your help. Incase, here is the link i found…
    https://www.petri.com/boot-hyper-v-virtual-machine-using-pxe

    Good day Yall! :)


  • Moderator

    @sfayle If you have a mix of bios and uefi then you may need to review this wiki page to help you setup the dhcp server to offer the proper boot image based on the target computer that is requesting dhcp information.
    https://wiki.fogproject.org/wiki/index.php?title=BIOS_and_UEFI_Co-Existence



  • @george1421 Ok thank you for you reply. I change option 67 to snponly.efi?
    At this time, i am trying to buid a template on a VM (Windows 7 X64) in Hyper-V. My DHCP server is in fact Server 2012.


  • Moderator

    @sfayle said in Fog setup on Hyper-V:

    Option 67 in DHCP = undionly.kpxe

    Well that is problem #1. Your target device is trying to boot EFI and you are sending it a bios boot file. (undionly.kpxe). For uefi devices you need to send snponly.efi if you want to stay with the generic driver kernel (i.e. first choice and equivalent to undionly.kpxe [bios])

    To collect a bit more information what is the target computer manufacturer and model?

    If you disable secure boot, check the network settings. You may have to enable the uefi network stack and/or legacy ROMs. Or switch the device back to bios/legacy mode if you have a mixture of bios and uefi systems. If you need to deploy to both uefi and bios systems and you have a MS 2012 dhcp server or a linux dhcp server you have a few additional options available.



  • Option 67 in DHCP = undionly.kpxe
    Option 66 in DHCP = IP adress of FOG server
    The intended target OS is Windows 7. If i disable secure boot, the PXE is not detected.


  • Moderator

    Well lets get some background information.

    1. What do you have dhcp option 67 set to?
    2. What is the intended target OS you will be deploying?

    And a check

    1. Ensure in the bios settings for this VM to disable secure boot.

Log in to reply
 

686
Online

39.3k
Users

11.0k
Topics

104.4k
Posts

Looks like your connection to FOG Project was lost, please wait while we try to reconnect.