Paul G. Allen wrote:
Brinkley Harrell wrote:
The next logical extension from here would be to move to VmWare's ESX
server and run a minimal hypervisor architecture and maximize the
vm's footprint space.
The data center where Greenest Hosts servers are located uses ESX.
It's a managed center so I have limited access to VMWare and no access
to the actual hardware (and now that I'm working in "maintenance mode"
and "we'll call you when something breaks", I'm hardly accessing
anything at all. Until ESX migrates one of our servers.
Then all hell breaks loose. Such a migration happened about two weeks
ago. Suddenly, the web server could not reliably connect to the
database server. After three days of fscking with it, we moved the
important web sites and databases to another data center. Those web
sites and the DB server work perfectly fine.
Another problem is that whenever a server is migrated or rebooted, the
NIC configurations get hosed. We end up with duplicate IPs and aliases
that either don't belong or are incorrect. The config files are
present and correct, but the NICs are always mis-configured and I have
to reset them.
Things seem to work fine again for a while after such a migration, and
then a server gets migrated again, and the cycle repeats. Another
admin friend of mine said he's come across the same problem in the
past with ESX.
So, either the admins at the data center are clueless (along with the
VMWare experts they pay to help support them) and are configuring
something wrong in VMWare, or VMWare ESX has serious problems.
What you describe is totally atypical for my experiences in VmWare
(Workstation, Server, or ESX server).
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Brinkley Harrell
http://www.fusemeister.com
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
