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

Hyper-V virtual machine image hanging at init.xz... ok

Scheduled Pinned Locked Moved Solved
FOG Problems
4
11
931
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.
  • S
    Sebastian Roth Moderator
    last edited by Oct 29, 2019, 4:14 PM

    @holydonut From the title of your post it sounds like it could be a newer kernel causing the hang.

    Which FOG version did you use before the server rebuild? Which version do you use now?

    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
    • H
      holydonut
      last edited by Oct 29, 2019, 6:08 PM

      I can’t recall the FOG version before the server rebuild. We’re on the following version.

      Estimated FOG Sites:4290

      Latest Version:1.5.7

      Latest Development Version:1.5.7.47

      Latest SVN Version:6078

      1 Reply Last reply Reply Quote 0
      • S
        Sebastian Roth Moderator
        last edited by Sebastian Roth Oct 29, 2019, 12:35 PM Oct 29, 2019, 6:31 PM

        @holydonut I had forgotten about this but I think you might run into the issue described here: https://forums.fogproject.org/topic/11348/hyper-v-and-pxe-boot-to-fog-problems

        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

        P 1 Reply Last reply Oct 31, 2019, 12:36 AM Reply Quote 0
        • S
          Sebastian Roth Moderator
          last edited by Oct 29, 2019, 6:36 PM

          @holydonut Probably another regressing caused by Microsoft as described here: http://forum.ipxe.org/showthread.php?tid=10998

          Do you have all the latest updates for 1803 installed???

          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
          • G
            george1421 Moderator
            last edited by Oct 30, 2019, 8:36 PM

            FWIW I spun up a Hyper-V VM on Windows 2016 DataCenter server and it pxe booted correctly with a UEFI VM. Imaging rates are not quite a good as vSphere, but the 2016 DC server is running as a VM under vSphere so it was a vm inside a vm. The settled transfer rates were about 7.2GB/m vs 13GB/m under vSphere on the same physical VM host. So at least with Hyper-V on 2016 DataCenter we are not seeing the slow imaging speeds or the hangs we are seeing with Win10 Hyper-V. If I have time this week I’ll spin up a Win10 1903 install and enable Hyper-V to see if I get similar results on a Dell o7050.

            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!

            1 Reply Last reply Reply Quote 0
            • H
              holydonut
              last edited by Oct 30, 2019, 8:52 PM

              thanks for the help guys. I built a new image with Windows 10 1903 with latest updates and it also hangs at init.xz

              G 1 Reply Last reply Oct 31, 2019, 2:54 PM Reply Quote 0
              • S
                Sebastian Roth Moderator
                last edited by Oct 30, 2019, 10:29 PM

                @holydonut We are not talking about the OS in the VM but the Windows running HyperV!

                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
                • P
                  Paulman9 @Sebastian Roth
                  last edited by Paulman9 Oct 30, 2019, 6:38 PM Oct 31, 2019, 12:36 AM

                  @Sebastian-Roth Not saying this isn’t related to the issue I had previously, however, the issues I had caused the image to stall at ipxe initializing devices. Sounds like @holydonut is making it past that to stall at init.xz. This a bootfile issue? @holydonut are you sure you are uefi network booting other machines to fog?

                  1 Reply Last reply Reply Quote 0
                  • G
                    george1421 Moderator @holydonut
                    last edited by george1421 Oct 31, 2019, 8:55 AM Oct 31, 2019, 2:54 PM

                    @holydonut Well I don’t have good news for you, because I just stood up a win10 1903 Pro CBB machine and the VM boots into the fog menu and compatibility check under hyper-v without issue. Now understand there may be windows updates pending. But on a fresh build it works out of the box.
                    fog_cli_vm_hyperv.png

                    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!

                    G 1 Reply Last reply Oct 31, 2019, 5:12 PM Reply Quote 1
                    • G
                      george1421 Moderator @george1421
                      last edited by george1421 Oct 31, 2019, 11:33 AM Oct 31, 2019, 5:12 PM

                      @george1421 After fully patching the workstation it still run compatibility ok. I didn’t try imaging before but I completed imaging the VM after the update and it imaged but threw a strange error:
                      pc_img_err.png

                      It almost looks like a core dump but the system kept imaging. I have noticed several times that in the percent complete line it will post a message about balloon request will be partially <something>. And then several seconds later balloon floor reached. On both esxi and now on hyper-v. But I think that is a topic for a different thread and a different time.

                      Edit: Irrelevant follow up. I noticed that 4.19.48 was listed on the screen shot so I confirmed the version of bzImage and it was indeed 4.19.48. I put back 4.19.64 (which was shipped with fog 1.5.7 and that CPU core dump did not come back on a system reimage. So its possible the older bzImage had issues that were resolved in 4.19.64.

                      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!

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

                      196

                      Online

                      12.0k

                      Users

                      17.3k

                      Topics

                      155.2k

                      Posts
                      Copyright © 2012-2024 FOG Project