Changeset 105289 in vbox for trunk/doc/manual/en_US/dita/topics/features-overview.dita
- Timestamp:
- Jul 12, 2024 9:07:43 AM (6 months ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/dita/topics/features-overview.dita
r105134 r105289 15 15 <xref href="hostossupport.dita#hostossupport"/>. 16 16 </p> 17 <p> 18 <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a so-called <i>hosted</i> 19 hypervisor, sometimes referred to as a <i>type 20 2</i> hypervisor. Whereas a 21 <i>bare-metal</i> or <i>type 1</i> 22 hypervisor runs directly on the hardware, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 23 requires an existing OS to be installed. It can thus run 24 alongside existing applications on that host. 25 </p> 26 <p> 27 To a very large degree, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is functionally 28 identical on all of the host platforms, and the same file and 29 image formats are used. This enables you to run virtual 30 machines created on one host on another host with a different 31 host OS. For example, you can create a virtual machine on 32 Windows and then run it on Linux. 33 </p> 34 <p> 35 In addition, virtual machines can easily be imported and 36 exported using the Open Virtualization Format (OVF), an 37 industry standard created for this purpose. You can even 38 import OVFs that were created with a different virtualization 39 software. See <xref href="ovf.dita#ovf"/>. 40 </p> 41 <p> 42 For users of <ph conkeyref="vbox-conkeyref-phrases/oci"/> the functionality extends to exporting and 43 importing virtual machines to and from the cloud. This 44 simplifies development of applications and deployment to the 45 production environment. See 46 <xref href="cloud-export-oci.dita#cloud-export-oci"/>. 47 </p> 17 <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> is a so-called <i>hosted</i> hypervisor, sometimes 18 referred to as a <i>type 2</i> hypervisor. Whereas a <i>bare-metal</i> or <i>type 1</i> hypervisor runs 19 directly on the hardware, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> requires an existing OS to be 20 installed. It can thus run alongside existing applications on that host. </p> 21 <p>To a very large degree, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> is functionally identical on 22 all of the host platforms, and the same file and image formats are used. This enables you to run virtual 23 machines created on one host on another host with a different host OS. For example, you can create a virtual 24 machine on Windows and then run it on Linux. </p> 25 <p>In addition, virtual machines can easily be imported and exported using the Open Virtualization Format (OVF), 26 an industry standard created for this purpose. You can even import OVFs that were created with a different 27 virtualization software. See <xref href="ovf.dita#ovf"/>. </p> 28 <p>For users of <ph conkeyref="vbox-conkeyref-phrases/oci"/> the functionality extends to exporting and 29 importing virtual machines to and from the cloud. This simplifies development of applications and deployment 30 to the production environment. See <xref href="cloud-export-oci.dita#cloud-export-oci"/>. </p> 48 31 </li> 49 32 <li> … … 59 42 <xref href="guestadditions.dita#guestadditions"/>. 60 43 </p> 61 <p> 62 In particular, Guest Additions provide for <i>shared 63 folders</i>, which let you access files on the host 64 system from within a guest machine. See 65 <xref href="sharedfolders.dita#sharedfolders"/>. 66 </p> 44 <p>In particular, Guest Additions provide for <i>shared folders</i>, which let you access files on the host 45 system from within a guest machine. See <xref href="sharedfolders.dita#sharedfolders"/>. </p> 67 46 </li> 68 47 <li> … … 175 154 <xref href="frontends.dita#frontends"/>. 176 155 </p> 177 <p> 178 Due to its modular architecture, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can also 179 expose its full functionality and configurability through a 180 comprehensive <b outputclass="bold">software development kit 181 (SDK),</b> which enables integration of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> 182 with other software systems. See 183 <xref href="VirtualBoxAPI.dita"><ph conkeyref="vbox-conkeyref-phrases/product-name"/> Programming Interfaces</xref>. 184 </p> 156 <p>Due to its modular architecture, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can also expose its 157 full functionality and configurability through a comprehensive <b outputclass="bold">software development kit 158 (SDK),</b> which enables integration of <ph conkeyref="vbox-conkeyref-phrases/product-name"/> with other 159 software systems. See <xref href="VirtualBoxAPI.dita"><ph conkeyref="vbox-conkeyref-phrases/product-name"/> 160 Programming Interfaces</xref>. </p> 185 161 </li> 186 162 <li> … … 192 168 additions for full client USB support. 193 169 </p> 194 <p> 195 The VRDE does not rely on the RDP server that is built into 196 Microsoft Windows. Instead, the VRDE is plugged directly into 197 the virtualization layer. As a result, it works with guest 198 OSes other than Windows, even in text mode, and does not 199 require application support in the virtual machine either. The 200 VRDE is described in detail in <xref href="vrde.dita">Remote Display (VRDP Support)</xref>. 201 </p> 202 <p> 203 On top of this special capacity, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> offers you 204 more unique features: 205 </p> 170 <p>The VRDE does not rely on the RDP server that is built into Microsoft Windows. Instead, the VRDE is plugged 171 directly into the virtualization layer. As a result, it works with guest OSes other than Windows, even in text 172 mode, and does not require application support in the virtual machine either. The VRDE is described in detail 173 in <xref href="vrde.dita">Remote Display (VRDP Support)</xref>. </p> 174 <p>On top of this special capacity, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> offers you more unique 175 features: </p> 206 176 <ul> 207 177 <li>
Note:
See TracChangeset
for help on using the changeset viewer.
