VirtualBox

Ignore:
Timestamp:
May 15, 2023 5:27:56 PM (19 months ago)
Author:
vboxsync
Message:

Docs: bugref:10302. Merging changes from the docs team. Almost exclusively conkeyref related stuff.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/manual/en_US/dita/topics/vdidetails.dita

    r99497 r99797  
    99      Disk image files reside on the host system and are seen by the
    1010      guest systems as hard disks of a certain geometry. When a guest OS
    11       reads from or writes to a hard disk, Oracle VM VirtualBox redirects the
     11      reads from or writes to a hard disk, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> redirects the
    1212      request to the image file.
    1313    </p>
     
    1515      Like a physical disk, a virtual disk has a size, or capacity,
    1616      which must be specified when the image file is created. As opposed
    17       to a physical disk however, Oracle VM VirtualBox enables you to expand
     17      to a physical disk however, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to expand
    1818      an image file after creation, even if it has data already. See
    1919      <xref href="vboxmanage-modifymedium.dita"/>.
    2020    </p>
    2121               <p>
    22       Oracle VM VirtualBox supports the following types of disk image files:
     22      <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports the following types of disk image files:
    2323    </p>
    2424               <ul>
    2525                  <li>
    2626                     <p>
    27                         <b outputclass="bold">VDI.</b> Normally, Oracle VM VirtualBox
     27                        <b outputclass="bold">VDI.</b> Normally, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
    2828          uses its own container format for guest hard disks. This is
    2929          called a Virtual Disk Image (VDI) file. This format is used
     
    3333                  <li>
    3434                     <p>
    35                         <b outputclass="bold">VMDK.</b> Oracle VM VirtualBox also
     35                        <b outputclass="bold">VMDK.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also
    3636          fully supports the popular and open VMDK container format that
    3737          is used by many other virtualization products, such as VMware.
     
    4040                  <li>
    4141                     <p>
    42                         <b outputclass="bold">VHD.</b> Oracle VM VirtualBox also
     42                        <b outputclass="bold">VHD.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> also
    4343          fully supports the VHD format used by Microsoft.
    4444        </p>
     
    8383          drive reaches the maximum capacity chosen when the drive was
    8484          created. While this format takes less space initially, the
    85           fact that Oracle VM VirtualBox needs to expand the image file
     85          fact that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> needs to expand the image file
    8686          consumes additional computing resources, so until the disk
    8787          file size has stabilized, write operations may be slower than
Note: See TracChangeset for help on using the changeset viewer.

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