Hi,
VirtualBox seems to be very efficient when saving the contents of a VM's
memory. If your VM just booted, saving its state will take less than a
second, while saving a VM that, for example, has been fetching many
things over NFS (and therefore has full caches claimed by the OS) will
take its time because almost all $memsize has to be written down.
How does VB know what parts of memory have to be saved and is there a
way to influence this by some trivial action inside of the VM?
Thanks,
Petar Bogdanovic
_______________________________________________
vbox-dev mailing list
vbox-dev@virtualbox.org
https://www.virtualbox.org/mailman/listinfo/vbox-dev
