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

    Kernel for Hyper-V

    Scheduled Pinned Locked Moved
    Hardware Compatibility
    3
    16
    6.5k
    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.
    • K
      kpourmand
      last edited by

      Indeed it is.

      1 Reply Last reply Reply Quote 0
      • K
        kpourmand
        last edited by

        So, I upgraded and now things still don’t work, but are a bit different.

        First, I tried copying the old bzImage file from the old install, but it will not work with the new install (I confirmed it worked on the old install earlier today). It has the error “kernel panic – not syncing, no init found.”

        Second, I tried the default kernel from the upgrade. It doesn’t work, but I get a different error than before. It says “BUG: using smp_processor_id() in preemptible [00000000] code:ntfsresize/”

        Any thoughts?

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

          [quote=“kpourmand, post: 33693, member: 172”]So, I upgraded and now things still don’t work, but are a bit different.

          First, I tried copying the old bzImage file from the old install, but it will not work with the new install (I confirmed it worked on the old install earlier today). It has the error “kernel panic – not syncing, no init found.”

          Second, I tried the default kernel from the upgrade. It doesn’t work, but I get a different error than before. It says “BUG: using smp_processor_id() in preemptible [00000000] code:ntfsresize/”

          Any thoughts?[/quote]

          The reason you got kernel panic – not syncing, no init found is because the kernel you installed in place of the original bzImage is 32 bit, where FOG now separates between 64bit and 32bit. The natural bzImage is now a 64bit image and loads with a 64bit init.xz file. If you copied your old kernel, chances are it is 32bit kernel trying to boot a 64bit init which will panic as the init doesn’t exist for that kernel to load. The same works in reverse (meaning 64bit kernel and 32bit init).

          I still have a theory as to the “smp_process_id()” error though I can’t do anything until later today.

          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
          • K
            kpourmand
            last edited by

            Very interesting. Is there a way to change the init file to 32 bit to match the kernel? How does that work if you download one of the 32 bit kernels available? Or are those only meant for 32 bit servers?

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

              The kernels that you use are simple designed to run on the clients. You can run both bit’s on your server as your server is not booting to those kernels, they’re simply for the clients.

              You should never need to use a 32 bit kernel in place of a 64 bit kernel. You actually lose support for things jumping down from 64 to 32. That said, if you’re mindset on trying 32 bit only, simply rename the init_32.xz file to init.xz and rename the bzImage32 to bzImage.

              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
              • K
                kpourmand
                last edited by

                Gotcha. I would prefer to keep the 64 bit to retain the extra features, but if it turns out that dropping to 32 bit would enable the old bzImage to work with Hyper V, then I’ll take that.

                1 Reply Last reply Reply Quote 0
                • K
                  kpourmand
                  last edited by

                  Also, am I correct in assuming the 32 bit kernel is required for 32 bit clients? Because I still have a small collection of 32 bit machines.

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

                    It autodetects

                    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
                    • K
                      kpourmand
                      last edited by

                      Oh wow…that’s pretty cool.

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

                        Yeah, that’s why I hesitate to have people change the kernel and init file names.

                        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
                        • K
                          kpourmand
                          last edited by

                          I understand. FWIW, switching to the old bzImage and 32bit init file appears to make my Hyper-V server work again. I’m uploading a new image right now.

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

                          178

                          Online

                          12.1k

                          Users

                          17.3k

                          Topics

                          155.4k

                          Posts
                          Copyright © 2012-2024 FOG Project