<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: ifup: vmnics device eth0 does not seem to be present, delaying initializing in VI: VMware ESX® 3.0 Discussions</title>
    <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487556#M18749</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We just had simular issue after upgrading vmware tools on CentOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fixed it by upgrading virtual Hardware and reruning vmware tools config tool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 04 Nov 2010 20:53:24 GMT</pubDate>
    <dc:creator>SashaGrybyuk</dc:creator>
    <dc:date>2010-11-04T20:53:24Z</dc:date>
    <item>
      <title>ifup: vmnics device eth0 does not seem to be present, delaying initializing</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487544#M18737</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;After upgrading my RHES 4 to the latest kernel release I noticed in the startup of my vm that he was showing an error on my vmware-tools.&lt;/P&gt;&lt;P&gt;The system said I had to reconfigure my vmware tools.  After doing that i rebooted the server and now he doesn't automatically start my eth0.  When i go to network setting and i start the mic my network recovers.&lt;/P&gt;&lt;P&gt;What can that be?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards Ronald P.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Sep 2006 12:52:45 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487544#M18737</guid>
      <dc:creator>Ronaldp</dc:creator>
      <dc:date>2006-09-21T12:52:45Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initializing</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487545#M18738</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Check that &lt;A href="https://communities.vmware.com/b"&gt;&lt;/A&gt;/etc/sysconfig/network-scripts/ifcfg-eth0[/b] contains the line &lt;A href="https://communities.vmware.com/b"&gt;&lt;/A&gt;ONBOOT=yes[/b]&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Sep 2006 13:18:50 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487545#M18738</guid>
      <dc:creator>admin</dc:creator>
      <dc:date>2006-09-21T13:18:50Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initiali</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487546#M18739</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Verify the above - but I have also seen that after any kernel updates you may have to reinstall/reconfig the vmtools.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DB&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Sep 2006 14:13:21 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487546#M18739</guid>
      <dc:creator>boydd</dc:creator>
      <dc:date>2006-09-21T14:13:21Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initiali</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487547#M18740</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm seeing this on a fresh install of RHEL 4 as well.  Tryied to re-configure/re-install tools and same thing.   The NIC functions correctly but it just errors on bootup.   Anyone else seeing this in a RHEL 4 box?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Dec 2006 19:04:14 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487547#M18740</guid>
      <dc:creator>jbsengineer</dc:creator>
      <dc:date>2006-12-11T19:04:14Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initializing</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487548#M18741</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Any time we ever get a problem with RHES we always seem to uninstall reinstall the tools..!!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 11 Dec 2006 20:31:58 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487548#M18741</guid>
      <dc:creator>acr</dc:creator>
      <dc:date>2006-12-11T20:31:58Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initiali</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487549#M18742</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;got exactly the same thing with mandriva2007 guest. actually it works on the first boot after installation of guest, but it got lost after a reboot.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;dmesg | grep eth0 shows it is present as pcnet32&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;pcnet32 kernel module is also loaded fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;weird problem.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Feb 2007 00:08:38 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487549#M18742</guid>
      <dc:creator>johnshen</dc:creator>
      <dc:date>2007-02-02T00:08:38Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initiali</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487550#M18743</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I figured out my problem. It seems that after vmware-tools installation eth0 became eth1 &lt;img id="smileysad" class="emoticon emoticon-smileysad" src="https://communities.vmware.com/i/smilies/16x16_smiley-sad.png" alt="Smiley Sad" title="Smiley Sad" /&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had to use static mac address in the configuration and add HWADDR="macaddress" to force it to be eth0 again. Now it works. It took me a while to realize that this is what is going on.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Feb 2007 01:59:42 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487550#M18743</guid>
      <dc:creator>johnshen</dc:creator>
      <dc:date>2007-02-02T01:59:42Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initiali</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487551#M18744</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I've also got mandriva2007 and found that after a reboot the eth switched to eth1 from eth0.  I hadn't installed vmware-tools -- the strange thing that I did was to "ghetto clone" a vm by copying the vmdk files and create a new custom vm using those disks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The source vm worked fine.  But after the first reboot the new vm wouldn't get on the network, giving "pcnet32 device eth0 does not seem to be present" when I ran "ifup eth0".&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks johnshen for posting the tip on HWADDR, it fixed it for me -- I never would have figured that out.  I guess this is a mandriva peculiarity?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Amir&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 24 Feb 2007 05:08:56 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487551#M18744</guid>
      <dc:creator>adt22</dc:creator>
      <dc:date>2007-02-24T05:08:56Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initiali</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487552#M18745</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You might also try running 'depmod -a'. It appears the vmware tools install doesn't rebuild the database modprobe, etc. use to locate the modules. This command will do that, this combined with removing the HWADDR line from ifcfg-eth0 fixed everything for me.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 02 Mar 2007 18:10:23 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487552#M18745</guid>
      <dc:creator>kjbrady</dc:creator>
      <dc:date>2007-03-02T18:10:23Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initializing</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487553#M18746</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I had the same problem on a Debian Etch.&lt;/P&gt;&lt;P&gt;After installation of vmware-tools, i added the alias line (alias vmxnet eth0)&lt;/P&gt;&lt;P&gt;to /etc/modprobe.d/alias, and everything worked again &lt;img id="smileyhappy" class="emoticon emoticon-smileyhappy" src="https://communities.vmware.com/i/smilies/16x16_smiley-happy.png" alt="Smiley Happy" title="Smiley Happy" /&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2007 09:56:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487553#M18746</guid>
      <dc:creator>bbh</dc:creator>
      <dc:date>2007-06-14T09:56:24Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initiali</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487554#M18747</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Linux kernels &amp;gt; 2.6.18 do not have vmware-tools that work. I am working on some patches but even the any-any patch will not compile the vmware-tools properly. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When you installed vmware-tools and the builds broke, the file /etc/modprobe.conf was still updated. Edit the file....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;       1) change the 'alias eth0 vmnics' line to read 'alias eth0 pcnet32'&lt;/P&gt;&lt;P&gt;       2) Delete all lines after and including the 'Added by VMware' comment.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This will allow your eth0 device to work properly again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I was able to properly patch the vmmemctl driver with no issues however. My attempts to patch the other drivers including vmxnet did not work yet. Still working on it as there was a serious change to the CHECKSUM code between 2.6.18 and later versions of the kernel.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;To put this patch in do the following:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;as root&lt;/P&gt;&lt;P&gt;cd /usr/lib/vmware-tools/modules/source&lt;/P&gt;&lt;P&gt;cp vmmemctl.tar vmmemctl.tar.orig&lt;/P&gt;&lt;P&gt;tar -xf vmmemctl.tar&lt;/P&gt;&lt;P&gt;cd vmmemctl-only&lt;/P&gt;&lt;P&gt;patch -p1 &amp;lt; /tmp/vmmemctl-only.patch&lt;/P&gt;&lt;P&gt;cd ..&lt;/P&gt;&lt;P&gt;tar -cf vmmemctl.tar vmmemctl-only&lt;/P&gt;&lt;P&gt;rm -rf vmmemctl-only&lt;/P&gt;&lt;P&gt;cd /tmp&lt;/P&gt;&lt;P&gt;vmware-config-tools.pl&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When the builds fail for vmhgfs, vmxnet answer 'NO' to the question. That way they will not take effect.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, you will once more need to edit /etc/modprobe.conf per the beginning of this post. Yet, now the memory module is compiled and it will interact with ESX nicely. I am working on the vmxnet module next. My first attempt did not work very well and I am not sure why yet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Best regards,&lt;/P&gt;&lt;P&gt;Edward&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;diff -c -b vmmemctl-only-orig/os.c vmmemctl-only/os.c&lt;/P&gt;&lt;P&gt;\*** vmmemctl-only-orig/os.c     2007-03-30 13:54:30.000000000 -0400&lt;/P&gt;&lt;P&gt;\--- vmmemctl-only/os.c  2007-06-13 11:35:11.000000000 -0400&lt;/P&gt;&lt;P&gt;***************&lt;/P&gt;&lt;P&gt;\*** 23,29 ****&lt;/P&gt;&lt;P&gt;\--- 23,31 -&lt;/P&gt;&lt;HR originaltext="---" /&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  #include "driver-config.h"&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;+ #if   LINUX_VERSION_CODE &amp;lt;= KERNEL_VERSION(2,6,18)&lt;/P&gt;&lt;P&gt;  #include &amp;lt;linux/config.h&amp;gt;&lt;/P&gt;&lt;P&gt;+ #endif&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  #ifdef        MODULE&lt;/P&gt;&lt;P&gt;  #include &amp;lt;linux/module.h&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 14 Jun 2007 12:03:29 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487554#M18747</guid>
      <dc:creator>Texiwill</dc:creator>
      <dc:date>2007-06-14T12:03:29Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initiali</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487555#M18748</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Where can i get vmmemctl-only.patch ???&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Nov 2007 08:10:49 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487555#M18748</guid>
      <dc:creator>nikv</dc:creator>
      <dc:date>2007-11-15T08:10:49Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initializing</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487556#M18749</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We just had simular issue after upgrading vmware tools on CentOS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Fixed it by upgrading virtual Hardware and reruning vmware tools config tool.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Nov 2010 20:53:24 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487556#M18749</guid>
      <dc:creator>SashaGrybyuk</dc:creator>
      <dc:date>2010-11-04T20:53:24Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initializing</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487557#M18750</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Seen this exact same issue on RHEL VMs after Linux kernel updates.&amp;nbsp;&amp;nbsp; I think the VMware driver fails. Reinstalling VMware tools (manual or unattended) then reboot and network was back fine.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Mar 2014 15:47:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487557#M18750</guid>
      <dc:creator>virtualsmoot</dc:creator>
      <dc:date>2014-03-11T15:47:00Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initializing</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487558#M18751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="line-height: 1.5em; color: #000000; font-size: 10pt;"&gt;Hi &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em; color: #000000;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em; color: #000000;"&gt;Take a look in /etc/udev/rules.d for the networking file on the vm and check the MAC addresses there. &lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt; line-height: 1.5em; color: #000000;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Tahoma, Helvetica, Arial, sans-serif; background-color: #f5f5f5;"&gt;You can remove the persistent udev rules file and let it regenerate:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Tahoma, Helvetica, Arial, sans-serif; background-color: #f5f5f5;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; background-color: #f5f5f5; font-family: 'courier new', courier;"&gt;service network stop&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; background-color: #f5f5f5; font-family: 'courier new', courier;"&gt;rm /etc/udev/rules.d/70-persistent-net.rules&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Tahoma, Helvetica, Arial, sans-serif; background-color: #f5f5f5;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; font-family: Tahoma, Helvetica, Arial, sans-serif; background-color: #f5f5f5;"&gt;Then remove the HWADDRESS from the ifcfg-ethX file all together&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; background-color: #f5f5f5; font-family: 'courier new', courier;"&gt;start_udev&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000; background-color: #f5f5f5; font-family: 'courier new', courier;"&gt;service network start&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000;"&gt;take a look at&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000;"&gt;&lt;A href="http://alexcline.net/2011/11/15/reconfiguring-network-interfaces-in-centosrhel-systems-cloned-with-vcenter/" title="http://alexcline.net/2011/11/15/reconfiguring-network-interfaces-in-centosrhel-systems-cloned-with-vcenter/"&gt;&lt;SPAN style="color: #000000;"&gt;Reconfiguring Network Interfaces in CentOS/RHEL Systems Cloned with vCenter &amp;amp;amp;laquo; AlexCline.net&lt;/SPAN&gt;&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000;"&gt;regards&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #000000;"&gt;Russ&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 Dec 2014 09:01:52 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487558#M18751</guid>
      <dc:creator>roconnor</dc:creator>
      <dc:date>2014-12-05T09:01:52Z</dc:date>
    </item>
    <item>
      <title>Re: ifup: vmnics device eth0 does not seem to be present, delaying initializing</title>
      <link>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487559#M18752</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: arial, helvetica, sans-serif; font-size: 12pt; text-align: justify;"&gt;Step1: Make sure that the MACADDR of the affected NIC in the ifcfg-eth'x' file is same as that of the MAC address in the advanced configuration of the NIC (From the VM settings)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #303030;"&gt;&lt;SPAN style="text-align: justify;"&gt;Step2: Then remove the file&lt;/SPAN&gt;&lt;SPAN style="font-weight: 600; text-align: justify;"&gt; /etc/udev/rules.d/70-persistent-net.rules&lt;/SPAN&gt;&lt;SPAN style="text-align: justify;"&gt; and reboot your system.&lt;/SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: arial, helvetica, sans-serif; font-size: 12pt; text-align: justify;"&gt;# rm /etc/udev/rules.d/70-persistent-net.rules&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #303030;"&gt;VMware workstation : 12.1.1 build-3770994&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #303030;"&gt;RHEL: 6.5&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #303030; font-family: arial, helvetica, sans-serif; font-size: 12pt; text-align: justify;"&gt;Worked like charm!!!!!&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 17 Mar 2019 13:07:54 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VI-VMware-ESX-3-0-Discussions/ifup-vmnics-device-eth0-does-not-seem-to-be-present-delaying/m-p/1487559#M18752</guid>
      <dc:creator>jackril</dc:creator>
      <dc:date>2019-03-17T13:07:54Z</dc:date>
    </item>
  </channel>
</rss>

