<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:clearspace="http://www.jivesoftware.com/xmlns/clearspace/rss" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:opensearch="http://a9.com/-/spec/opensearch/1.1/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>VMware Communities: Message List - Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
    <link>http://communities.vmware.com/community/vmtn/vi/esx3.5?view=discussions</link>
    <description>Most recent forum messages</description>
    <language>en</language>
    <pubDate>Fri, 13 Feb 2009 18:09:29 GMT</pubDate>
    <generator>Clearspace 1.10.12 (http://jivesoftware.com/products/clearspace/)</generator>
    <dc:date>2009-02-13T18:09:29Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1171596?tstart=0#1171596</link>
      <description>&lt;br /&gt;
Hi Guys,&lt;br /&gt;
Just wanted to let you know that I had similar problem getting ESXi to work with DL180 even though I had followed the suggestions of making sure BIOS was up-to-date, add-on card was used for storage (HP Smart Array P400) and network card, and using a USB keyboard and mouse rather than the PS2 version. &lt;br /&gt;
&lt;br /&gt;
However, after a number of different combinations of raid card and add-on card and disabling this and that I still could get the ESXi to work either from a USB stick, or when installed on the local drives, both old and new version (at the timing of writing this the latest version is 130755). It would basically stay alive for around 1-2 minutes and then PSOD with Exception 14 errors. I even tried ram changes, upgrades and individual module inserted, and trying to virtual copy the USB stick from a perfectly working ML350 G5 with the latest ESXi build. At one point I thought of replacing the single 2.5Ghz Quad Core CPU for 1 or 2x Dual/Quad core 2Ghz to see if that worked.&lt;br /&gt;
&lt;br /&gt;
It was then that I asked TechFan for a hand, as his last post he had mentioned that he managed to get a couple of Dl180 G5's working for the last several months. After a number of emails being sent back and forth he suggested ditching the downloadable ESXi + HP Insight Support, and just using the standard ESXi download, and IT WORKED. Simple really, and i guess it made sense, as the HP tools where probably not designed for the DL180 G5 and as soon as ESXi booted and tried to run the HP Tools, it crashed and gave me PSOD.&lt;br /&gt;
&lt;br /&gt;
I have now been using it for a few days straight and not a single crash. I have installed new VMs, migrated VMs, backed up VMs and made a heap of configurations changes + assigned it to Virtual Center and everything is ticking along nicely.&lt;br /&gt;
&lt;br /&gt;
So for all of you out there wanting to use a DL180 G5, for whatever reason, and mine was for home use to get to know VMware slightly better (as it is a great little cheap server that can easily take up to 12x Hard Disk) make sure you do the following and you should be fine:&lt;br /&gt;
&lt;br /&gt;
1- Disable on board SATA as it does not work well with it on. If you want to use a CD/DVD-Rom then make sure to connect it to the first port and not the second and set the port to non-raid.&lt;br /&gt;
    - No need to disable onboard Lan as it seems to work fine&lt;br /&gt;
2- Download and install whatever version of ESXI (and i think ESX as well) you want but make sure not to use the ones with HP Tools, as for the time being (13-02-2009) that causes the server to crash.&lt;br /&gt;
3- Use the USB keyboard and mouse and not the PS2 version, as this also has the habit of making it slightly less stable and prone to crashes.&lt;br /&gt;
&lt;br /&gt;
And you should be fine.&lt;br /&gt;
&lt;br /&gt;
Good Luck and thank you TechFan</description>
      <pubDate>Fri, 13 Feb 2009 18:09:29 GMT</pubDate>
      <author>fa147</author>
      <guid>http://communities.vmware.com/message/1171596?tstart=0#1171596</guid>
      <dc:date>2009-02-13T18:09:29Z</dc:date>
      <clearspace:dateToText>9 months, 1 week ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1113832?tstart=0#1113832</link>
      <description>Just an update. Our CPU not responding messages went away after we stopped plugging in the PS2 keyboard (use USB) and mouse. We can also install with the first onboard SATA/IDE controller disabled. So, we have been running fine with the E200 controller and using the built-in NIC and an addon</description>
      <pubDate>Wed, 03 Dec 2008 06:38:37 GMT</pubDate>
      <author>TechFan</author>
      <guid>http://communities.vmware.com/message/1113832?tstart=0#1113832</guid>
      <dc:date>2008-12-03T06:38:37Z</dc:date>
      <clearspace:dateToText>11 months, 3 weeks ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1067444?tstart=0#1067444</link>
      <description>&lt;br /&gt;
So, the conclusion is that someone has ESXi 3.5 U2 running on a DL180 G5??&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
We have been having major issues with this.  We have two identical DL180 G5's.  We already had added a supported Intel NIC and replaced the E200 controller (though it appears that controller is on the list now).  We have gotten ESXi installed (which some people seem to be having issues with; actually, it never auto reboots at the end of installation, but it comes up fine after manually powering off/on the machine).  We have even had some VM's running for a short time, but then all of a sudden we get the Purple screen of death with a message about CPU 0 (or some other number) not responding.  We have re-installed 10+ times on 2 different identically configured machines.&lt;br /&gt;
&lt;p /&gt;
 Anyone have ESXi running on a DL180 G5??  Anyone seen the CPU not responding message??</description>
      <pubDate>Mon, 06 Oct 2008 07:59:43 GMT</pubDate>
      <author>TechFan</author>
      <guid>http://communities.vmware.com/message/1067444?tstart=0#1067444</guid>
      <dc:date>2008-10-06T07:59:43Z</dc:date>
      <clearspace:dateToText>1 year, 1 month ago</clearspace:dateToText>
      <clearspace:replyCount>2</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1038564?tstart=0#1038564</link>
      <description>At the initial VMware VMvisor Boot Menu (i.e. the blue screen), press the tab key and you should then see&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt; mboot.c32 vmkernel.tgz  --- binmod.tgz --- ienviroment.tgz --- cim.tgz --- oem.tgz --- license.tgz --- install.tgz&lt;/div&gt;
&lt;br /&gt;
you can add  the switch and then press enter to continue booting&lt;br /&gt;
&lt;br /&gt;
&lt;div class="jive-quote"&gt;mboot.c32 vmkernel.tgz acpi=off --- binmod.tgz --- ienviroment.tgz --- cim.tgz --- oem.tgz --- license.tgz --- install.tgz&lt;/div&gt;</description>
      <pubDate>Sun, 31 Aug 2008 07:23:09 GMT</pubDate>
      <author>Dave.Mishchenko</author>
      <guid>http://communities.vmware.com/message/1038564?tstart=0#1038564</guid>
      <dc:date>2008-08-31T07:23:09Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1038549?tstart=0#1038549</link>
      <description>&lt;br /&gt;
Dear quicknetsv;&lt;br /&gt;
&lt;p /&gt;
I have the same problem installing ESXi 3.5 on HP Proliant DL320G5 SmartArrayE200 controler with 2xSATA drives. If you're so kind, and please let me know, where and how can I add/edit ESXi configuration (since ESXi doesn't have service console) with this "esx noapic"?&lt;br /&gt;
&lt;p /&gt;
Thank you in advance,Regards,Miha</description>
      <pubDate>Sun, 31 Aug 2008 07:03:00 GMT</pubDate>
      <author>Bernikm</author>
      <guid>http://communities.vmware.com/message/1038549?tstart=0#1038549</guid>
      <dc:date>2008-08-31T07:03:00Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
      <clearspace:replyCount>4</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1034607?tstart=0#1034607</link>
      <description>With your ICH9R controller you'll have to put it in non-RAID mode within the BIOS.  To fix the mounting root failed error take a look at the instructions here - &lt;a class="jive-link-external" href="http://www.vm-help.com/esx/esx3.5/SATA_mounting_root_failed.html"&gt;http://www.vm-help.com/esx/esx3.5/SATA_mounting_root_failed.html&lt;/a&gt;.</description>
      <pubDate>Tue, 26 Aug 2008 20:51:00 GMT</pubDate>
      <author>Dave.Mishchenko</author>
      <guid>http://communities.vmware.com/message/1034607?tstart=0#1034607</guid>
      <dc:date>2008-08-26T20:51:00Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1034586?tstart=0#1034586</link>
      <description>&lt;br /&gt;
