VBox as a service in Lucid

[Entilza]

Did you make the service do stop as well? (As per your scripts)

[CharlesA]

Did you make the service do stop as well? (As per your scripts)

The script is set to save the state of any running VMs on system shutdown/reboot.

You can also do that manually like so:

sudo service vmboot stop

[Entilza]

Ah cool, I was looking at the individual start / stop. You have the combined one as well listed, thanks.

So is this the proper way to shutdown guest machines if the host system goes down? I would probably prefer to shut them down individually?

ie: Host Ubuntu, guest: Win7 In order to shutdown win7 fully you would have to send a shutdown signal but I don't think this is possible through vbox? Atleast without some sort of program listening on the guests and waiting for a shutdown signal..

[CharlesA]

You can send a shutdown signal via vbox. I have been using savestate so I can pick up where I left off instead of having to restart what I was doing on the VM.

[doas777]

well, I've tried it over a few days and I like it thus far. i am having a problem with the stop however. I added syslogging to the script so i could confirm that it was reacting to the events correctly, and that in itself appears to be working fine, but I am not getting any logs from the shutdown event unless I stop the service manually.

I've attached my mutant version, in case you see a problem there.
I'm going to try adding a flag file at shutdown to see if I can confirm the event is firing but perhaps after the logging service has stopped.

Thanks!

[CharlesA]

Have you tried adding $local_fs and $syslog to the requires areas?

http://wiki.debian.org/LSBInitScripts

I'm not even sure I wrote that part correctly, but it looks right.

[doas777]

interesting.

ok,I've added those items start/stop dependency list, but I'm still not getting log messages on the stop, unless I stop the service manually from the shell. service start works as expected.

per the LSB init specs, I added restart and force-reload clauses as well just in case. I've been removing and resetting the service with update-rc.d on each change before testing.

my latest version is attached. see anything amiss?

[CharlesA]

Looks fine to me.

It sounds like the system logger is being stopped during shutdown before the commands are being run. or something. I'm not sure how to fix that.

BTW: Nice mod with the functions.

[doas777]

It sounds like the system logger is being stopped during shutdown before the commands are being run. or something. I'm not sure how to fix that.

looks like that is exactly the case. I had it touch a file in /var/log after it stops the vm without error, and that file does get created on reboot, so I guess all is in working order. as long as its working, I'm not so worried about the logging.

Thanks for all your help with this. I've enjoyed working with you and learning about service configuration.
cya 'round

[CharlesA]

No problem, glad you (sorta) got it figured out.