VirtualBox

Ticket #3069 (closed enhancement: invalid)

Opened 5 years ago

Last modified 8 months ago

Feature request: support more than 3.584 MB guest RAM (64 bits hosts)

Reported by: pjulien Owned by:
Priority: major Component: host support
Version: VirtualBox 2.1.0 Keywords: memory
Cc: Guest type: other
Host type: Windows

Description (last modified by frank) (diff)

Even when running the 64-bit version of VirtualBox on a 64 bit version of Windows Vista, it's not possible to allocate more than 3GB of memory to the guess operating system.

Change History

comment:1 Changed 5 years ago by frank

  • Summary changed from Guest memory limit on Windows 64 bit host is still 3GB to Guest memory limit is 4GB (even on 64-bit hosts)

comment:2 Changed 5 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to worksforme

Which method are you using for running the VMs? My VirtualBox.exe has the LARGE_ADDRESS_AWARE flag set and I can use up to the max (3.584 MB). Vista 64 host with 16 GB ram.

comment:3 Changed 5 years ago by pjulien

I too, can set the maximum to 3.584MB with a Vista 64 bit host with 32GB of RAM.

However, it's possible for the process to access up to 8TB of virtual address space. Looking at the article that I posted, the testlimit64 tool was able to reserve(not commit) 8TB of virtual memory before running out.

I am trying to find the switch that makes this possible.

comment:4 Changed 5 years ago by pjulien

According to the information I have found, IMAGE_FILE_LARGE_ADDRESS_AWARE is all that is needed on a 64-bit host to have access to an 8TB address space on 64 bit.

So why is virtual box limiting the memory limit of a guest to 3.584MB then?

comment:5 follow-up: ↓ 6 Changed 5 years ago by sandervl73

Because we don't allow more at the moment. That has nothing to do with executable image flags. We will allow for more in the near future.

comment:6 in reply to: ↑ 5 Changed 5 years ago by pjulien

Replying to sandervl73:

Because we don't allow more at the moment. That has nothing to do with executable image flags. We will allow for more in the near future.

OK then, sounds good.

comment:7 Changed 5 years ago by sandervl73

  • Priority changed from minor to major
  • Summary changed from Guest memory limit is 4GB (even on 64-bit hosts) to Feature request: support more than 3.584 MB guest RAM (64 bits hosts)

comment:8 Changed 5 years ago by sandervl73

Note that we'll probably not implement this on 32 bits *hosts*.

comment:9 Changed 5 years ago by sandervl73

  • Description modified (diff)

comment:11 in reply to: ↑ 10 Changed 5 years ago by pjulien

Replying to pjulien:

Replying to sandervl73:

Note that we'll probably not implement this on 32 bits *hosts*.

I wouldn't expect you too, this is a feature request for 64 bit hosts only.

comment:12 Changed 5 years ago by pjulien

However, I have to ask why did you close this "worksforme"? Shouldn't this ticket be left open and turned into a RFE?

comment:13 Changed 5 years ago by sandervl73

  • Status changed from closed to reopened
  • Resolution worksforme deleted

comment:14 Changed 5 years ago by sandervl73

Of course. Forgot :)

comment:15 Changed 5 years ago by sandervl73

  • Type changed from defect to enhancement

comment:16 Changed 5 years ago by bqbauer

2.1.2 says you can now have up to 75% of host memory in new guests. I've tried creating a new 64-bit guest on my 64-bit OpenSolaris host with 8GB memory, and the limit is still 3584. Also tried a larger number using VBoxManage, and it also says the limit is 3584.

comment:17 Changed 5 years ago by ni81036

More than 3.5G RAM limitation for guests not yet lifted - it's hypervisor limitation. Mentioned feature is only UI enhancement.

comment:18 Changed 5 years ago by pakin

