Changeset 37837 in vbox

Timestamp:

Jul 8, 2011 11:21:46 AM (14 years ago)

Author:

vboxsync

Message:

doc/manual: 'dynamically expanding image' => 'dynamically expanded image'

Location:

trunk/doc/manual/en_US

Files:

• user_AdvancedTopics.xml (modified) (2 diffs)
• user_Introduction.xml (modified) (2 diffs)
• user_Storage.xml (modified) (4 diffs)
• user_VBoxManage.xml (modified) (3 diffs)

trunk/doc/manual/en_US/user_AdvancedTopics.xml

@@ -1547 +1547 @@
           <computeroutput>true</computeroutput> to
           <computeroutput>false</computeroutput>. To manually start the
-          service use the following command: <screen>launchctl load ~/Library/LaunchAgents/org.virtualbox.vboxwebsrv.plist</screen>
+          service use the following command:
+          <screen>launchctl load ~/Library/LaunchAgents/org.virtualbox.vboxwebsrv.plist</screen>
           For additional information on how launchd services could be
           configured see <literal><ulink
@@ -1558 +1559 @@
     <title>Memory Ballooning Service</title>
 
-    <para>Starting with VirtualBox 4.0.8 a new host executable called <computeroutput>VBoxBalloonCtrl</computeroutput> is
-    available to automatically take care of a VM's configured memory balloon (see <xref linkend="guestadd-balloon" />
-    for an introduction to memory ballooning). This is especially useful for server environments where VMs may dynamically
-    require more or less memory during runtime.</para>
-
-    <para>VBoxBalloonCtrl periodically checks a VM's current memory balloon and its free guest RAM and automatically adjusts
-    the current memory balloon by inflating or deflating it accordingly. This handling only applies to running VMs having recent
-    Guest Additions installed.</para>
-
-    <para>To set up VBoxBalloonCtrl and adjust the maximum ballooning size a VM can reach the following parameters will be checked in the following
-    order:
+    <para>Starting with VirtualBox 4.0.8 a new host executable called
+      <computeroutput>VBoxBalloonCtrl</computeroutput> is available to
+      automatically take care of a VM's configured memory balloon
+      (see <xref linkend="guestadd-balloon" /> for an introduction to memory
+      ballooning). This is especially useful for server environments where
+      VMs may dynamically require more or less memory during runtime.</para>
+
+    <para>VBoxBalloonCtrl periodically checks a VM's current memory balloon
+      and its free guest RAM and automatically adjusts the current memory
+      balloon by inflating or deflating it accordingly. This handling only
+      applies to running VMs having recent Guest Additions installed.</para>
+
+    <para>To set up VBoxBalloonCtrl and adjust the maximum ballooning size a
+      VM can reach the following parameters will be checked in the following
+      order:
       <itemizedlist>
-        <listitem>specified via VBoxBalloonCtrl command line parameter <computeroutput>--balloon-max</computeroutput></listitem>
-        <listitem>per-VM parameter using <screen>VBoxManage setextradata "VM-Name" VBoxInternal/Guest/BalloonSizeMax &lt;Size in MB&gt;</screen></listitem>
-        <listitem>global parameter for all VMs using <screen>VBoxManage setextradata global VBoxInternal/Guest/BalloonSizeMax &lt;Size in MB&gt;</screen></listitem>
+        <listitem>specified via VBoxBalloonCtrl command line parameter 
+          <computeroutput>--balloon-max</computeroutput></listitem>
+        <listitem>per-VM parameter using
+          <screen>VBoxManage setextradata "VM-Name" VBoxInternal/Guest/BalloonSizeMax &lt;Size in MB&gt;</screen></listitem>
+        <listitem>global parameter for all VMs using
+          <screen>VBoxManage setextradata global VBoxInternal/Guest/BalloonSizeMax &lt;Size in MB&gt;</screen></listitem>
       </itemizedlist>
       <note>
-        <para>If no maximum ballooning size is specified by at least one of the parameters above, no ballooning will be performed at all.</para>
+        <para>If no maximum ballooning size is specified by at least one of the
+          parameters above, no ballooning will be performed at all.</para>
       </note>
     </para>
 
