socratis wrote:"signal 6" is a libc memory allocation error AFAIK.
But I have a more "basic" question. When you run that command (why as root?) someone is logged in, there is a window manager responsible for actually drawing the VM. When you run that cron job, where's that VM going to be displayed? Is anyone logged in?
"Why root", because root is doing a system-wide backup, which includes backing up the VM. It first shuts down the VM via 'su mfoley --command "/usr/bin/VBoxManage controlvm WIN7VM savestate"'. Note that the script actually runs through the list of running VMs (in case there is more than one -- there isn't really, but just in case) shutting them down in the save state and logging which ones were shut down for later. After the backup is complted, the root cron job attempts to restart the VMs based on the log of ones shut down.
Yes, there is a user logged in on Linux. I am using KDE and if the user running the VM logs out it shuts down the VM, in which case the root cron job won't find a VM to shutdown and hence won't attempt to start it. I am expecting the VM to be displayed on that logged in user's screen.
When, as that logged in normal user, I 'su' to root and run the startvm, it fires up just fine. Since I'm doing that as root, why is it any different that root doing that in a cron script? This particular restart VM error is consistent with 3 VMs on 3 different Linux workstations.
How about if you try either of the following commands:
Well, I don't want it to be headless. The idea is to backup production workstations and have the user none the wiser the next morning, especially if lots of windows with unsaved files are left open at end of day, which is typical!
Also, from ch.
2.3.5 Starting VirtualBox on Linux:
All VirtualBox applications (VirtualBox, VBoxSDL, VBoxManage and VBoxHeadless) require the VirtualBox directory to be in the library path:
OK, this gives me a clue! I was wondering if something needed to be set in the environment. Unfortunately, LD_LIBRARY_PATH is not set even with an interactive logon, but I'll try listing the ENV in both interactive and cron modes and see if there is some difference. (to be honest, I'm not sure what that env set command does. When I run 'LD_LIBRARY_PATH=. VBoxManage showvminfo WIN7VM' LD_LIBRARY_PATH is not set to anything)