I knew if I dug hard enough, I might find something -- yeah, I know you all don't care.  But the noapic did not work for me, neither did "noapic" including the quotes.  Finally, I ran across a solution to the problem where I had to enter "esx noapic" without the quotes.  That did the trick, I am now running ESX on my non-supported HP DL320 G5p server... did not attempt to play with the built-in RAID cuz it didn't not see the drive at all when I first tried it.  I gave up on that real fast.&lt;br /&gt;
&lt;p /&gt;
Now, since that worked, and since it is my birthday -- I am leaving early to try the "fix" I found for my car on the internet last night!!  With all this computerized stuff, what would we ever do without Google and User Communities.  BTW, whatever happened to CompuServe?  That is what I cut my computer teeth on while learing to install Novell 2.2.</description>
      <pubDate>Tue, 26 Aug 2008 20:36:21 GMT</pubDate>
      <author>quicknetsv</author>
      <guid>http://communities.vmware.com/message/1034586?tstart=0#1034586</guid>
      <dc:date>2008-08-26T20:36:21Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
      <clearspace:replyCount>5</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1034164?tstart=0#1034164</link>
      <description>&lt;br /&gt;
I have about reached the end of my rope.  I was glad to see that you were using the DL320 G5p as that is what I have.  Even though I have added the parameter on the kernel, it stills fails to mount!  I was evaluating ESX to see if it would make server setup easier as advertised, but I have already wasted two days -- the installer comes up, recognizes all the hardware, installs the system as far as I can tell, and then fails with a "failed to mount root system" or some such message!&lt;br /&gt;
&lt;p /&gt;
Arrrrgggggghhhhhh!!!!!  When I give up, it will be for good!  I am not going to fight this battle much longer!&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
It doesn't help that I am not a Linux expert.&lt;br /&gt;
&lt;p /&gt;
It doesn't help that the eval guide says nothing about what to do it it fails to start.&lt;br /&gt;
&lt;p /&gt;
It doesn't help that the software simply will install but not run on the brand new server.&lt;br /&gt;
&lt;p /&gt;
It doesn't help that when it fails, you are thrown out to a Linux maintenance shell with no direction of what to try next.&lt;br /&gt;
&lt;p /&gt;
It doesn't help to go through debug mode&lt;br /&gt;
&lt;p /&gt;
It doesn't help to go to the mode where the screen looks funky but you can say "CONFIGURE" on all the devices it recognizes!&lt;br /&gt;
&lt;p /&gt;
It doesn't help that a non-linux expert can't figure out how to read the dang install logs to see where all this crap went wrong!!&lt;br /&gt;
&lt;p /&gt;
There is NOTHING, helpful about this software, the guide, the readmes, the lack of documentation, or messages not displayed when it fails to run.  Man, I am ticked off that I have wasted this much time.&lt;br /&gt;
&lt;p /&gt;
 There, I feel better now.</description>
      <pubDate>Tue, 26 Aug 2008 14:53:56 GMT</pubDate>
      <author>quicknetsv</author>
      <guid>http://communities.vmware.com/message/1034164?tstart=0#1034164</guid>
      <dc:date>2008-08-26T14:53:56Z</dc:date>
      <clearspace:dateToText>1 year, 2 months ago</clearspace:dateToText>
      <clearspace:replyCount>7</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1022105?tstart=0#1022105</link>
      <description>&lt;br /&gt;
