VirtualBox image crashes with > 4GB base memory

Discussions related to using VirtualBox on Windows hosts.
Post Reply
Anj
Posts: 1
Joined: 8. Oct 2012, 08:52

VirtualBox image crashes with > 4GB base memory

Post by Anj »

Hi

My VirtualBox image crashes with when allocated more than 4GB base memory. Please help, details below:
  • 1. Successfully deployed a VirtualBox image with no errors and the following settings:
    - base memory(3.584GB)
    - Enable PAE/NX = Y
    - hwvirtex = off (to resolve startup error "VT-x is not available. (VERR_VMX_NO_VMX)" when base memory is increased above 4GB)
    - network = NAT
    2. Increased the base memory to 12GB, and started image. However when trying to run any process the VirtualBox image crashes with error "Not in text mode"
    - Log file attached
    3. Environment details:
    - host: Windows Server 2008 R2 (64-bit)
    - guest: Oracle Linux 5 (32-bit)
    - virtualbox: 4.2.1 r80956
Thanks in advance,
Andrzej

[mod edit] For future reference, you wouldn't have needed to edit and split your log file attachment(s) if you uploaded it as a zip. I did it for you this time.
Attachments
VBox.log.zip
(32.36 KiB) Downloaded 1 time
mpack
Site Moderator
Posts: 39134
Joined: 4. Sep 2008, 17:09
Primary OS: MS Windows 10
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Mostly XP

Re: VirtualBox image crashes with > 4GB base memory

Post by mpack »

To run a 64bit guest, you need VT-x (if not available you get the "no VTx-x" error), however VT-x can only be used if nothing else is using it - otherwise you get the "VMX locked" error. I'm not sure if assigning more than 4GB to a guest requires VT-x support... but I wouldn't be surprised.

ps. "Not in text mode" is not an error message, it's just a statement of fact. The error recording feature tried to grab the blue/blackscreen information you sometimes get from the text mode shell (of some OS's) on a crash, but it couldn't because there was no shell.
Post Reply