Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • Good thought, but this would warrant that guest VM be reachable via network from the host, atleast the ssh port(22). Commented Jan 8, 2012 at 17:30
  • Basically, this would work, the appliance can be reached in the entire LAN via its DNS entry. However, suppose I wrote a script that ssh'd into the appliance whenever the host goes down -- it would still have to block (pause) until the guest has shut down completely. This is precisely the point of my question: How can the script know when the guest is down, so that it can yield control flow back to SysV-Init and the host can continue to shut down? Commented Jan 8, 2012 at 19:35
  • 1
    Your comment assumes that everything will work smoothly on host system and not on guest system. What if power cable is plugged out on host system? Its a different discussion. Your SysV-init on host system will wait for the service script to stop the VMs as long as service script understands the logic to get the guest VMs off in a right way (exec shutdown on remote host or just power off through vbox interface) and then yield return the success or failure status back to console or init. Commented Jan 8, 2012 at 20:02
  • 1
    Regarding: how script knows when the guest is down, try a simple check if the vm is on or off from VboxManager interface and if the guest is ssh'able. Also, put some monitoring on the host system which will perform whether the VM is available from Vboxmanager and its ssh'able on a timely basis. Commented Jan 8, 2012 at 20:05