The network latency I referred to would be for running ESXi, as
opposed to on a VMWare host machine. The guests run on the ESXi box,
but all remote access really is "remote" since there is no browser on
the ESXi box, only a "bios-like" interface. When Hao Wu was back from
China he talked about his outsourcing company near Hong Kong. They
have 200 developers working for a well-known U.S. company. No client
software is installed in China. All the developers connect to virtual
desktops maintained by the client in the US. That must be running on
something like ESXi. I sent him an email to ask.
Here is a link to a 3-hour webinar on VMWare ESXi that I watched last
night:
http://www.vmware.com/a/webcasts/details/201. The first 90
minutes are an overview of virtualization that are useful no matter
what VMWare product(s) that you run. The second 90 minutes show a
ESXi install, configuration, and creating a couple of guests.
The ESXi kernel and drivers are only tested on server class hardware
(xeon and opteron), but I found several posts like this one,
http://communities.vmware.com/message/1088200, about running EXSi on
desktop hardware (amd Phenom). Had I chosen that route, it looks like
all I would have to do is add a SATA controller since the ESXi
firmware does not recognize integrated controllers.
In then end, ESXi to more than I need, and I don't want to dedicate a
box to run it. I'm going to follow your lead and stick with the VMWare
Server I installed on Ubuntu. I built my Solaris image in
compatibility mode, so I'll see if it will run on VMWare Fusion on my
MacBook Pro too. I don't believe I can remote into VMWare Server from
OS X. I'm not sure if I will install VMWare Workstation on my Vista
machine since that is not my primary machine and I don't anticipate
needing to run multiple guests there. I am anxious to see what is like
using the Solaris image from the Vista machine vs from the VMWare
Server host box. I'm upgrading to a gigabit switch to make it a fair
fight.
VMWare saved my bacon too a few weeks ago. I just happened to be
working on a project for a client that required Windows XP. We were
coming up on a deadline when the motherboard in my MacBook Pro failed.
I had an old copy of the XP image on my Vista machine, so I just fired
up VMWare Player, checked out the code from Subversion, and kept on
trucking. The customer wasn't effected by my laptop being gone for a
week.
On Jun 23, 8:14 am, Gary Murphy <
g...@hilbertinc.com> wrote:
> I took a quick look at ESXi when my hard drive failed, but I couldn't
> find a way to migrate my VMs and since I was in a "down time" scenario,
> I just went with VMWare Server again. I guess it's less opaque to me
> when there is a full OS anyway.
>
> I guess I don't really understand the question. The VMs running on the
> server only have *remote* consoles (even if accessed via 127.0.0.1), so
> I access them from my laptop usually, but sometimes from localhost. The
> VMWare Workstation product only has *local* consoles. If you want to
> access them remotely, it's ssh, VNC or Remote Desktop access - just like
> physical hardware. I use VMWare Workstation for a lot of reasons, but
> not for latency. Main reasons are:
>
> * The ability to run multiple OSs at once. For example Flex
> client/Java server development, the client runs on Windows and the
> server on Linux.
> * A custom installation of an OS for a special needs customer, such
> as the 64-bit Windows for the publishing customer.
> * Full OS backup and portability. If I get a faster laptop, all I
> do is move the VMs. There's no OS re-install and customization.
> * Disaster recovery. If I have a hardware failure, I get the last
> good VM copy and apply the subsequent backups and it works on
> whatever replacement hardware I got.
> * Setup of an environment for another developer. Set it up and