IBM xSeries 3550 – not supported on ESX 3.0.1?

Our main virtualization platform of choice has been IBM xSeries servers, specifically xSeries 3850. We have 5 remote offices that are now being deployed domain controllers and decided to use a smaller model (x3550) instead. Upon first load of the OS, we get the following error message:
0:00:00:12.996 cpu0:1024)PCI: 1650: failed for 000.08.0
I called VMware support, and they point to the System Peripheral Bus after enumerating the PCI bus using lspci. I call IBM tech support and ask about supported firmware version due to all 5 systems seeing the same problem.

This is where it gets interesting. I eventually escalate the call to Back Office engineers, who tell me despite what the Systems HCL List ( http://www.vmware.com/pdf/vi3_systems_guide.pdf) says, only 3.0 is supported not 3.0.1. She said the only reliable document on support is http://www-03.ibm.com/servers/eserver/serverproven/compat/us/nos/vmware.html
(which does not list any 2.5.x variants either). I am frustrated right as it would seem my whole environment while supported via VMware is unsupported according to IBM. I could believe a front line tech getting supportability wrong, but with back office should at least have the correct information. She said I had to downgrade to 3.0 before she could support me. I installed 3.0 and still got a similar error message (0:00:00:12.974 cpu0:1024)PCI: 1655: failed for 000.08.0), so at least the 5 systems are consistent. :-)

Is anyone else having the same error message as I?


Technorati : , , , , , ,

Share

No comments yet to IBM xSeries 3550 – not supported on ESX 3.0.1?

  • I love the blog that you have. I was wondering if you would link my blog to yours and in return I would do the same for your blog. If you want to, my site name is American Legends and the URL is:

    http://www.americanlegends.blogspot.com

    If you want to do this just go to my blog and in one of the comments just write your blog name and the URL and I will add it to my site.

    Thanks,
    David

  • Niwrad

    Hey, love the site! Sorry, I am using MS Virtual Server 2005 R2. I am very interested in what you aredoing with the remote DCs and virtualization..? Not sure I understand? Are you deploying hosts in the remote offices?
    Sorry, I have no suggestions, but it is interesting.

  • Niwrad

    Hey, call me! I need the updated key or we need to get our maint. updated for Hfnetchk Pro.. I came in to day to patch and cannot download the latest XML. Bummer! Reply to my email or call my office if you get this today…. Thanks!!!

  • Emiliano

    Yes I’ve got the same problem with an Intel Dual PRO/1000 PT Network card.
    The system doesn’t assign any IRQ on any ports and I haven’t no network support…
    If I move that card in a different slot, I solve the problem.
    I think the problem is how kernel enumerate the IRQ numbers!
    But the other slot is filled with another card and I cannot move this.

  • Emiliano – the good news is that the updated BIOS was just released and it fixed our issue. It might fix your issue too.

  • [...] Just an update on a previous post about ESX incompatibility with x3550, the solution from IBM was to install 3.0.2 or install a BIOS patch, which was not released (at that time) yet. Fortunately, it was released ahead of schedule, and the patch eliminated the aesthetic error message. We have deployed the latest BIOS on the UpdateExpress v4.05, and we aren’t bothered by the error message. [...]

  • ESX 3.01 is running fine using IBM Server xSeries x3500 Model 7977K1G, x3500 is Tower Model, x3550 is Rack Modell.

  • IBM 3850 ventilator problem

    sometimes my server IBM XSerie 3850 these ventilator works at a raised normal rate, what is causes it, for so much the room is well air-conditioned and the temperature is of 25°C

Statistics