ESX is linux based, it is a proprietary flavour designed by vmware
themselves in which is a non locking filesystem and is geared toward the
storage of extremely large files.
Vmware Server is Linux and Windows based (We run vm's mostly on Ubuntu
Server hosts haven't bothered with the GUI) and you are right,
irritatingly enough the windows version has less tools than the linux
version e.g. I just checked and vmrun and vmware-ping don't exist
however vmware-cmd does in all versions therefore retrieving the status
of the Guests is easy peasy (although just to be really annoying vmware
installer doesn't add the path the the vmware install directory to the
environment path variable so you need the full path of the exe to run or
manually add)
.
Executed and restarted yes can be done "vmware-cmd <path to vmx>
start|stop" (By adding a 1 at the end you can also force instant
poweroff if I remember rightly). The real problem is if "vmware-cmd
<path to vmx> getstate" reports "stuck" as you then need to provide
answers to quetsions which can be done manually by "vmware-cmd <path to
vmx> answer", I wouldn't like to try to do this automatically as the
different stuck states could be one of many.
To be truly remote vmare provide perl and com API's which are included
with the Server console download on the vmware website. This allows you
to simply use provided dll files for COM which I presume you would be
most interested in to interrogate / manage remote vmware Servers. I
suspect that this would be the most useful as it provided a scipted
interface to vmware Server which I suspect would work with ESX as well
(Untested though, as I believe that Server Console does work with ESX
but would require someone running ESX to confirm as I only tested
briefly).
I myself have used the vmware perl interface to suspend and restart
remote guests prior to taking a full backup, although I have since
discovered that this isn't necessary merely adviseable.
Mark Perry
Systems & Networks Administrator
Telephonetics VIP Ltd
"making sound
business sense"
Simply dial +44 (0)1442 242 242 and ask for me by name.
www.telephoneticsVIP.co.uk
Providing innovative hosted and customer premises speech recognition and
voice automation solutions.
Disclaimer: available at
http://www.telephoneticsVIP.co.uk/telephonetics/emaildisclaimer.jsp or
by sending email to <mailto:[EMAIL PROTECTED]
applies to this email.
Registered address: 7th Floor, Hamilton House, 111 Marlowes, Hemel
Hempstead, Hertfordshire HP1 1BB
Registered in England No: 2831215
-----Original Message-----
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Dirk Bulinckx
Sent: 03 December 2007 10:30
To: Servers Alive Discussion List
Subject: RE: [SA-list] Virtualisation
I thought that ESX was Linux based while the VMWare server was Windows
based.
So I guess that the tools are different.
Also the big question is then can they be executed/started from a remot
esystem.
For a Linux based system we can use an SSH connection to execute the
command and check the return, as we currently have for the diskspace and
process checker for *NIX. Not sure how we can do that for a Windows
based system IF there are no options in the cmdline to call the remote
system.
Dirk Bulinckx.
-----Original Message-----
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Mark Perry
Sent: Monday, December 03, 2007 11:21 AM
To: Servers Alive Discussion List
Subject: RE: [SA-list] Virtualisation
We use the cheap and cheerful Vmware Server Edition ;0)
It would be useful to have alerts for the state of Virtual Machines,
Vmware has many programs that can be run on the command line, if my
understanding is correct Vmware console is mostly a wrapper for these
utilities. I believe that ESX has pretty much the same utilities as
Server but with obviously enhanced capabilites e.g.
vmrun list (will list all running vm's in all versions of vmware)
vmware-cmd -l (will list all registered vm's running or not)
vmware-ping <hostname or ip> (will give a one line return if the machine
is reachable which is useful to test state of machine if in host-only
mode or configured in another network such as a test domain, although
would only be reachable by the Vmware host it is running on)
vmware-cmd <path to vmx file> getstate (tells us if the machine is
running, off or stuck in which case user intervention is required, this
would be very useful to monitor)
These are just a few things which would be useful and I have tried to
cite examples which would apply more to SA.
Mark Perry
Systems & Networks Administrator
Telephonetics VIP Ltd
"making sound
business sense"
Simply dial +44 (0)1442 242 242 and ask for me by name.
www.telephoneticsVIP.co.uk
Providing innovative hosted and customer premises speech recognition and
voice automation solutions.
Disclaimer: available at
http://www.telephoneticsVIP.co.uk/telephonetics/emaildisclaimer.jsp or
by sending email to <mailto:[EMAIL PROTECTED]
applies to this email.
Registered address: 7th Floor, Hamilton House, 111 Marlowes, Hemel
Hempstead, Hertfordshire HP1 1BB
Registered in England No: 2831215
-----Original Message-----
From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On
Behalf Of Dirk Bulinckx
Sent: 30 November 2007 19:51
To: Servers Alive Discussion List
Subject: [SA-list] Virtualisation
Just wanted to see if any of you are using some virtualisation software
(like VMWare SERVER, VMWare ESX, XEN, ...).
We are "looking" at it to see if it can be usefull to have some checks
for it
:-)
Dirk Bulinckx.
To unsubscribe send a message with UNSUBSCRIBE as subject to
[email protected] If you use auto-responders (like out-of-the-office
messages), then make sure that they are not send to the list nor to the
individual members of the list that send a message. Doing this will get
you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to
[email protected] If you use auto-responders (like out-of-the-office
messages), then make sure that they are not send to the list nor to the
individual members of the list that send a message. Doing this will get
you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to
[email protected] If you use auto-responders (like out-of-the-office
messages), then make sure that they are not send to the list nor to the
individual members of the list that send a message. Doing this will get
you removed from the list.
To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected]
If you use auto-responders (like out-of-the-office messages), then make sure
that they are not send to the list nor to the individual members of the list
that send a message. Doing this will get you removed from the list.
