Changeset 35142 in vbox for trunk/doc/manual/en_US
- Timestamp:
- Dec 15, 2010 4:02:58 PM (14 years ago)
- Location:
- trunk/doc/manual/en_US
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_Storage.xml
r34841 r35142 251 251 the image file.</para> 252 252 253 <para>Note that when you create an image file, its size needs to be 254 specified, which represents a fixed geometry of the virtual disk. It is 255 therefore not possible to change the size of the virtual hard disk 256 later.</para> 253 <para>Like a physical disk, a virtual disk has a size (capacity), which 254 must be specified when the image file is created. As opposed to a physical 255 disk however, VirtualBox allows you to expand an image file after 256 creation, even if it has data already; see <xref 257 linkend="vboxmanage-modifyvdi" /> for details.<footnote> 258 <para>Image resizing was added with VirtualBox 4.0.</para> 259 </footnote></para> 257 260 258 261 <para>VirtualBox supports four variants of disk image files:<itemizedlist> … … 290 293 </itemizedlist></para> 291 294 292 <para>Irrespective of the disk format, as briefly mentioned in <xref293 linkend="gui-createvm" />, there are two options of how to create a disk294 image: fixed-size or dynamically expanding.</para>295 <para>Irrespective of the disk capacity and format, as briefly mentioned 296 in <xref linkend="gui-createvm" />, there are two options of how to create 297 a disk image: fixed-size or dynamically expanding.</para> 295 298 296 299 <itemizedlist> 297 300 <listitem> 298 301 <para>If you create a <emphasis role="bold">fixed-size 299 image</emphasis> of e.g. 10 GB, an image file of roughly the same size 300 will be created on your host system. Note that the creation of a 302 image</emphasis>, an image file will be created on your host system 303 which has roughly the same size as the virtual disk's capacity. So, 304 for a 10G disk, you will have a 10G file. Note that the creation of a 301 305 fixed-size image can take a long time depending on the size of the 302 306 image and the write performance of your hard disk.</para> … … 477 481 478 482 <listitem> 479 <para> Finally, <emphasis role="bold">immutable images</emphasis> only483 <para>Next, <emphasis role="bold">immutable images</emphasis> only 480 484 remember write accesses temporarily while the virtual machine is 481 485 running; all changes are lost when the virtual machine is powered on … … 528 532 linkend="vboxmanage-modifyvdi" /> for details.</para> 529 533 </listitem> 534 535 <listitem> 536 <para>An image in <emphasis role="bold">multiattach mode</emphasis> 537 can be attached to more than one virtual machine at the same time, 538 even if these machines are running simultaneously. For each virtual 539 machine to which such an image is attached, a differencing image is 540 created. As a result, data that is written to such a virtual disk by 541 one machine is not seen by the other machines to which the image is 542 attached; each machine creates its own write history of the 543 multiattach image.</para> 544 545 <para>Technically, a "multiattach" image behaves identically to an 546 "immutable" image except the differencing image is not reset every 547 time the machine starts. </para> 548 </listitem> 549 550 <listitem> 551 <para>Finally, a <emphasis role="bold">read-only image</emphasis> is 552 one that cannot be written to at all. This can only be used for DVD 553 and floppy images: for DVD images, this mode is automatically used and 554 cannot be changed, whereas the mode can be manually set for a floppy 555 image to simulate a floppy which is write-protected. It is an error to 556 enable read-only mode for a hard disk.</para> 557 </listitem> 530 558 </orderedlist> 531 559 -
trunk/doc/manual/en_US/user_VBoxManage.xml
r35090 r35142 1907 1907 1908 1908 <para>With the <computeroutput>modifyhd</computeroutput> command, you can 1909 change the type of an existing image between the normal, immutable and 1910 write-through modes; see <xref linkend="hdimagewrites" /> for 1911 details.<note> 1912 <para>For compatibility with earlier versions of VirtualBox, the 1913 "modifyvdi" command is also supported and mapped internally to the 1914 "modifyhd" command.</para> 1909 change the characteristics of a disk image after it has been 1910 created:<screen>VBoxManage modifyhd <uuid>|<filename> 1911 [--type normal|writethrough|immutable|shareable| 1912 readonly|multiattach] 1913 [--autoreset on|off] 1914 [--compact] 1915 [--resize <megabytes>|--resizebyte <bytes>]</screen><note> 1916 <para>Despite the "hd" in the subcommand name, the command works with 1917 all disk images, not only hard disks. For compatibility with earlier 1918 versions of VirtualBox, the "modifyvdi" command is also supported and 1919 mapped internally to the "modifyhd" command.</para> 1915 1920 </note></para> 1916 1921 1917 <para>For immutable (differencing) hard disks only, the 1918 <computeroutput>modifyhd autoreset on|off</computeroutput> command 1919 determines whether the disk is automatically reset on every VM startup 1920 (again, see <xref linkend="hdimagewrites" />). The default is "on".</para> 1921 1922 <para>In addition, the <computeroutput>modifyhd --compact</computeroutput> 1923 command can be used to compact disk images, i.e. remove blocks that only 1924 contains zeroes. For this operation to be effective, it is required to 1925 zero out free space in the guest system using a suitable software tool. 1926 Microsoft provides the <computeroutput>sdelete</computeroutput> tool for 1927 Windows guests. Execute <computeroutput>sdelete -c</computeroutput> in the 1928 guest to zero the free disk space before compressing the virtual disk 1929 image. Compaction works both for base images and for diff images created 1930 as part of a snapshot.</para> 1922 <para>The following options are available:<itemizedlist> 1923 <listitem> 1924 <para>With the <computeroutput>--type</computeroutput> argument, you 1925 can change the type of an existing image between the normal, 1926 immutable, write-through and other modes; see <xref 1927 linkend="hdimagewrites" /> for details.</para> 1928 </listitem> 1929 1930 <listitem> 1931 <para>For immutable (differencing) hard disks only, the 1932 <computeroutput>--autoreset on|off</computeroutput> option 1933 determines whether the disk is automatically reset on every VM 1934 startup (again, see <xref linkend="hdimagewrites" />). The default 1935 is "on".</para> 1936 </listitem> 1937 1938 <listitem> 1939 <para>With the <computeroutput>--compact</computeroutput> option, 1940 can be used to compact disk images, i.e. remove blocks that only 1941 contains zeroes. This will shrink a dynamically expanding image 1942 again; it will reduce the <emphasis>physical</emphasis> size of the 1943 image without affecting the logical size of the virtual disk. 1944 Compaction works both for base images and for diff images created as 1945 part of a snapshot.</para> 1946 1947 <para>For this operation to be effective, it is required that free 1948 space in the guest system first be zeroed out using a suitable 1949 software tool. For Windows guests, you can use the 1950 <computeroutput>sdelete</computeroutput> tool provided by Microsoft. 1951 Execute <computeroutput>sdelete -c</computeroutput> in the guest to 1952 zero the free disk space before compressing the virtual disk image. 1953 </para> 1954 </listitem> 1955 1956 <listitem> 1957 <para>The --resize option allows you to expand the capacity of an 1958 existing image; this increases the <emphasis>logical</emphasis> size 1959 of a virtual disk without affecting the physical size much.<footnote> 1960 <para>Image resizing was added with VirtualBox 4.0.</para> 1961 </footnote> This currently works only for the VDI and VHD formats, 1962 and only for the dynamically expanding variants. For example, if you 1963 originally created a 10G disk which is now full, you can use the 1964 --resize command to add more space to the virtual disk without 1965 having to create a new image and copy all data from within a virtual 1966 machine.</para> 1967 </listitem> 1968 </itemizedlist></para> 1931 1969 </sect1> 1932 1970 … … 2937 2975 <listitem> 2938 2976 <para>To add a new extension pack, use <computeroutput>VBoxManage 2939 extpack install <tarball></computeroutput>. 2977 extpack install <tarball></computeroutput>.</para> 2940 2978 </listitem> 2941 2979
Note:
See TracChangeset
for help on using the changeset viewer.