Kernel Panic with SVN 3553 and virtual ESXi-Image
-
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):
Other (real) computers I can register with svn 3553 on debian 8. -
@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…
-
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.
-
@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? -
I don’t know what you mean? Di dyou attempt updating the kernel, but gave the wrong name?
-
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!
-
@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.
-
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 -
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.
-
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.
-
@Wayne-Workman That is great! I will try it and see if it works thanks.