Debian guest aborted on suspend/resume

[cacheguard]

Hi

My host is a Debian Jessie 64 bits and I have a Debian Jessie 32 bit in a VM. The issue that I'm encountering is that whenever I suspend my host that guest is aborted. I don't have the same issue with a guest Windows 7.

I use VirtualBox v5.0.20 and I installed Guest additions on my Debian 32 bit guest. Power saving is completely off in the guest.

I have no idea where to begin investigate. If anybody could help me... Thanks in advance.

Best Regards

[cacheguard]

I just upgraded to the 5.0.22 but have still the same issue...
Nobody can help me to resolve my issue?
Any help is appreciated...
BR

[Perryg]

Post the guests log file ( as an attachment ). Right click on the guest in the Main Manager then click show log. Save and post as an attachment. Compress if it is too large to post.

[cacheguard]

Hi

Please find attached a recent log.
Thanks in advance

[Perryg]

I don't see any glaring issues and do see the suspend and resume. I guess the abort happens after the second suspend, can you verify that? I am curious about the extradata settings at the the top of the log though. What are these?

Code: Select all

00:00:00.981331   VBoxInternal2/SharedFoldersEnableSymlinksCreate="1"
00:00:00.981382   VBoxInternal2/SharedFoldersEnableSymlinksCreate/Backup="1"
00:00:00.981434   VBoxInternal2/SharedFoldersEnableSymlinksCreate/MyDir="1"
00:00:00.981486   VBoxInternal2/SharedFoldersEnableSymlinksCreate/MyDirm="1"
00:00:00.981536   VBoxInternal2/SharedFoldersEnableSymlinksCreatse/MyDir="1"

Also the additional drives

Code: Select all

00:00:00.501235 File system of '/home/me/VirtualBox VMs/Debian 8 x86/Debian 8 .vdi' is ext4
00:00:00.505342 File system of '/home/me/VirtualBox VMs/Debian 8 x86/LFS.vdi' is ext4
00:00:00.507418 File system of '/home/me/VirtualBox VMs/Debian 8 x86/CG.vdi' is ext4

You might want to try the latest upgrade of VirtualBox 5.0.24, but it also might be better if you raised a ticket at bugtracker

[cacheguard]

The following:

Code: Select all

00:00:00.981331   VBoxInternal2/SharedFoldersEnableSymlinksCreate="1"
00:00:00.981382   VBoxInternal2/SharedFoldersEnableSymlinksCreate/Backup="1"
00:00:00.981434   VBoxInternal2/SharedFoldersEnableSymlinksCreate/MyDir="1"
00:00:00.981486   VBoxInternal2/SharedFoldersEnableSymlinksCreate/MyDirm="1"
00:00:00.981536   VBoxInternal2/SharedFoldersEnableSymlinksCreatse/MyDir="1"

Allow me to create symbolic links from files/directories in my shared directories to files/directories that are located on my guest (32 bits machine). Without those settings VirtualBox does not allow me to do it for security reasons. But I really need those symbolic links to link a files/directories to distinct content depending on which environment I work (32 for the guest or 64 bits for the host).

LFS.vdi and CG.vdi contain other OS: LFS stands for Linux From Scratch and CG stands for CacheGuard. In my development environment I build those OS. I use distinct devices to have the possibility to boot on them for testing purpose (even if today I do my tests differently).

anyway I just manually suspended twice my VM and didn't have any issue... Strange. Maybe the automatic suspend (for energy saving) occurs differently or the issue happens after a long period of suspension... I'm lost

I'll try the new version and let you know.

Thanks again
Regards,

[Perryg]

Thank you for explaining. I in no way meant it as an issue, just curious as to why. I do unique things as well but never have I needed the symlink. Normal shares whether it LAN or shared folders have always worked.