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

    Kernel Panic with SVN 3553 and virtual ESXi-Image

    Scheduled Pinned Locked Moved Solved
    FOG Problems
    4
    11
    4.7k
    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.
    • tomtomT
      tomtom
      last edited by

      With fog 1.20 on debian 7 i was able to clone a virtual (esxi) windows (working with virutal ide- and scsi-drive).
      Whe I’m trying to do so with svn 3553 on debian 8, i’m getting the following error, when trying to register the virtual host (full host registration and inventory):
      kernel-panic.png
      Other (real) computers I can register with svn 3553 on debian 8.

      1 Reply Last reply Reply Quote 0
      • tomtomT
        tomtom
        last edited by

        @Jbob
        Yes, its windows 8.1.
        But i don’t think, that it has to do something with the version of windows.

        I want to add, that i also tried different kernels…

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

          IT does have something to do with the OS’s particularly from the way the VM sets up the host for the particular OS. You could, create a new vm but keep it’s OS level at Windows 7, and still install Windows 8 on it.

          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
          • tomtomT
            tomtom
            last edited by

            @Tom Hey Tom, thanks for replying!
            But why can i handle the same (!) vm-image with fog 1.2.0 and not with svn 3553?

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

              I don’t know what you mean? Di dyou attempt updating the kernel, but gave the wrong name?

              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
              • tomtomT
                tomtom
                last edited by

                No, with image a meant the windows-image.

                But: HAAA! I found it!
                On the SVN 3553 I always just tried some of the very new kernels (Fog-Configuration > Kernel-Update).
                When I select an older one (I took 3.0.1), then it works!

                Is there a reason, why the newer kernels (like 4.0.4) don’t support the VM-Images?
                Can I help by giving you a list of the virtual hardware the esxi applied to the machine?

                Thank to all the great work!

                Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                • Wayne WorkmanW
                  Wayne Workman @tomtom
                  last edited by

                  @tomtom said:

                  No, with image a meant the windows-image.

                  But: HAAA! I found it!
                  On the SVN 3553 I always just tried some of the very new kernels (Fog-Configuration > Kernel-Update).
                  When I select an older one (I took 3.0.1), then it works!

                  Is there a reason, why the newer kernels (like 4.0.4) don’t support the VM-Images?
                  Can I help by giving you a list of the virtual hardware the esxi applied to the machine?

                  Thank to all the great work!

                  Yes, please provide any info you have on your ESXi machines configured for FOG.

                  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!
                  Daily Clean Installation Results:
                  https://fogtesting.fogproject.us/
                  FOG Reporting:
                  https://fog-external-reporting-results.fogproject.us/

                  1 Reply Last reply Reply Quote 0
                  • tomtomT
                    tomtom
                    last edited by

                    Here is the full inventory report of the virtual (esxi) windows 8.1:

                    Host ID : 1
                    Host name : win8.1-ent-x64
                    Host MAC : 00:0c:29:…
                    Host Desc : Created by FOG Reg on June 18
                    Image ID : 2015
                    Image Name : 4:50 pm
                    Image Desc : 2
                    OS Name : win10-test
                    Inventory ID :
                    Inventory Desc :
                    Primary User : 1
                    Other Tag 1 :
                    Other Tag 2 :
                    System Manufacturer :
                    System Product :
                    System Version : VMware
                    System Serial : Inc.
                    System Type : VMware Virtual Platform
                    BIOS Version : None
                    BIOS Vendor : VMware-56 4d 9f 5a db d9 cb f7-52 1b 88 3e 3a 45 d3 7e
                    BIOS Date : Type: Other
                    MB Manufacturer : 6.00
                    MB Name : Phoenix Technologies LTD
                    MB Version : 07/30/2013
                    MB Serial : Intel Corporation
                    MB Asset : 440BX Desktop Reference Platform
                    CPU Manufacturer : None
                    CPU Version : None
                    CPU Speed : Not Specified
                    CPU Max Speed : GenuineIntel 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000000000000 000
                    Memory : Intel® Xeon® CPU E5606 @ 2.13GHz Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Processor Unknown Process
                    HD Model : Current Speed: 2133 MHz
                    HD Firmware : Max Speed: 30000 MHz
                    HD Serial : 3.86 GB
                    Chassis Manufacturer :
                    Chassis Version :
                    Chassis Serial :
                    Chassis Asset : No Enclosure

                    1 Reply Last reply Reply Quote 2
                    • T
                      Tim.Trageser
                      last edited by

                      I am having a similar issue. With VMware Workstation 11. Are there any significant drawbacks to using the older Kernel? I don’t want to break my Win 7 imaging capabilities.

                      Wayne WorkmanW 1 Reply Last reply Reply Quote 0
                      • Wayne WorkmanW
                        Wayne Workman @Tim.Trageser
                        last edited by

                        @Tim.Trageser

                        It’s possible to configure a host to use a particular kernel. Right on the Host Manaagement page, pick the virtual machine, and then just go to the “general” area. There’s a spot for the kernel to use, along with other stuff.

                        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!
                        Daily Clean Installation Results:
                        https://fogtesting.fogproject.us/
                        FOG Reporting:
                        https://fog-external-reporting-results.fogproject.us/

                        1 Reply Last reply Reply Quote 0
                        • T
                          Tim.Trageser
                          last edited by

                          @Wayne-Workman That is great! I will try it and see if it works thanks.

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

                          216

                          Online

                          12.0k

                          Users

                          17.3k

                          Topics

                          155.2k

                          Posts
                          Copyright © 2012-2024 FOG Project