On Fri, Oct 22, 2010 at 11:45 AM, L. V. Lammert <span dir="ltr"><<a href="mailto:lvl@omnitec.net">lvl@omnitec.net</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Visited a new client this AM, .. they had a pretty sweet setup - 5 VMs<br>
separated into services (web, email, ..), separate physical Windoze<br>
machine.<br>
<br>
They have a user & root login to the machine that responds to the monitor<br>
& keyboard, but it has no ssh key traces of connection to the other<br>
four machines.<br>
<br>
Apparently, they have a VMWare environment (recognized name over Xen or<br>
VirtualBox - the system was build two years ago, so VB is most likely not<br>
a choice), however I see no evidence OF the environment - the console is<br>
connected to the first VM, and no evidence of ssh config to the other<br>
machines.<br>
<br>
Have not done much VMWare myself, .. is this common in the VMWare world?<br>
Assuming there is a DOM0 in place, why would it not be connected to the<br>
console? How does one connect with the VMWare hypervisor, or to the VMs<br>
for maintenance work?<br><br></blockquote><div>Would this perhaps be an ESX installation?</div><div><br></div><div>In ESX, I would expect to see a VM solely for control of the VM environment, and it would be at system level, with none of the usual connections we're accustomed to.</div>
<div><br></div><div>I heard recently that one problem with ESX is finding the 'just right' hardware to run it. It can be somewhat restrictive on hardware unless you choose just the right configuration, usually pretty high end.</div>
<div><br></div><div>Anyone else with actual experience with ESX?</div><div><br></div><div>--Don Ellis </div></div><br>