-    <para>For more options and parameters check the built-in command line help accessible with <computeroutput>--help</computeroutput>.</para>
+    <para>For more options and parameters check the built-in command line help
+      accessible with <computeroutput>--help</computeroutput>.</para>
   </sect1>
 </chapter>

trunk/doc/manual/en_US/user_Introduction.xml

@@ -748 +748 @@
           <para>VirtualBox supports two types of image files:<itemizedlist>
               <listitem>
-                <para>A <emphasis role="bold">dynamically expanding
+                <para>A <emphasis role="bold">dynamically allocated
                 file</emphasis> will only grow in size when the guest actually
                 stores data on its virtual hard disk. It will therefore
@@ -761 +761 @@
                 occupying much more space, a fixed-size file incurs less
                 overhead and is therefore slightly faster than a dynamically
-                expanding file.</para>
+                allocated file.</para>
               </listitem>
             </itemizedlist></para>

trunk/doc/manual/en_US/user_Storage.xml

@@ -295 +295 @@
     <para>Irrespective of the disk capacity and format, as briefly mentioned
     in <xref linkend="gui-createvm" />, there are two options of how to create
-    a disk image: fixed-size or dynamically expanding.</para>
+    a disk image: fixed-size or dynamically allocated.</para>
 
     <itemizedlist>
@@ -309 +309 @@
       <listitem>
         <para>For more flexible storage management, use a <emphasis
-        role="bold">dynamically expanding image</emphasis>. This will
+        role="bold">dynamically allocated image</emphasis>. This will
         initially be very small and not occupy any space for unused virtual
-        disk sectors, but the image file will grow every time a disk sector is
-        written to for the first time. While this format takes less space
-        initially, the fact that VirtualBox needs to constantly expand the
-        image file consumes additional computing resources, so until the disk
-        has fully expanded, write operations are slower than with fixed size
-        disks. However, after a dynamic disk has fully expanded, the
-        performance penalty for read and write operations is
-        negligible.</para>
+        disk sectors, but will grow every time a disk sector is written to for
+        the first time, until the drive reaches the maximum capacity chosen
+        when the drive was created. While this format takes less space
+        initially, the fact that VirtualBox needs to expand the image file
+        consumes additional computing resources, so until the disk file size has
+        stabilized, write operations may be slower than with fixed size disks.
+        However, after a time the rate of growth will slow and the average penalty
+        for write operations will be negligible.</para>
       </listitem>
     </itemizedlist>
@@ -416 +416 @@
     virtual machine and snapshot operations. This applies to all of the
     aforementioned image formats (VDI, VMDK, VHD or HDD) and irrespective of
-    whether an image is fixed-size or dynamically expanding.</para>
+    whether an image is fixed-size or dynamically allocated.</para>
 
     <para>By default, images are in "normal" mode. To mark an existing image
@@ -473 +473 @@
         between VMs and similar applications which are explicitly prepared to
         access a disk concurrently. Only fixed size images can be used in this
-        way, and dynamically growing images are rejected.<warning>
+        way, and dynamically allocated images are rejected.<warning>
             <para>This is an expert feature, and misuse can lead to data loss
             -- regular filesystems are not prepared to handle simultaneous

trunk/doc/manual/en_US/user_VBoxManage.xml

@@ -2046 +2046 @@
           <para>With the <computeroutput>--compact</computeroutput> option,
           can be used to compact disk images, i.e. remove blocks that only
-          contains zeroes. This will shrink a dynamically expanding image
+          contains zeroes. This will shrink a dynamically allocated image
           again; it will reduce the <emphasis>physical</emphasis> size of the
           image without affecting the logical size of the virtual disk.
@@ -2063 +2063 @@
           <para>Please note that compacting is currently only available for
           VDI images. A similar effect can be achieved by zeroing out free
-          blocks and then cloning the disk to any other dynamically expanding
+          blocks and then cloning the disk to any other dynamically allocated
           format. You can use this workaround until compacting is also
           supported for disk formats other than VDI.</para>
@@ -2075 +2075 @@
               <para>Image resizing was added with VirtualBox 4.0.</para>
             </footnote> This currently works only for expanding the capacity of
-          VDI and VHD formats, and only for the dynamically expanding variants.
+          VDI and VHD formats, and only for the dynamically allocated variants.
           For example, if you originally created a 10G disk which is now full,
           you can use the <computeroutput>--resize 15360</computeroutput>