Chris,
As far as I can see its not happening anymore after the ( boot->stall->shutdown->nic_disconnect->boot->NO_stall->shutdown->nic_connect->boot->NO_stall
I rebooted five time in a row the three VM(deployed from template) that all showd the routing error. After the nic (dis)connect, they no longer throw the error message.
I though perhaps it may be a time-related issue, so one of those VM's that i've had running for a few days now I just did the following:
Gracefull reboot (init 6)
Gracefull shutdown (init 0)
Hard reset (power reset)
Hard shutdown (power off/on)
On each method, the VM came up with no IPV4 routing error. However, as I mentioned before the INIT step of "Bringing up interface eth0" which should only take a few seconds.... literally took 34 seconds to throw back the [OK] status. So, I think something may still be going on under the covers. 34sec is exceedingly long for bringing up a network interface.
Kernel:
Linux labvm01 2.6.32-279.14.1.el6.x86_64 #1 SMP Tue Nov 6 23:43:09 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
OS:
CentOS release 6.3 (Final)
VMware-Tools version:
VMware Tools daemon, version 9.0.0.15210 (build-782409)
I've attached the vmware-tools debug log, and the /var/log/message snip (shows kernel post messages)
I googled around a bit and I saw some mentioning that this could be related to RTC on the hypervisor, and or time on the VM, or perhaps IPV6? Just throwing darts at this point, seems unlikely ;-)
