Delay when starting a VM with previous state saved

[Rafael Fassi Lobão]

After turning on the computer, the first time I start the VM, it takes a long time to start restoring the machine state. After the first time I start the VM there is no problem. Also do not hesitate problem if I start a VM that does not possess the previous state saved. Viewing the log, it seems that the delay occurs in memory allocation.

00:00:01.575381 SUP: Loaded VMMR0.r0 (/usr/lib/virtualbox/VMMR0.r0) at 0xf9a88020 - ModuleInit at 00000000f9a9e4c0 and ModuleTerm at 00000000f9a9e820

00:00:01.575457 SUP: VMMR0EntryEx located at 00000000f9a9f9e0, VMMR0EntryFast at 00000000f9a9f730 and VMMR0EntryInt at 00000000f9a9f720

00:01:31.631232 File system of '/home/rafael/VirtualBox VMs/WinXp/Snapshots' (snapshots) is ext3

00:01:31.631268 File system of '/home/rafael/VirtualBox VMs/WinXp/WinXp.vdi' is ext3

But analyzing the allocated memory, I noticed that only begins to allocate memory after this long delay.

Visually, when I start a VM with previous state saved, open the window and the progress bar remains at 0% for a minute and a half. Soon after the progress bar begins to fill and I see on the monitor system memory allocation starts.

[Frank Mehnert]

I doubt that the delay comes from some memory allocation. Is the saved state located on some slow medium?

[Rafael Fassi Lobão]

The machine state is saved in the /home partition on my hard disk. I realized that while the progress bar remains at 0% nothing happens. Not consumed CPU processing, it is not accessing the hard drive. Not consumes memory. Looks like he is waiting for the response of some system service.