virtualbox.org

I'm using VBox302 on a WinXPSP2 host with 1GB of RAM (not easily upgradable, sadly).

This morning I made a mistake, because I launched a VM while another one was running (actually in pause mode).
As the first machine uses 480MB of RAM, there was obviously not enough memory to run the second one.

I realized my mistake a few seconds after launching the second VM and was expecting the usual message that older VBox versions used to display in such a situation (something like "the VM can not be initialized because VB is unable to allocate the required memory") but, instead of that message, I got a sudden complete reset of the host system, without any kind of message or blue screen: something like the old DOS times.

I am not willing to try again, because I don't want to run any risks of messing up the host system's registry.
My question is: why didn't VBox issue the warning message? Is that a bug of the new version?

This is something that you should report to bugtracker. Link is below my post.

Perryg wrote:This is something that you should report to bugtracker.

That is right. I just wanted to know, before reporting, whether this problem had occurred also to other users.
In other word, I wanted to check if it should be considered an actual bug or not.

Anyway, I'll report to bugtracker at once.

I actually reported the above to bugtracker, but I received no answer.

I noticed however in the VB304 changelog the following line:

VMM: eliminated several bugs which could lead to a host reboot

which maybe means that the crash I had experienced actually was a bug which has been now hopefully fixed.

If it works correctly now then please go to the bug tracker and leave a comment that it is solved so that they can close the bug.