VirtualBox

source: vbox/trunk/doc/manual/en_US/dita/topics/guestadd-balloon.dita

Last change on this file was 107390, checked in by vboxsync, 8 weeks ago

Docs: bugref:10705. bugref: 10829. The docs build has been modified to split generated refentry dita files and the user manual files and the following commits from doc's team git repo has been applied:

0946136c74dda0483704db891345cb39548b4e28 Started consolidating known issues and troubleshooting information
845b847e6a8e778b38a57867e25ee5e086a73800 Added individual topics for list of known issues, integrated into Troubleshooting section.
bb574836aac775889bd61e4a72f489617fcb7d18 Removed EFI firmware from experimental features for 7.2
6d2e68b244869991e713d170ecd239739d99ba56 Moved known issues into Known Issues section
e2630c896561587718b5c3197c384a38d07014d5 Merge branch 'VBP-1461_experimental-features' into 'main'
0512e2cce51f49ccdc56f3381a2a0c924f2bd278 Feedback on known issues
a77d6c980f6ff5cad9d32b2fb9290990093a03fa Restructured host and guest OS topics
988af5cc9628f5de0806531bc98686f691a911fd Updates with feedbback from Jacob
982a61c9f25b22b745ec483e763e3d88efe59c40 Included feedback from Jacob
93181c8c6cc2d9a26bcccb1145cb0423c0d9f4c9 Updated known issues with feedback from Klaus
8bc369561c383f09b409fe5e44f507440b3735fb Created Legacy Guest OS section
d7932f55accdab7a03666302d58b8c941cd48be2 Moved known issues to more appropriate places for the info
2a4aa094ba8a7ac6894d2a777316eabf41746580 Further moving of known issues
baeabd5308c5519a4dc26b4197be9b00e419a85a Updated links to cli_topics

  • Property svn:eol-style set to native
  • Property svn:keywords set to Author Date Id Revision
File size: 3.9 KB
Line 
1<?xml version='1.0' encoding='UTF-8'?>
2<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
3<topic xml:lang="en-us" id="guestadd-balloon">
4 <title>Memory Ballooning</title>
5
6 <body>
7 <p>
8 The Guest Additions can change the amount of host memory that a
9 VM uses, while the machine is running. Because of how this is
10 implemented, this feature is called <i>memory
11 ballooning</i>.
12 </p>
13 <note>
14 <ul>
15 <li>
16 <p>
17 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports memory ballooning only on 64-bit
18 hosts. It is not supported on macOS hosts.
19 </p>
20 </li>
21 <li>
22 <p>
23 Memory ballooning does not work well with large pages
24 enabled. To turn off large pages support for a VM, run
25 <userinput>VBoxManage modifyvm <varname>vmname</varname> --large-pages
26 off</userinput>
27 </p>
28 </li>
29 </ul>
30 </note>
31 <p>
32 Normally, to change the amount of memory allocated to a virtual
33 machine, you have to shut down the virtual machine entirely and
34 modify its settings. With memory ballooning, memory that was
35 allocated for a virtual machine can be given to another virtual
36 machine without having to shut the machine down.
37 </p>
38 <p>
39 When memory ballooning is requested, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> Guest
40 Additions, which run inside the guest, allocate physical memory
41 from the guest operating system on the kernel level and lock
42 this memory down in the guest. This ensures that the guest will
43 not use that memory any longer. No guest applications can
44 allocate it, and the guest kernel will not use it either.
45 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can then reuse this memory and give it to another
46 virtual machine.
47 </p>
48 <p>
49 The memory made available through the ballooning mechanism is
50 only available for reuse by <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. It is
51 <i>not</i> returned as free memory to the host.
52 Requesting balloon memory from a running guest will therefore
53 not increase the amount of free, unallocated memory on the host.
54 Effectively, memory ballooning is therefore a memory
55 overcommitment mechanism for multiple virtual machines while
56 they are running. This can be useful to temporarily start
57 another machine, or in more complicated environments, for
58 sophisticated memory management of many virtual machines that
59 may be running in parallel depending on how memory is used by
60 the guests.
61 </p>
62 <p>
63 At this time, memory ballooning is only supported through
64 <userinput>VBoxManage</userinput>. Use the following command to
65 increase or decrease the size of the memory balloon within a
66 running virtual machine that has Guest Additions installed:
67 </p>
68 <pre xml:space="preserve">VBoxManage controlvm "VM name" guestmemoryballoon n</pre>
69 <p> where <varname>VM name</varname> is the name or UUID of the virtual machine in question and <varname>n</varname> is the amount of memory to allocate from the guest in megabytes. See <xref href="../cli_topics/vboxmanage-controlvm.dita"/>.</p>
70 <p>
71 You can also set a default balloon that will automatically be
72 requested from the VM every time after it has started up with
73 the following command:
74 </p>
75 <pre xml:space="preserve">VBoxManage modifyvm "VM name" --guest-memory-balloon n</pre>
76 <p> By default, no balloon memory is allocated. This is a VM setting, like other <userinput>modifyvm</userinput> settings, and therefore can only be set while the machine is shut down. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>. </p>
77 </body>
78
79</topic>
Note: See TracBrowser for help on using the repository browser.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette