• Recent
    • Unsolved
    • Tags
    • Popular
    • Users
    • Groups
    • Search
    • Register
    • Login

    FOG UEFI Boot Hyper-V 2016

    Scheduled Pinned Locked Moved Solved
    General Problems
    uefi hyper-v
    6
    33
    13.1k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      ty900000 @george1421
      last edited by

      @george1421

      Okay, yeah. I just did a quick Google and Hyper-V can make templates akin to VMWare’s operation. (I’m new to Hyper-V, myself) That may be our best option going forward. Thanks for the tip.

      And, it is possible our network is wonky. I’m the same guy from the Multicast being really slow issue: https://forums.fogproject.org/topic/10017/fog-server-cpu-requirements. So, it wouldn’t surprise me if 99% of the world had this working and my company is part of the 1% with a bad network setup.

      But, yeah. If this is a more common issue than just me, I’m more than willing to help in any way I can with it.

      T 1 Reply Last reply Reply Quote 0
      • T
        ty900000 @ty900000
        last edited by ty900000

        @george1421

        I tested the UEFI boot with a physical laptop, a brand new Dell Latitude E5570 and I got this iPXE error.

        0_1494010692868_20170505_145232.jpg

        I took a video of it as it was PXE booting and did confirm it picked up the ipxe.efi configuration file from DHCP.

        I went to that website and it just says try the latest version of iPXE. Is this just an iPXE error and not a FOG error?

        It does copy an image down just fine when I boot from legacy NIC.

        I’m sorry for being such a hassle with all this!

        george1421G 1 Reply Last reply Reply Quote 0
        • george1421G
          george1421 Moderator @ty900000
          last edited by

          @ty900000 Well that was one check I was going to ask you to try.

          I’m a bit supersized that it is sending the 32 bit FOS stuff to the target computer. The 5570 should be a 64 bit system. The error message was basically the hand off between iPXE (ipxe.efi) and FOS (bzImage32) failed.

          Are we forcing the 32 bit kernels for some reason on this host or in the global settings. Its not like iPXE to pick the wrong kernels for booting.

          Please help us build the FOG community with everyone involved. It's not just about coding - way more we need people to test things, update documentation and most importantly work on uniting the community of people enjoying and working on FOG!

          T 1 Reply Last reply Reply Quote 0
          • T
            ty900000 @george1421
            last edited by

            @george1421

            No, I haven’t made any changes to force 32 bit anything to anything else. Where would I look to double check?

            1 Reply Last reply Reply Quote 0
            • sudburrS
              sudburr @ty900000
              last edited by

              @ty900000 I’m currently running 1.4.0-RC-4 and I just tested on both types of VMs for this reply and they work.
              Gen1 (Legacy) picks up undionly.kpxe and Gen2 (UEFI) pulls down ipxe.efi on Hyper-V 2016 VMs .

              [ Standing in between extinction in the cold and explosive radiating growth ]

              T 1 Reply Last reply Reply Quote 1
              • T
                ty900000 @sudburr
                last edited by

                @sudburr

                Nice… At this point, it really doesn’t surprise me that it seems to work for everyone else since our network infrastructure is so old and unmanageable.

                1 Reply Last reply Reply Quote 0
                • T
                  ty900000
                  last edited by

                  @Psycholiquid

                  Did you happen to have any luck with Hyper-V 2016 this weekend? I’m in the process of setting up a testing environment at my company, but wanted to see if you had any luck. Thanks!

                  PsycholiquidP 1 Reply Last reply Reply Quote 0
                  • PsycholiquidP
                    Psycholiquid Testers @ty900000
                    last edited by

                    @ty900000 negative. Real life got in the way once again sorry.

                    T 1 Reply Last reply Reply Quote 0
                    • T
                      ty900000 @Psycholiquid
                      last edited by

                      @Psycholiquid

                      That’s cool; I understand.

                      1 Reply Last reply Reply Quote 0
                      • T
                        ty900000
                        last edited by

                        I just wanted to post to close this out.

                        I got a test environment working with better switches and FOG was able to pass 64-bit UEFI traffic correctly the first time, every time. Thanks all for the big help! I really appreciate it!

                        1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 2 / 2
                        • First post
                          Last post

                        196

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project