VirtualBox causing big peaks in CPU

NoOp glgxg at
Wed May 7 19:27:28 UTC 2008

On 05/07/2008 09:46 AM, Paolo wrote:
> Nils Kassube wrote:
>> Better wait for 1.6.2 because NoOp pointed out yesterday that there is a 
>> network problem in version 1.6.
> Thanks. I've already gone ahead and installed 1.6
> I don't need to use networking -- just web access is ok.
> But I haven't got USB working yet, despite following
> Paolo

I ended up backing down to 1.5.6. & will wait for 1.6.2.

For your memory:

>From the 1.6 manual:
3 Starting out with VirtualBox
Note: Choose this setting carefully! The memory you give to the VM will
not be available to your host OS while the VM is running, so do not
specify more than you can spare. For example, if your host machine has 1
GB of RAM and you enter 512 MB as the amount of RAM for a particular
virtual machine, while that VM is running, you will only have 512 MB
left for all the other software on your host. If you run two VMs at the
same time, even more memory will be allocated for the second VM (which
may not even be able to start if that memory is not available). On the
other hand, you should specify as much as your guest OS (and your
applications) will require to run properly.
A Windows XP guest will require at least a few hundred MB RAM to run
properly, and Windows Vista will even refuse to install with less than
512 MB. Of course, if you want to run graphics-intensive applications in
your VM, you may require even more RAM.
So, as a rule of thumb, if you have 1 GB of RAM or more in your host
computer, it is usually safe to allocate 512 MB to each VM. But, in any
case, make sure you always have at least 256-512 MB of RAM left on your
host operating system. Otherwise you may cause your host OS to
excessively swap out memory to your hard disk, effectively bringing your
host system to a standstill. As with the other settings, you can change
this setting later, after you have created the VM.

I find that 256KB is fine for Win2KPro on my machine.

For your USB: Are you running the OSE or the PULE? I used these & added
the entry in my fstab:


none /proc/bus/usb usbfs devgid=124,devmode=664 0 0
[on mine, the devgid=131]

More information about the ubuntu-users mailing list