I'm looking to use the DL180's in my test lab. Have a separate NIC and P400. For the 64 bit issue, did you turn on the Intel Virtualization Technology on for the processors in the BIOS? I used to have problems with the DL380's using 64 bit until we enabled VT on the CPUs.</description>
      <pubDate>Wed, 13 Aug 2008 15:00:20 GMT</pubDate>
      <author>kdmh</author>
      <guid>http://communities.vmware.com/message/1022105?tstart=0#1022105</guid>
      <dc:date>2008-08-13T15:00:20Z</dc:date>
      <clearspace:dateToText>1 year, 3 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1002544?tstart=0#1002544</link>
      <description>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".&lt;br /&gt;
&lt;br /&gt;
But 32 bits work fine, which is OK for me.</description>
      <pubDate>Fri, 25 Jul 2008 07:21:45 GMT</pubDate>
      <author>girgen</author>
      <guid>http://communities.vmware.com/message/1002544?tstart=0#1002544</guid>
      <dc:date>2008-07-25T07:21:45Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1002529?tstart=0#1002529</link>
      <description>When using the "noapic" option, I did not need to add the sub-vendor PCI ID to get ESX to boot properly.</description>
      <pubDate>Fri, 25 Jul 2008 03:50:40 GMT</pubDate>
      <author>plmc</author>
      <guid>http://communities.vmware.com/message/1002529?tstart=0#1002529</guid>
      <dc:date>2008-07-25T03:50:40Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1002514?tstart=0#1002514</link>
      <description>Did running noapic eliminate the issue with the sub-vender / device ID on SATA controller?</description>
      <pubDate>Fri, 25 Jul 2008 03:02:16 GMT</pubDate>
      <author>Dave.Mishchenko</author>
      <guid>http://communities.vmware.com/message/1002514?tstart=0#1002514</guid>
      <dc:date>2008-07-25T03:02:16Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>1</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1002432?tstart=0#1002432</link>
      <description>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).</description>
      <pubDate>Thu, 24 Jul 2008 23:34:37 GMT</pubDate>
      <author>plmc</author>
      <guid>http://communities.vmware.com/message/1002432?tstart=0#1002432</guid>
      <dc:date>2008-07-24T23:34:37Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>10</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1002254?tstart=0#1002254</link>
      <description>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".&lt;br /&gt;
&lt;br /&gt;
Without this option, I was getting errors such as the following:&lt;br /&gt;
&lt;div class="jive-quote"&gt;IRQ: 153: Irq 151: apic 0 pin -1 vector 0x0 action NO&lt;/div&gt;
&lt;br /&gt;
This was repeated with the same "IRQ: 153" prefix with the "Irq xxx" number changing. Then the console reports:&lt;br /&gt;
&lt;div class="jive-quote"&gt;WARNING: IRQ: 343: Likely BIOS error&lt;/div&gt;
&lt;br /&gt;
Then the VMWare init scripts start loading and there are several messages such as:&lt;br /&gt;
&lt;div class="jive-quote"&gt;cp: /proc/vmware/log: No such file or directory&lt;br /&gt;
cp: /proc/vmware/pci: No such file or directory&lt;/div&gt;
&lt;br /&gt;
Using the "noapic" kernel parameter gets past these errors, although VMware does warn me that it's using PIC instead of APIC.</description>
      <pubDate>Thu, 24 Jul 2008 20:16:01 GMT</pubDate>
      <author>plmc</author>
      <guid>http://communities.vmware.com/message/1002254?tstart=0#1002254</guid>
      <dc:date>2008-07-24T20:16:01Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>11</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1002225?tstart=0#1002225</link>
      <description>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 &lt;b&gt;/proc/vmware&lt;/b&gt; directory wasn't getting populated (although it did seem that &lt;b&gt;/proc&lt;/b&gt; was getting mounted) as I was getting errors about &lt;b&gt;/proc/vmware/pci&lt;/b&gt; 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".</description>
      <pubDate>Thu, 24 Jul 2008 19:44:10 GMT</pubDate>
      <author>plmc</author>
      <guid>http://communities.vmware.com/message/1002225?tstart=0#1002225</guid>
      <dc:date>2008-07-24T19:44:10Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>12</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1002138?tstart=0#1002138</link>
      <description>Seems the verbose output from &lt;b&gt;esxcfg-boot&lt;/b&gt; was due to my not mounting &lt;b&gt;/var/log&lt;/b&gt; into the chroot environment (normally it writes to */var/log/vmware/esxcfg-boot.log*). I've attached this file as well as the updated &lt;b&gt;/etc/vmware/esx.conf&lt;/b&gt;.</description>
      <pubDate>Thu, 24 Jul 2008 18:37:01 GMT</pubDate>
      <author>plmc</author>
      <guid>http://communities.vmware.com/message/1002138?tstart=0#1002138</guid>
      <dc:date>2008-07-24T18:37:01Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>13</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1001485?tstart=0#1001485</link>
      <description>I got the device ID using &lt;b&gt;lspci&lt;/b&gt;. The vendor ID and device ID were already listed in &lt;b&gt;ata_piix.xml&lt;/b&gt;, 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.&lt;br /&gt;
