Accepted Solutions
Hi,
you welcome 
All seems to point to the sfcbd process (CIM providers). But it's a initial hypothesis. Just this :).
Running a customized esxi HP version on unsupported HP machines can produce weird effects. Because of this is highly unrecommended using this kind of installation.
I really don't know a alternative for what you want. To be able to monitoring (in a tightly way) on esxi you must use a supported HP machine. If not then you must use a vanilla esxi version without tight hardware monitoring.
Please, don't forget to mark any helpful or correct answer.
Regards/Saludos,
Pablo
Please consider awarding any helpful answer. Thanks!! - Por favor considera premiar las respuestas útiles. ¡¡Muchas gracias!!
Hi,
without see more information about the PSOD i would recommend you to check if all the hardware is really supported by esxi.
A PSOD in the install time sounds like some hardware component isn't supported. Then the issue happens.
I would recommend you check carefully this post to be 100% confident about your esxi 4.0 hardware compatibility.
Anyway if you can't show more information about the PSOD, you maybe can check this KB to gain knowledge about the PSOD's:
Hope this helps 
Regards/Saludos,
Pablo
Please consider awarding any helpful answer. Thanks!! - Por favor considera premiar las respuestas útiles. ¡¡Muchas gracias!!
Hi,
thanks for the hint's.
Just to make clear... I don't get this screen while i'm installting esxi. I get it after the host has boot up. I see the, let's say, "home" sceen of esxi where you can the ip adress of the host etc. and after a minute I get the attached blue screen....
But I will check memory afterwards.
Any other ideas???
Regards,
Sebastian
Hi
just to discard it, check the host memory with a tool like memtest.
Checking your screen snapshot, i can notice esxi was just up one minute before the PSOD happens!
Also i have seen that the PSOD is more likely to be related to the sfcbd process. This process is the esxi CIM agent that permits a tight host hardware monitoring in the Dell, IBM or HP machines.
This issue remember me another issue with the sfcbd process. But in this case it happens on esxi 3.5 ...
Perhaps you are running a HP customized esxi 4.0? I just have checked the official HCL and your HP system (HP Proliant dl 120) isn't supported. Then is recommended to install the vanilla esxi 4.0 U1 version, not the HP customized one.
Anyway if it isn't supported then maybe esxi 4.0 will work but with issues. I would recommend you to check this post about the esxi 4.0 hardware compatibilities.
Ok, IMHO i would recommend you follow this steps:
1) Check the host memory to find if some memory dim is broken. This can be the reason to your PSOD.
2) Disable the CIM Agent in your esxi host. To do it, you can check my previous link in this post about the sfcbd issue. If PSOD's not happens again, then you know the issue's cause. Another option is install the vanilla esxi 4.0 U1 version instead.
Let me know if any of my advices works for you
Regards/Saludos,
Pablo
Please consider awarding any helpful answer. Thanks!! - Por favor considera premiar las respuestas útiles. ¡¡Muchas gracias!!
Hi,
you welcome
All seems to point to the sfcbd process (CIM providers). But it's a initial hypothesis. Just this :).
Running a customized esxi HP version on unsupported HP machines can produce weird effects. Because of this is highly unrecommended using this kind of installation.
I really don't know a alternative for what you want. To be able to monitoring (in a tightly way) on esxi you must use a supported HP machine. If not then you must use a vanilla esxi version without tight hardware monitoring.
Please, don't forget to mark any helpful or correct answer.
Regards/Saludos,
Pablo
Please consider awarding any helpful answer. Thanks!! - Por favor considera premiar las respuestas útiles. ¡¡Muchas gracias!!
.PNG){kind=link}