VMkernel failed to initialize after install

[HKWP]

Hi,

Since here is the problem:

I installed ESX 3.5 U3 on a IBM x3850M2 with 4 six cores processor. The installation completed but the VMkenerl failed to initialize. Please check attachment.

During installation, I have modifed the partition as follow:

/boot -- 250MB

swap -- 1600 MB

/ -- 5120 MB

Extend partition:

/var/log -- 4096 MB

/tmp --2048 MB

/home -- 2048MB

/opt --- 2048 MB

vmkcore -- 100MB

The partitions were shown in exact order listed. I have forced the swap partition in the primary partition. Would this be the cause of the problem? This is only thing that I change. Also, would the problem be with the 6 cores processor. I have checked the HCL and didn't see any 6 cores processor listed but in the note section "6. Up to 16 cores processor."

Thanks for the help.

[HKWP]

These are the log files from the system.

[Texiwill]

Hello,

ESX does not properly support USB devices. What happens when you remove Lexar JumpDrive? Unless are we discussing ESXi here and not ESX?

The vmkernel failed to run so you could have many problems unrelated to your disk layout. First I would drop the USB, I would then do the following:

1) Open up the box and look for obvious hardware issues, then reseat cards/memory

2) Update the BIOS and Firmware on the system

2a) Verify that the BIOS settings are correct for ESX

3) Run memtest86+ for 24 to 48 hours

4) Run Vendor Hardware Diags for 24 to 48 hours

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

Blue Gears and SearchVMware Pro Blogs: http://www.astroarch.com/wiki/index.php/Blog_Roll

Top Virtualization Security Links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links

[HKWP]

The VMware tech support engineer suggested that the issue is CPU stepping related. And asked me to run the CPUID tool. However, I guess the CPU is too new, CPUID doesn't work on the IBM x3850 M2 (Intel six-core E7450 processor). Is there any other tool that can determine CPU stepping? I've already ran the IBM hardware diags and IBM tech support said they all have the same cpu step. I just want to verify the result. In addition, the bios and firmware is up to date. As far as bios settings, I don't think there is any specific settings and vt is turned on.

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=100795...

Any other suggestions??

Thanks

[HKWP]

Also, I just want to mention that the USB drive was inserted after the server failed to mount the root fs and leads me to a shell to

execute vm-support.

[Texiwill]

Hello,

Other than removing the Jumpdrive, I do not have anything. If the CPU is too new ESX may not yet support it. I would Get IBM to talk to VMware and get you the support state of the system with those CPUs.

Best regards,

Edward L. Haletky

VMware Communities User Moderator

====

Author of the book 'VMWare ESX Server in the Enterprise: Planning and Securing Virtualization Servers', Copyright 2008 Pearson Education.

Blue Gears and SearchVMware Pro Blogs: http://www.astroarch.com/wiki/index.php/Blog_Roll

Top Virtualization Security Links: http://www.astroarch.com/wiki/index.php/Top_Virtualization_Security_Links

[HKWP]

Hi All,

The issue has been resolved. I'm now able to boot the IBM x3850 M2 up with ESX 3.5 U2. VM Kernel loaded successfully during boot up. Lesson learned: First, CPUID doesn't run on the new IBM x3850 M2 (both six-core and quad-core processor). Second, using USB/PS2 adapter will cause VMkernel failed to load during boot up.

I have contacted IBM tech support and they did mention something about using a KVM on these IBM x3850 M2 can cause issue running ESX. Therefore, we removed the server from the KVM but we were still using the same USB/PS2 adapter that were attached. After removing the adapter and switched to USB keyboard and mouse (direct plug in). The box boot up flawlessly. We have tested this on three IBM x3850 M2.

Thanks

Will

[joesanzone]

This problem still exists in 4.1. We have an old Avocent KVM with ps/2 connectors & adapters to USB. CPU fails to initialize. Remove adapter & the problem goes away.