&lt;br /&gt;
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 &lt;b&gt;esxcfg-boot&lt;/b&gt; and it gave quite a bit more output. I can post that output when I get into work tomorrow.&lt;br /&gt;
&lt;br /&gt;
I also tried replicating the XML used by some of the other drives where a &amp;lt;table&amp;gt; tag is used, but that didn't seem to make a difference.&lt;br /&gt;
&lt;br /&gt;
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.</description>
      <pubDate>Thu, 24 Jul 2008 04:58:47 GMT</pubDate>
      <author>plmc</author>
      <guid>http://communities.vmware.com/message/1001485?tstart=0#1001485</guid>
      <dc:date>2008-07-24T04:58:47Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>14</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1001490?tstart=0#1001490</link>
      <description>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?&lt;br /&gt;
&lt;br /&gt;
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.</description>
      <pubDate>Thu, 24 Jul 2008 04:06:58 GMT</pubDate>
      <author>Dave.Mishchenko</author>
      <guid>http://communities.vmware.com/message/1001490?tstart=0#1001490</guid>
      <dc:date>2008-07-24T04:06:58Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>15</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1001361?tstart=0#1001361</link>
      <description>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 &lt;b&gt;/etc/vmware/pciid/ata_piix.xml&lt;/b&gt; to include the DL180-specific device ID (based on instructions &lt;a href="http://communities.vmware.com/thread/116768" class="jive-link-thread"&gt;SATA Support Clear as Mud!?&lt;/a&gt;). I added this to the Intel vendor section (8086).&lt;br /&gt;
&lt;br /&gt;
&lt;pre class="jive-pre"&gt;&lt;code class="jive-code jive-xml"&gt;
&lt;span class="jive-xml-tag"&gt;&amp;lt;device id=&lt;span class="jive-xml-quote"&gt;&amp;quot;2920:103c:31fe&amp;quot;&lt;/span&gt;&amp;gt;&lt;/span&gt;
&lt;span class="jive-xml-tag"&gt;&amp;lt;vmware label=&lt;span class="jive-xml-quote"&gt;&amp;quot;scsi&amp;quot;&lt;/span&gt;&amp;gt;&lt;/span&gt;
&lt;span class="jive-xml-tag"&gt;&amp;lt;driver&amp;gt;&lt;/span&gt;ata_piix&lt;span class="jive-xml-tag"&gt;&amp;lt;/driver&amp;gt;&lt;/span&gt;
&lt;span class="jive-xml-tag"&gt;&amp;lt;vmware&amp;gt;&lt;/span&gt;
&lt;span class="jive-xml-tag"&gt;&amp;lt;name&amp;gt;&lt;/span&gt;HP DL180 G5 integrated 4 port SATA&lt;span class="jive-xml-tag"&gt;&amp;lt;/name&amp;gt;&lt;/span&gt;
&lt;span class="jive-xml-tag"&gt;&amp;lt;/device&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;&lt;br /&gt;
&lt;br /&gt;
I then ran &lt;b&gt;esxcfg-pciid&lt;/b&gt; and then &lt;b&gt;esxcfg-boot -p&lt;/b&gt; 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.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
Per &lt;a class="jive-link-external" href="http://www.vm-help.com/esx/esx3.5/Whiteboxes_SATA_Controllers_for_ESX_3.5_3i.htm"&gt;the ESX 3.5 whitebox table&lt;/a&gt; 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).&lt;br /&gt;
&lt;br /&gt;
I've seen some other posts mention using an HTTP-based install (&lt;a href="http://communities.vmware.com/thread/123254" class="jive-link-thread"&gt;Building a test server / white box - post your builds here&lt;/a&gt;), 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.</description>
      <pubDate>Wed, 23 Jul 2008 23:36:08 GMT</pubDate>
      <author>plmc</author>
      <guid>http://communities.vmware.com/message/1001361?tstart=0#1001361</guid>
      <dc:date>2008-07-23T23:36:08Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>16</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1001146?tstart=0#1001146</link>
      <description>Your post has been moved to the VI: ESX 3.5 forum&lt;br /&gt;
