• Recent
  • Unsolved
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Register
  • Login
  • 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 May 26, 2017, 11:21 PM

    Server
    • FOG Version: 1.4.0
    • OS: Ubuntu 17.04
    Client
    • Service Version:
    • OS:
    Description

    I have Virtualbox 5.1.22 with the extension pack installed. Host OS is Windows 10 Pro 64-bit. Trying to register a Guest OS image with Windows 7 Pro 64-bit.
    I’m new to FOG and haven’t had PXE booting working correctly yet.

    The network is 10.1.10.0/24 and has an unmanaged netgear switch, with only the router, FOG server, and Virtualbox Host machine on it.
    The FOG server is on 10.1.10.9 and configured to serve DHCP. Virtualbox is 10.1.10.100. Guest OS is using a bridged network interface, and gets an IP from FOG when it boots from the HD.

    I originally had FOG 1.3.5 stable, and it had this error: No configuration methods succeeded.
    I upgraded to FOG 1.4.0 stable today, and it appears to have the same problem.

    0_1495840787778_virtualbox-net-config.png
    0_1495840799082_virtualbox-pxe.png

    I’m unsure what to try next. Thanks in advance.

    1 Reply Last reply Reply Quote 0
    • T
      Tom Elliott
      last edited by May 27, 2017, 12:33 AM

      Either change the VirtualBox boot rom to use ipxe, or you have to power off, and power on.

      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 May 27, 2017, 12:53 AM

        It is booting into iPXE as shown in the second screenshot, unless you mean something else?

        I have tried powering off the VM and powering it on a few times (not reboot) and it always has that error.

        T 2 Replies Last reply May 27, 2017, 12:55 AM Reply Quote 0
        • T
          Tom Elliott @austin_g
          last edited by May 27, 2017, 12:55 AM

          @austin_g Is the VM setup with a “NAT” nic or “Bridged” nic?

          What’s providing DHCP to the VM?

          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 May 27, 2017, 3:04 AM

            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
            • T
              Tom Elliott @austin_g
              last edited by May 27, 2017, 5:59 AM

              @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 May 27, 2017, 4:21 PM

                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 May 27, 2017, 9:54 PM

                  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 Jun 21, 2017, 10:28 PM Reply Quote 0
                  • H
                    Hanz @austin_g
                    last edited by Hanz Jun 21, 2017, 4:30 PM Jun 21, 2017, 10:28 PM

                    @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 May 7, 2019, 2:28 AM May 7, 2019, 8:25 AM

                      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.

                      G 1 Reply Last reply May 7, 2019, 11:54 AM Reply Quote 0
                      • G
                        george1421 Moderator @sandervg
                        last edited by May 7, 2019, 11:54 AM

                        @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!

                        T 1 Reply Last reply May 7, 2019, 12:48 PM Reply Quote 0
                        • T
                          Tom Elliott @george1421
                          last edited by May 7, 2019, 12:48 PM

                          @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

                          G 1 Reply Last reply May 7, 2019, 1:14 PM Reply Quote 0
                          • G
                            george1421 Moderator @Tom Elliott
                            last edited by May 7, 2019, 1:14 PM

                            @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!

                            T 1 Reply Last reply May 7, 2019, 1:22 PM Reply Quote 0
                            • T
                              Tom Elliott @george1421
                              last edited by May 7, 2019, 1:22 PM

                              @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
                              • T Tom Elliott referenced this topic on Aug 30, 2023, 10:18 AM
                              • T Tom Elliott referenced this topic on May 10, 2024, 10:53 AM
                              • 1 / 1
                              • First post
                                Last post

                              176

                              Online

                              12.0k

                              Users

                              17.3k

                              Topics

                              155.2k

                              Posts
                              Copyright © 2012-2024 FOG Project