I have a similar problem, with the DL 160 G5. The installer says it can't find any supported NICs
(5722s: RH EL 5 - 64 says it uses the tg3 driver, and its supposed to be in 3.5, so, don't get it).
thanks in advance,
Apparently, HP DL180 is not supported by VmWare.
By using a separate NIC card and a SmartArray P400, I managed to get almost all the way. VmWare 3.5 is installed and seems to be working. Only, when tyring to actually install a guest OS, it cannot find a hard disk.
It gets as far as reading the installation CD, that part works fine. Trying to install Win XP, it says "Cannot find a hard disk". When trying FreeBSD, it loads the kernel from the CD, and then fails with "BTX Halted".
Since it is not supported by VmWare, I guess we are out of luck?
With ESX, virtual machines only can use virtual SCSI disks and XP doesn't include the drivers for that. See this thread on how to get around that - http://communities.vmware.com/message/819716?tstart=0.
Your post has been moved to the VI: ESX 3.5 forum
VMware Communities User Moderator
I'm also trying to evaluate ESX 3.5 on two DL180 G5s. I'm using local SATA drives and have tried using the service console to edit /etc/vmware/pciid/ata_piix.xml to include the DL180-specific device ID (based on instructions SATA Support Clear as Mud!?). I added this to the Intel vendor section (8086).
<device id="2920:103c:31fe"> <vmware label="scsi"> <driver>ata_piix</driver> <vmware> <name>HP DL180 G5 integrated 4 port SATA</name> </device>
I then ran esxcfg-pciid and then esxcfg-boot -p but even after boot I get errors mounting the root filesystem. I am able to confirm that the proper PCI IDs have been added to the initrd's config files.
I have SATA RAID mode disabled and the installer sees the devices just fine. After some research it seems that this hardware is not "officially" supported but it doesn't seem to be different from other working ICH9 controllers (different device ID perhaps but the service console works using the ata_piix driver). There doesn't seem to be a way in the BIOS to select native or legacy SATA modes.
Per the ESX 3.5 whitebox table it seems like this should work... am I missing something or should I get new hardware? I also tried 3i but post-install I had the same error mounting the root filesystem (but haven't tried the PCIID hack yet).
I've seen some other posts mention using an HTTP-based install (Building a test server / white box - post your builds here), so I'll give this a shot with a USB DVD drive and see if there are any differences versus using the installed (SATA/PATA) DVD drive.
Welcome to the VMware Community forums. For the PCI ID, did you get that from the SATA MUD thread or from your server with the lspci command?
ESXi uses a different method for the PCI database so you can't edit files on it as you would with ESX. You have to create a custom oem.tgz file from the install CD.
I got the device ID using lspci. The vendor ID and device ID were already listed in ata_piix.xml, but I assume that because HP uses a sub-vendor and (I assume) sub-device ID such that the generic module wasn't getting properly matched to the HP-branded device.
I tried this hack with both ESX and ESXi, but neither seemed to work. I also tried using a Linux live CD to chroot into the service console environment and when I ran esxcfg-boot and it gave quite a bit more output. I can post that output when I get into work tomorrow.
I also tried replicating the XML used by some of the other drives where a <table> tag is used, but that didn't seem to make a difference.
My attempts to use a USB DVD drive to install didn't seem to make a difference either... so my task for tomorrow will be digging into the HP documentation to see if their BIOS allows disabling "legacy" IDE/SATA mode.
So the problem at hand may not have been directly related to the ICH9 support or hacking PCI config files. After reviewing the boot scripts and the kernel output after a failed boot, it seemed like the /proc/vmware directory wasn't getting populated (although it did seem that /proc was getting mounted) as I was getting errors about /proc/vmware/pci not existing among other errors. Just prior to that, there were a large number of APIC-related messages. On a whim I added "noapic" as a kernel parameter via GRUB and this time the init scripts did seem to work and the VMWare kernel seems to have started. I'm currently reinstalling and will see if it works out of the box if I add "noapic".
So I can confirm that the HP DL180 G5 works out of the box if during your install, you use advanced boot parameters and add "noapic".
Without this option, I was getting errors such as the following:
IRQ: 153: Irq 151: apic 0 pin -1 vector 0x0 action NO
This was repeated with the same "IRQ: 153" prefix with the "Irq xxx" number changing. Then the console reports:
WARNING: IRQ: 343: Likely BIOS error
Then the VMWare init scripts start loading and there are several messages such as:
cp: /proc/vmware/log: No such file or directory
cp: /proc/vmware/pci: No such file or directory
Using the "noapic" kernel parameter gets past these errors, although VMware does warn me that it's using PIC instead of APIC.
Well, a follow up where I get to put my tail between my legs. I just got a bunch of new servers and confused the model numbers. I was testing with an HP DL320 G5p, not a DL180 G5. I'm using the DL180 to run OpenFiler. The upside is that the DL320 G5p does work with the "noapic" option (at least for evaluation and prototyping).
Did running noapic eliminate the issue with the sub-vender / device ID on SATA controller?
When using the "noapic" option, I did not need to add the sub-vendor PCI ID to get ESX to boot properly.
When using a SmartArray400 and a separate NIC that is supported, the DL 180 now works fine, bu ony for 32-bit guests. 64-bit OS:s cannot be installed at all. Ubuntu says "this is not a 64 bit machine" and FreeBSD the more subtle "Halted on BTX".
But 32 bits work fine, which is OK for me.