Page 1 of 1

Does VirtualBox free allocated resources when VM is saved?

Posted: 23. Feb 2014, 22:33
by loostro
Hi,

recetly (due to mouse lag problem) I had to increase the number of CPU units allocated to my VM to 4 (out of 8 on my host machine). To speed up opening I did not close the VM - I saved it instead.

However, I am experiencing computer slowdown, when useing NetBeans IDE (its slower than before I used VirtualBox) and my Process Monitor sais the only thing useing CPU more than 1% is JAVA.

Now that could be Netbeans IDE (it's written in JAVA), but since it worked well before (and there was no update to it, i'm editing the same project as before, and the project itself did not grow much) I started suspecting, that when in "SAVED" state - the VirtualBox does not acctually "free" the 4 CPUs allocated to the VM.

Could anyone confirm/deny that?

Re: Does VirtualBox free allocated resources when VM is save

Posted: 24. Feb 2014, 01:18
by Perryg
Only way to change the number of processors is hotplug, or shut the guest down (not saved state)
hotplug must be setup in advance while the guest is shut down.

Re: Does VirtualBox free allocated resources when VM is save

Posted: 24. Feb 2014, 05:28
by socratis
loostro wrote:I started suspecting, that when in "SAVED" state - the VirtualBox does not acctually "free" the 4 CPUs allocated to the VM.
That suspicion is not accurate. When the VM is in the saved state all of the resources are returned to the host. The process is not active any more, so it consumes neither RAM nor CPU.
As for your original problem (mouse lag on the host) I would check the available RAM and the disk activity on your host.

Re: Does VirtualBox free allocated resources when VM is save

Posted: 3. Mar 2014, 18:51
by loostro
Hi,

thanks for the anwser. After a few days I found that the new version (Netbeans IDE 7.4) is being reported as slower (than 7.3) by many users. I fixed my problem by reverting to netbeans IDE 7.3.

So, in my process manager, the `java` process (slowing the computer down) was Netbeans IDE 7.4, not VirtualBox.