• 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.
    • george1421G
      george1421 Moderator @ty900000
      last edited by

      @ty900000 <snarky> Yeah use VMWare instead </snarky>

      As far as I can see ipxe.efi should work with a hyper-v gen 2 uefi virtual machine. I’ve seen videos of this working.

      Can you tell me what your end game is here with pxe booting a hyper-v vm? I have a few other options in my back pocket that we may have to use depending on what your plan is.

      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

        Ha! Yeah, I had to fight to use Hyper-V in the first place…

        I work for a federal government contracting company and we have orders to harden our systems, network, infrastructure, etc by the end of the year. One of our guys already created an image of a 2016 server with a hardened baseline. I was hoping I could just blow that image to a VM, rather than use the generic ISO and rebuild all the security hardening from scratch every time we need to set up a server.

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

          @ty900000 while this is off point of your post.

          I know of a company that must compily with USGCB/STIG/NIST standards. Those policies are typically applied by GPO generally. They use MDT to build a baseline system with some of the “stuff” already in the box and configured for compliance the rest is applied by GPO.

          They use MDT to build the reference image using a virtual machine running under VMWare. Once that reference image is created on the VM, they sysprep it and power it off. (now this is a feature of VMWare so I can’t speak for Hyper-V). The shutdown VM is then turned into a VM template. When ever they need a new virtual machine they just clone the vm template to a virtual machine. No external services are required here other than MDT to build the golden image to start with. By using MDT they can refresh their vm template on some interval with the latest windows updates and STIG requirements.

          But we still should identify the proper settings to pxe boot a hyper-v vm. I know this won’t be the last time this issue comes up on the forums. UEFI is here to stay.

          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

            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

                              192

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project