Problem with Virtualbox and save state VM

[boxino]

Use virtualbox and as main machine using Debian. I often hibernatei and various restorations and unfortunately if i store the state of a VM this, if I use one of the methods above, should be deleted it. Error: "The VM session was closed before any attempt to power it on." I modified in preferences the default folder on external disk, and the snapshot folder machine identically. I have the distinct feeling that VBox store something else somewhere else ... Yes, but what? Solution / suggestion ? Help me!

Log:

Code: Select all

VirtualBox VM 5.1.6 r110634 linux.amd64 (Sep 12 2016 17:55:26) release log
00:00:00.403183 Log opened 2016-11-23T17:20:50.410452000Z
00:00:00.403184 Build Type: release
00:00:00.403186 OS Product: Linux
00:00:00.403187 OS Release: 3.16.0-4-amd64
00:00:00.403188 OS Version: #1 SMP Debian 3.16.36-1+deb8u2 (2016-10-19)
00:00:00.403210 DMI Product Name: Notebook
00:00:00.403217 DMI Product Version: 1.0       
00:00:00.403382 Host RAM: 7889MB total, 7339MB available
00:00:00.403385 Executable: /usr/lib/virtualbox/VirtualBox
00:00:00.403386 Process ID: 3104
00:00:00.403387 Package type: LINUX_64BITS_DEBIAN_8_0
00:00:00.403940 ERROR [COM]: aRC=VBOX_E_FILE_ERROR (0x80bb0004)
aIID={8da64572-4a0b-8501-jde3-9eed7902105b} aComponent={ConsoleWrap}
aText={VM cannot start because the saved state file
'/media/ilmiopc/discossd/cartelladefinita/SnapShot/2016-11-23T16-40-08-750972000Z.sav'
is invalid (VERR_FILE_NOT_FOUND). Delete the saved state prior to starting
the VM}, preserve=false aResultDetail=0
00:00:00.404043 GUI: Aborting startup due to power up issue detected...
00:00:00.404177 GUI: UIMediumEnumerator: Medium-enumeration finished!

[mpack]

Partial logs are not useful to us.

Please provide a VM log file. With the VM fully shut down, right click it in GUI. Select "Show Log" and save "VBox.log" (ONLY) to a zip file. Attach the zip here.

[boxino]

I make vbox.log and i compressed in a zip file.
I noticed these some lines that seem to coincide with the configuration that I gave to save everything on the external drive.

Code: Select all

00:00:00.591053   GlobalInitScript <string>  = "/home/ilmiopc/.config/VirtualBox/dbgc-init" (cb=49)
00:00:00.591055   HistoryFile      <string>  = "/home/ilmiopc/.config/VirtualBox/dbgc-history" (cb=52)
00:00:00.591056   LocalInitScript  <string>  = "/home/ilmiopc/VirtualBox VMs/Machinevirtualizzata-1/dbgc-init" (cb=58)

00:00:00.591057 [/DBGF/] (level 1)
00:00:00.591058   Path <string>  = "/home/ilmiopc/VirtualBox VMs/Machinevirtualizzata-1/debug/;/home/ilmiopc/VirtualBox VMs/Machinevirtualizzata-1/;/home/ilmiopc/" (cb=125)

See you!

[mpack]

Thanks, however I do not see the described error in the log file provided. I need a log file which shows the problem.

I see also that you are still on 5.1.6. It would be better if you were on the current version, 5.1.10, so we can tell if any problem hasn't already been fixed.

[Perryg]

Code: Select all

00:00:00.591022   NumCPUs           <integer> = 0x0000000000000004 (4)

00:00:00.713585 CPUM: Logical host processors: 4 present, 4 max, 4 online, online mask: 000000000000000f
00:00:00.713632 CPUM: Physical host cores: 2

Assigning all vCPUs to a guest is never a good idea and especially when you want to use things like hibernate. I would try with a single core and see if it works like you request. Another thing I see is you are using a removable media device to store your guests files ( /media/ilmiopc/disco-2/ ). This will work but timing can be a real issue when recovering from hibernation. These mounts are not handled the same as a real drive mount including permissions which need to be re-initialized when resumed. Make sure that you have a proper mount statement and not just the auto-mount of the device.

[boxino]

I installed the 5.1.10 version and its estention pack. I installed in the driver vmbox machines. The problem does not change. I enclose the two logs. I used the hard disk to avoid mistakes. I will continue to believe that the problem is here:

Code: Select all

00:00:00.964175 [/DBGC/] (level 1)
00:00:00.964177   GlobalInitScript <string>  = "/home/ilmiopc/.config/VirtualBox/dbgc-init" (cb=49)
00:00:00.964178   HistoryFile      <string>  = "/home/ilmiopc/.config/VirtualBox/dbgc-history" (cb=52)
00:00:00.964179   LocalInitScript  <string>  = "/home/ilmiopc/VirtualBox VMs/DebMate/dbgc-init" (cb=59)
00:00:00.964179 
00:00:00.964180 [/DBGF/] (level 1)
00:00:00.964181   Path <string>  = "/home/ilmiopc/VirtualBox VMs/DebMate/debug/;/home/ilmiopc/VirtualBox VMs/DebMate/;/home/ilmiopc/" (cb=127)

I think VMBOX does not save all files in the machine folder, and then to restore just that one file is not coordinated and restore does not work anymore. Is there a way to let go of all these files on a different partition or even better in the virtual machine folder? I try Vmplayer and it do not have this problem.
( i use translate.com)

[Perryg]

Both of these logs still show you using the media folder and that you still have over-committed the vCPUs. I suggested using one for a reason. However I do not try to hibernate the host while a guest is running due to there being so many ways that could go wrong. Saying that I will monitor but have nothing else to add at this point.

[boxino]

I think that the problem is storing some files in different folders that of the virtual machine. When it is restored located dates / time different and can not go on displaying the error. I tried to give a single cpu to the virtual machine, but the result does not change. I think the program need a fix from developers. it is necessary to open a ticket (where?) or just tread is sufficient as a warning?

[socratis]

You can continue to think where the problem is, or you can follow the instructions and try to fix it. In your first report you talk about "hibernate". Just to get the terminology correct: there are two ways to put temporarily a VM to "sleep":

• Hibernate, where you put the VM to sleep from within the guest.
• Save the VM state from the host. This is what you did. It's not hibernate, it's called "Saved State".

So, just please follow the previous instructions and reduce the CPUs in the guest. Then:

1. Start the VM. Not from a saved or paused state. Clean start.
2. Take the steps required to generate/observe the error. Record the error message. EXACTLY. Post a screenshot if you have to.
3. Shut down the VM (if it hasn't aborted by itself). Not saved, not paused. Completely shut down. If you can't shut it down by normal means, close the VM window and select "Power off".
4. Right-click on the VM in the VirtualBox Manager. Select "Show Log..."
5. Save it (just the first log), ZIP it and attach it in your response (see the "Upload attachment" at the bottom of the form).

I would also like to see the "recipe" of the VM, the ".vbox" file:

1. Right-click on the VM in the VirtualBox Manager. Select "Show in Finder/Explorer/Whatever".
2. ZIP the selected ".vbox" file and attach it in your response.