VMware Cloud Community
Nylarahotep
Contributor
Contributor

CentOS 5.5 install panics on ESX 4.1

I am trying to install CentOS 5.5/64-bit on an ESX 4.1 server.  The VM itself is fairly vanilla, 4 GB of memory and about 60 GB of disk, set up as a "RHEL 5 64-bit" system.  The host is a Dell R815 w/ 128 GB memory and 2 x 12-core AMD processors.

The problem is, the CentOS crashes almost immediately.  It will load the inital splash screen, where I can specify any kernel boot options, but as soon as it tries to load the installer kernel (initrd.img) off of the install media, it panics and crashes.  I've tried tweaking various aspects of the VM configuration, as well as different boot options from the CentOS install, but all to no avail.  However, I could run the 'memtest' utility from the CentOS installer without any problems.  I've used this same ISO image to install other instances of CentOS, and I did a cksum from the command line to validate it had been transferred correctly.  I've also been able to install RHEL 5.6//64-bit on this server without issue.

The final bit of the error that I'm getting is as follows:

Call trace:
cacheinfo_cpu_callback+0x9e/0x516
cacheinfo_cpu_callback+0x123/0x516
cache_sysfs_init+0x39/0x54
init+0x1f9/0x2f7
child_rip+0xa/0x11
acpi_ds_init_one_objectd+0x0/0x80
init+0x0/0x2f7
child_rip+0x0/0x11

Code: 8b 72 40 48 8d 4c 24 1c 48 8b 7a 20 ba c4 01 00 00 e8 5f 77
RIP [<ffffffff8008192f>] cpuid4_cache_lookup+0x256/0x356
RSP <ffff810104737d60>
CR2: 000000000040
<0>Kernel panic -- not syncing: Fatal exception


I checked the memory in the physical host with a BIOS check

Call trace:
cacheinfo_cpu_callback+0x9e/0x516
cacheinfo_cpu_callback+0x123/0x516
cache_sysfs_init+0x39/0x54
init+0x1f9/0x2f7
child_rip+0xa/0x11
acpi_ds_init_one_objectd+0x0/0x80
init+0x0/0x2f7
child_rip+0x0/0x11

Code: 8b 72 40 48 8d 4c 24 1c 48 8b 7a 20 ba c4 01 00 00 e8 5f 77
RIP [<ffffffff8008192f>] cpuid4_cache_lookup+0x256/0x356
RSP <ffff810104737d60>
CR2: 000000000040
<0>Kernel panic -- not syncing: Fatal exception

Any assistance would be greatly appreciated.

Reply
0 Kudos
1 Reply
Nylarahotep
Contributor
Contributor

On further investigation, this looks like something reported in Bugzilla at https://bugzilla.redhat.com/show_bug.cgi?id=607947

Reply
0 Kudos