Re: Beginnning to think about VMware and SCO 5.0.5
- From: Pepe <pepe@xxxxxxxxxx>
- Date: Sun, 29 Jun 2008 15:45:41 +0200
Nico Kadel-Garcia wrote:
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.
Too true. But no worries. You can build an "expect" script to remotely shutdown (via telnet or ssh) the OpenServer guest running on the "VMware Server for Linux" server A, and then use the "vmware-cmd" also from server A to "physically" shutdown the virtual machine itself. Then you can copy the *.vmdk, etc., files form server A to NFS in server B, and then you can use again "vmware-cmd" in server A to start the OpenServer guest virtual machine.
It can all be done quite easily with scripts from Linux (I didn't know you needed X-Window to be able to run the "vmware-cmd" commmand in Linux, but anyway it is probably a non issue in this case, as I don't think Steve would mind installing X-Window into the Linux "VMware Server" to make it just work - in fact, given the state of Linux today, it would be much harder to manage a Linux installation without X than with them).
As for the "expect" script, it goes something like this:
#!/usr/bin/expect -b
log_user 0
spawn telnet 192.168.0.10
expect login:
send root\r
expect password:
send PasswordOfRoot\r
sleep 5
send "shutdown -y now and whatever Openserver needs here\r"
sleep 3
send exit
close
Then you wait 5 minutes with some "sleep" command, for OpenServer to display the ** Safe to poweroff ** legend (or more, or less, Steve should know how long it takes to shutdown his OpenServer application software), and then you issue the "vmware-cmd VMname stop" commmand from server A.
You could do the "expect" thing against ssh instead of telnet if you please. Yes, you need to put the root password in there somewhere, or you could give some "sudo" permissions to shutdown for some other user, YMMV... (yes, I know OpenServer does not have sudo but it has something to the same effect with another name which I don't remember now).
Regards,
Pepe.
.
- 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
- Re: Beginnning to think about VMware and SCO 5.0.5
- From: Nico Kadel-Garcia
- 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
|
