virtualbox.org

So I've been using virtual box for a while. I recently updated to 2.0 but none of my guests would run. The message basically says there's not enough memory. Now bear in mind I didn't change anything about the guest so where's this memory issue coming from? really obvious

Well I ending up having the take the guests (Windows 2000) and change the amount of memory from 128 MB to 256 MB which is serioutly going to limit the number of VMs running at the same time.


FYI - a quick update: As I was writing this I thought I'd try dropping the memory back after the intial start up and it's now working with the original memory configuration. Just plan weird!



I hope at least by postin this I've helped someone!

Where did the message about too less memory come from? From the guest?

The error comes up immediately after starting the guest.

I forgot to mension that the host is Windows XP Pro. It didn't matter which one of the Windows 2000 guest I had but it did affect all 4 I had.

ironspeeder, welcome to our forum. You might want to take this opportunity to browse the Forum Posting Guide. This contains some useful tips on how to search for VBox knowledge and how to frame Qs.

What Frank is asking is what exactly is the message and what produces this -- the VBox VM, the Windows OS during the boot sequence ...? "The message basically says there's not enough memory" just doesn't help us to help you.

If VB responds with a Low Memory message, it means you set too much RAM to the Guest. The Host has a limited amount of physical RAM that you can assign. If you have 512 MB RAM in your Host, you really should consider upgrading your RAM. As per the manual, you should let the Host have at least 200 MB left of RAM to work with after you allocate the memory for your VM. If the Host would be using 200 MB of RAM, and needs an additional 200 to work with for other programs, that leaves only 112 MB of RAM for the Guest.

The server has 2 GB Ram but it has more to do with the newer version of VB. Server ran fine all along. Upgraded to 2.0 and the VB's need to have their memory increased for startup. Once they started at about 384 MB I was able to lower the VB back to 128 after I shut it down and restarted it and everything is fine.

I suspect the problem is something that VB needs to perform some sort of maintenance to the machine and that's where the memory issue comes up. Once that's complete and can go back. I think I'll be able to reproduce the error and send a screen shot a little later.