Opened 16 years ago
Closed 16 years ago
#3065 closed defect (fixed)
XP guest unable to allocate and lock memory
| Reported by: | Doug Roberts | Owned by: | |
|---|---|---|---|
| Component: | other | Version: | VirtualBox 2.1.0 |
| Keywords: | Urgent-yeah-I-Know-They-All-Are | Cc: | |
| Guest type: | Windows | Host type: | Linux |
Description
Hi.
I have a Kubuntu8.04 host with two quad-core Xeon 3.3 GHz cpus 8MB of physical memory, running the 2.6.24-23-server kernel so that all 8MB of memory is seen by Linux.
I have a Windows XP guest. When I try to configure the memory for the guest, the VirtualBox GUI only sees 3.584 MB of totall available memory, not the full 8. If I configure the guest to have access to 3.0 MB of memory, VirtualBox complains about HostMemoryLow and that it is unable to allocate and lock memory when I try to reboot the guest. Host memory is not low -- I still have 5MB free on the Linux host.
I need to be able to allocate at least 5BM of memory to the XP guest, but cannot do it via the gui. My log is attached.
Thanks,
--Doug
Attachments (1)
Change History (2)
by , 16 years ago
comment:1 by , 16 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
VirtualBox until version 2.1.4 supported only about 3GB per guest (even less on 32-Bit machines). Starting with VirtualBox 2.2.0, VirtualBox can maintain up to 16GB of RAM per guest on 64-Bit machines. The limit on 32-Bit machines (~2.5GB on linux hosts, ~1.8GB on Windows hosts) remains and will not be fixed. So you should be able to pass 5GB to the guest if you are using a 64-Bit host kernel (and the 64-bit version of VirtualBox of course).
Vbox.log