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

    Virtualbox PXE Boot - No configuration methods succeeded

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    5
    14
    7.8k
    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.
    • A
      austin_g
      last edited by

      It’s configured as Bridged, as shown in the first screenshot.
      The FOG server is handling DHCP. It appears to be assigning IPs correctly, and the next-server is set to the FOG server ip. There aren’t any other DHCP servers on that subnet.

      1 Reply Last reply Reply Quote 0
      • Tom ElliottT
        Tom Elliott @austin_g
        last edited by

        @austin_g just because it’s booting to ipxe does not mean it should work. What boot file are you using? In the past I had to use ipxe.pxe for virtual box to work consistently. Of course other factors could cause the problem I suppose.

        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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

        1 Reply Last reply Reply Quote 0
        • A
          austin_g
          last edited by

          I’m fuzzy about that part. I see class definitions in the dhcpd.conf that FOG installs that matches against vendor-class-identifier. I’m not sure what the vendor class identifier for virtualbox would return, but looking at the dhcpd.conf, there is no default option that it would select? I’ll try setting ipxe.pxe explicitly without the class matching.

          1 Reply Last reply Reply Quote 0
          • A
            austin_g
            last edited by

            Setting it explicitly and removing the class matches did the trick, I got into the boot rom. After that, I coped back the old config, and replaced the Legacy class match filename with ipxe.pxe, and that worked also.

            Thanks!

            H 1 Reply Last reply Reply Quote 0
            • H
              Hanz @austin_g
              last edited by Hanz

              @austin_g IPXE.kpxe is needed now for VMs as this wasn’t always the case. I’ve found that recently i have run into this more frequently as of late. That (I can confirm) is the only change necessary for sure pxe boot with Virtualbox VM. Probably on Virtualbox’s end I’d imagine given the timing.

              1 Reply Last reply Reply Quote 0
              • S
                sandervg
                last edited by sandervg

                I am facing the same issue as mentioned here. With a small difference. PXE boot is working perfect on a cold boot. But when I restart my vm I get the error that no configuration method succeeded. Using ipxe.kpxe is a solution for my virtualbox vm’s but causes physical computers to stop working. I guess the best option would be to match the UUID of my vm’s in my dnsmasq.conf and send the right PXE file. But in the syslog i can only see part of my client-machine-id. Any ideas on a good solution for my problem? vendor class: PXEClient:Arch:00000:UNDI:002001 this is the same for all my machines so I can’t switch on thath.

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

                  @sandervg said in Virtualbox PXE Boot - No configuration methods succeeded:

                  PXE boot is working perfect on a cold boot. But when I restart my vm I get the error that no configuration method succeeded.

                  FWIW: I also see this in my dev environment. Its an issue with virtual box and not your environment. When this happens I just have to power off the vm to do a cold boot. It not the answer you were looking for, but I just wanted you to know its not a unique issue.

                  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!

                  Tom ElliottT 1 Reply Last reply Reply Quote 0
                  • Tom ElliottT
                    Tom Elliott @george1421
                    last edited by

                    @george1421 I’ve seen this too though the fix for me was to use ipxe.pxe with VB and no more issues with warm boot failing.

                    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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                    Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                    Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

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

                      @Tom-Elliott said in Virtualbox PXE Boot - No configuration methods succeeded:

                      I’ve seen this too though the fix for me was to use ipxe.pxe

                      Just for clarity, you are using ipxe.pxe from the fog /tftpboot directory replacing the VBox version/file? This resolves the issue?

                      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!

                      Tom ElliottT 1 Reply Last reply Reply Quote 0
                      • Tom ElliottT
                        Tom Elliott @george1421
                        last edited by

                        @george1421 I’m using ipxe.pxe as the boot file. Not replacing the version VB’s NIC’s are set too. (Though I imagine that would work well too.)

                        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! Get in contact with me (chat bubble in the top right corner) if you want to join in.

                        Web GUI issue? Please check apache error (debian/ubuntu: /var/log/apache2/error.log, centos/fedora/rhel: /var/log/httpd/error_log) and php-fpm log (/var/log/php*-fpm.log)

                        Please support FOG if you like it: https://wiki.fogproject.org/wiki/index.php/Support_FOG

                        1 Reply Last reply Reply Quote 1
                        • Tom ElliottT Tom Elliott referenced this topic on
                        • Tom ElliottT Tom Elliott referenced this topic on
                        • 1 / 1
                        • First post
                          Last post

                        189

                        Online

                        12.0k

                        Users

                        17.3k

                        Topics

                        155.2k

                        Posts
                        Copyright © 2012-2024 FOG Project