I just want to chime in that enabling 64-bit guests to access more than 3584 MB of memory on a 64-bit (Linux) host containing gobs and gobs of memory is highly desirable to me as well. Any chance the hypervisor limitation will go away sometime soon? (I have no idea how much effort is involved in getting the hypervisor to handle large memory spaces.)

comment:19 Changed 5 years ago by frank

  • Status changed from reopened to closed
  • Resolution set to fixed

Fixed with version 2.2.0, make sure to check the latest release 2.2.2. VirtualBox can now maintain up to 16GB on a 64-bit host.

comment:20 Changed 5 years ago by pakin

Thanks, but why is there any limitation other than what the CPU can address? Can't VirtualBox be modified to support an "infinite" amount of guest RAM?

comment:21 Changed 5 years ago by frank

The guest RAM has to be maintained somehow. The larger the amount of guest RAM to maintain, the larger the maintenance structures and the bigger the maintenance overhead. VirtualBox maps all memory of the guest into the VM process. This could be changed but this would induce more overhead and this would require a rewrite of a big part of the VMM. Therefore the limitation for 32-Bit hosts.

comment:22 Changed 5 years ago by pakin

I'm confused by your comment, "Therefore the limitation for 32-Bit hosts", in relation to your prior comment, "VirtualBox can now maintain up to 16GB on a 64-bit host." If I have a 64-bit host with significantly more than 16GB of RAM, then can't VirtualBox let me create a guest with whatever my RAM size is minus the size of the VirtualBox maintenance structures? I don't see why there needs to be an arbitrary limit on guest memory capacity.

comment:23 Changed 5 years ago by frank

Sorry for the confusion, I told you the reason for the 64-bit limit with the first two sentences of my last comment. Only the lines starting with VirtualBox maps all ... were the reason for the 32-bit limit.

comment:24 Changed 20 months ago by sseidel

  • Status changed from closed to reopened
  • Resolution fixed deleted

I cannot assign more than 8GB to my Linux guest on Windows Server 2008 R2. This is a host with 24GB RAM, 64bit, VirtualBox 4.1.20. Has the guest memory limit been reduced in the more recent versions?

comment:25 Changed 20 months ago by frank

  • Description modified (diff)

What do you mean be 'cannot assign more than 8GB' -- what happens if you try to? Does the GUI not allow you to assign more than 8GB or do you experience a Guru Meditation when the guest starts? The latter is another bug which is reported elsewhere.

comment:26 Changed 20 months ago by sseidel

Whenever I assign more than 8GB I can save the settings and start the VM. But the started VM will only receive 8GB and when I re-check the settings page it is reset to 8GB. I also tried setting the RAM size with VBoxManage and by editing the vbox XML file to no avail.

comment:27 Changed 20 months ago by sseidel

Ok it works now. I must shut down the VBoxVmService for the change to work. I had always shut down (powered off) the VM itself, but VBoxVmService leaves VBoxSVC running which seems to prevent any changes to this VM configuration.

comment:28 Changed 20 months ago by frank

Leaving VBoxSVC running should not be a problem but running VirtualBox together with VBoxVmService might be a problem as we don't support the latter.

comment:29 Changed 8 months ago by ag987654321

Just checking in on the latest state of play on Max Ram that can be allocated to Guest (both Guest and Host are running 64b windows) and whether the 16GB limit https://forums.virtualbox.org/viewtopic.php?f=24&t=41211 is still in place?

comment:30 Changed 8 months ago by klaus

  • Status changed from reopened to closed
  • Resolution set to invalid

No, this limit has been raised significantly in VirtualBox 4.1. The officially supported maximum is now 1TB (see changelog of 4.1.0), but this only means that we tested it up to this point because we couldn't quickly get access to a system with more memory. The theoretical maximum is 2TB.

Reading the previous comment makes me think that there was no problem with VirtualBox as such, closing.

Note: See TracTickets for help on using tickets.

www.oracle.com
ContactPrivacy policyTerms of Use