You can give a process more CPU time relational to other processes by re-nice-ing it. For example, run
pgrep VirtualBox
to get the PID of VirtualBox. If more than one number pops up, you should run top to see which one is using all the CPU - this is likely to be the one you want to fiddle with. The PID is the first column.
Then you can do:
renice -5 PID
would give PID a nice value of -5. This gives it more CPU time than other processes competing for it.
"Niceness" ranges from -19 to 20; -19 is least-nice, meaning gets the most CPU time. 0 is the default. renice must be run as root, i.e., with sudo, to change "niceness" to anything below 0.
The changed niceness only lasts as long as the process runs; it will no longer be in effect after quitting VirtualBox, for next time you run it. (So you'll have to do it again each time.)
I don't think you can change the amount of RAM given to a VirtualBox guest at runtime. This would need to be done before booting it, in the virtual machine configuration.
You can give a process more CPU time relational to other processes by re-nice-ing it. For example, run
pgrep VirtualBoxto get the
PIDof VirtualBox. If more than one number pops up, you should runtopto see which one is using all the CPU - this is likely to be the one you want to fiddle with. ThePIDis the first column.Then you can do:
renice -5 PIDwould give
PIDa nice value of-5. This gives it more CPU time than other processes competing for it."Niceness" ranges from -19 to 20; -19 is least-nice, meaning gets the most CPU time. 0 is the default.
renicemust be run asroot, i.e., withsudo, to change "niceness" to anything below0.The changed niceness only lasts as long as the process runs; it will no longer be in effect after quitting VirtualBox, for next time you run it. (So you'll have to do it again each time.)
I don't think you can change the amount of RAM given to a VirtualBox guest at runtime. This would need to be done before booting it, in the virtual machine configuration.