&lt;br /&gt;
Dave Mishchenko&lt;br /&gt;
VMware Communities User Moderator</description>
      <pubDate>Wed, 23 Jul 2008 18:56:49 GMT</pubDate>
      <author>Dave.Mishchenko</author>
      <guid>http://communities.vmware.com/message/1001146?tstart=0#1001146</guid>
      <dc:date>2008-07-23T18:56:49Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1001145?tstart=0#1001145</link>
      <description>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 - &lt;a class="jive-link-external" href="http://communities.vmware.com/message/819716?tstart=0"&gt;http://communities.vmware.com/message/819716?tstart=0&lt;/a&gt;.</description>
      <pubDate>Wed, 23 Jul 2008 18:55:52 GMT</pubDate>
      <author>Dave.Mishchenko</author>
      <guid>http://communities.vmware.com/message/1001145?tstart=0#1001145</guid>
      <dc:date>2008-07-23T18:55:52Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/1000565?tstart=0#1000565</link>
      <description>Apparently, HP DL180 is not supported by VmWare.&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
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".&lt;br /&gt;
&lt;br /&gt;
Since it is not supported by VmWare, I guess we are out of luck?</description>
      <pubDate>Wed, 23 Jul 2008 09:13:45 GMT</pubDate>
      <author>girgen</author>
      <guid>http://communities.vmware.com/message/1000565?tstart=0#1000565</guid>
      <dc:date>2008-07-23T09:13:45Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>3</clearspace:replyCount>
    </item>
    <item>
      <title>Re: Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/988288?tstart=0#988288</link>
      <description>&lt;br /&gt;
I have a similar problem, with the DL 160 G5. The installer says it can't find any supported NICs&lt;br /&gt;
&lt;p /&gt;
(5722s: RH EL 5 - 64 says it uses the tg3 driver, and its supposed to be in 3.5, so, don't get it).&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;p /&gt;
thanks in advance,&lt;br /&gt;
&lt;p /&gt;
Matthew</description>
      <pubDate>Tue, 08 Jul 2008 00:33:19 GMT</pubDate>
      <author>tminc</author>
      <guid>http://communities.vmware.com/message/988288?tstart=0#988288</guid>
      <dc:date>2008-07-08T00:33:19Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
    </item>
    <item>
      <title>Support for ICH9R and NC7781 on ProLiant DL180 G5</title>
      <link>http://communities.vmware.com/message/983613?tstart=0#983613</link>
      <description>&lt;br /&gt;
We recently downloaded the evaluation disc for VMware  ESX 3.5 and it's unable to detect the harddisks and the network card. I've done a search for the ICH9R here on VMTN and apparently users have been able to get it working in SATA mode, so I'm assuming they didn't set it to IDE Legacy mode in the BIOS? I also did a search for the NC7781, and &lt;a class="jive-link-external" href="http://h20247.www2.hp.com/enterprise/cache/525611-0-0-98-121.html"&gt;according to HP, it was supported in VMware ESX 3.0&lt;/a&gt;.&lt;br /&gt;
&lt;p /&gt;
&lt;p /&gt;
&lt;br /&gt;
So, my question basically is whether anyone has managed to install VMware ESX 3.5 on an HP ProLiant DL180 G5? Barring that, does VMware offer any alternatives to VMware Server that will allow us to use more than 3600MB per virtual machine?</description>
      <pubDate>Tue, 01 Jul 2008 07:31:52 GMT</pubDate>
      <author>EdwardS</author>
      <guid>http://communities.vmware.com/message/983613?tstart=0#983613</guid>
      <dc:date>2008-07-01T07:31:52Z</dc:date>
      <clearspace:dateToText>1 year, 4 months ago</clearspace:dateToText>
      <clearspace:replyCount>23</clearspace:replyCount>
    </item>
  </channel>
</rss>

