Re: Beginnning to think about VMware and SCO 5.0.5
- From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
- Date: Sun, 29 Jun 2008 08:34:28 +0100
Pepe wrote:
Pepe wrote:(a) stopping the Openserver virtual machine at night, and copying the files via ethernet from server A to NFS in server B, and then restarting the virtual machine (I think "VMware Server" is scriptable via perl, anyone?)
Well, it seem that not only the virtual machines on the expensive VMware ESX host can be scripted, but also the startup/shutdown of virtual machines in the free VMware Server host can be scripted:
http://www.petri.co.il/virtual_script_startup_shutdown_vmware_servers.htm
Oh, my. Look more closely at that page, particularly where it says:
> Notice what happened here. I was able to successfully stop second virtual machine (see the stop = 1 code) but could not stop the first machine. This is because the VMware Tools have not been installed on the first virtual machine. You must install these tools to make the vmware-cmd work. Thus, this first machine is still running.
There are no VMware tools for SCO operating systems: it's not a supported OS.
.
- Follow-Ups:
- References:
- Beginnning to think about VMware and SCO 5.0.5
- From: Steve M. Fabac, Jr.
- Re: Beginnning to think about VMware and SCO 5.0.5
- From: Nico Kadel-Garcia
- Re: Beginnning to think about VMware and SCO 5.0.5
- From: Bill Campbell
- Re: Beginnning to think about VMware and SCO 5.0.5
- From: Nico Kadel-Garcia
- Re: Beginnning to think about VMware and SCO 5.0.5
- From: Pepe
- Re: Beginnning to think about VMware and SCO 5.0.5
- From: Pepe
- Beginnning to think about VMware and SCO 5.0.5
- Prev by Date: Re: Beginnning to think about VMware and SCO 5.0.5
- Next by Date: Re: Beginnning to think about VMware and SCO 5.0.5
- Previous by thread: Re: Beginnning to think about VMware and SCO 5.0.5
- Next by thread: Re: Beginnning to think about VMware and SCO 5.0.5
- Index(es):
Relevant Pages
|