kjpetrie, thanks for helping out, much appreciated!
Check the permissions and ownership of the Machines folder and its contents. I take it it's not a mount point for a partition or share, then.
Yes and no - insofar as my /home is on its separate partition... but it is in its default place, if that's what you mean.
Also, have you tried running VirtualBox from a terminal to see whether there are any error messages when saving the machine state.
I tried both starting the machine (VBoxManage startvm "BONZO_XP_ASP" --type gui) from terminal, as well as VirtualBox: no errors given, and all seems fine until the next reboot.
Do you save other things successfully to your home partition, even after a reboot? Silly question, I know, but it needs to be asked.
Yes, no problem there.
Ok, I think we are one step nearer to the problem: I just noticed that one
of my machines actually do get saved, even after reboot. (I should have noticed earlier, I don't use this particular machine very often, sorry.)
The difference? The path to the Snapshot folder!
The one that works is saved to ~/VirtualBox/Machines/<machine_name>/Snapshots; the others are set to save to a Snapshot folder on the separate partition where I also have the .vdi files.
I have checked the permissions between the two Snapshot folders - as well as the save files in them - and there is no
Additionally, I can see that the .sav files are
being saved to... at least, the last modified date/time stamp does update.
Thirdly, if the permissions were the issue, why would it work until a reboot and then not?
So... what can cause this, i.e. a .sav file that can be saved and
read - until after a reboot where it cannot be read?
I guess I could change the Snapshot location to the one in the /home/Machines/etc. that I know work, but I would rather have it on the separate partition... not to mention, I would really like to know why this is going on... if at all I could!
Any ideas? I am stumped.