Hello,
I recently implemented ESX 3.5 on my SunFire 40 Server (dual AMD single core CPUs); replacing ESX 3.02. When it boots it gets hung up for at least thirty minutes (no exaggeration) trying the connect to the ipmi drivers: ipmi_si - KCS, ipmi_si - SMIC, and ipmi_si - bt at different I/O ports.
I have two questions:
Is there a way to disable IPMI; or at least these checks for it?
With my Server evidently not supporting the Intel Management specification (IPMI); is this going to cause any problems? The system seems to operate fine except for the painfully long boot process.
I was a 3.5 beta tester and this occured with the beta's as well. Thanks in advance for any assistance!
M
Unload OpenIPMI driver that VMware loads, rpm -qa|grep -i IPMI should find it. I have an older ML350 G3 we try to blow up with new toys, and ESX 3.5 on it, gets the same error, but since the SMBus on the server is not recognized, it waits a second or two, and goes on.
Unload OpenIPMI driver that VMware loads, rpm -qa|grep -i IPMI should find it. I have an older ML350 G3 we try to blow up with new toys, and ESX 3.5 on it, gets the same error, but since the SMBus on the server is not recognized, it waits a second or two, and goes on.
So what you are saying is coffee is the key!
I am kinda partial to Vogon Poetry though, we can keep a few archives at least
And believe you me: I will always keep my towel handy
Is this cappuccino, expresso, or Latte?
I like cafe mocao, wow I need to go to Starbucks...
My bad? I am so used to using hardware vendor agents, which usually load separate IPMI, I was thinking VMware had a separate RPM for it. The chkconfig trick is correct.
I was reading the email notifications and missed the coffee comments before my last reply... and since I do not drink coffee, my final comment is...
"SO LONG... AND THANKS FOR ALL THE FISH"
Hi there,
any hints how to disable the IPMI within esxi 3.5 u2?
Thanks!