VirtualBox

Changeset 108750 in vbox


Ignore:
Timestamp:
Mar 26, 2025 9:46:02 AM (3 weeks ago)
Author:
vboxsync
svn:sync-xref-src-repo-rev:
168175
Message:

Docs: bugref:10705. The following commits from doc's team git repo has been applied:

113d19fbbcf63a7e5a7dc1870e5446a03e9687ff updated for clarity
7c100f906d5f7f6dba276fce9a20a58d8ec32a0a Vbp 1463 exp features
134915fb1e15f269acf050c5d1085589e09b645d Removed disk options no longer in GUI

Location:
trunk/doc/manual/en_US/dita
Files:
3 added
2 deleted
18 edited

Legend:

Unmodified
Added
Removed

  • trunk/doc/manual/en_US/dita/UserManual.ditamap

    r108599 r108750  
    103103    <topicref href="topics/create-vm-unattended-install.dita"/>
    104104    <topicref href="topics/create-vm-hardware.dita"/>
    105     <topicref href="topics/create-vm-virtual-hard-disk.dita"/>
    106105            <topicref href="topics/unattended-guest-install-example.dita"/>
    107106  </chapter>
    … …  
    359358         </topicref>
    360359         <topicref href="topics/changevpd.dita"/>
    361          <topicref href="topics/iscsi-intnet.dita"/>
    362360      </topicref>
    363361      <topicref href="topics/changenat.dita">
    … …  
    440438         </topicref>
    441439      </topicref>
    442       <topicref href="topics/pcspeaker_passthrough.dita"/>
    443440      <topicref href="topics/usbip.dita">
    444441         <topicref href="topics/usbip-setup-server.dita"/>
    … …  
    447444      <topicref href="topics/hyperv-support.dita"/>
    448445      <topicref href="topics/nested-virt.dita"/>
    449       <topicref href="topics/vboxsvc-session-0.dita">
    450          <topicref href="topics/vboxsvc-session-0-known-issues.dita"/>
    451       </topicref>
     446    <topicref href="topics/vboxsvc-session-0.dita"/>
    452447      <topicref format="ditamap" href="cli_topics/user_isomakercmd-man.ditamap"/>
    453448   </chapter>
    … …  
    494489        <topicref href="topics/ts_scale-mode.dita"/>
    495490        <topicref href="topics/guestadd-dnd-limitations.dita"/>
     491        <topicref href="topics/ts_ich9.dita"/>
    496492      </topicref>
    497493      <topicref href="topics/ts_win-guests.dita">
    … …  
    512508      <topicref href="topics/ts_win-hosts.dita">
    513509         <topicref href="topics/ts_win-host-cd-dvd-changes.dita"/>
     510        <topicref href="topics/vboxsvc-session-0-known-issues.dita"/>
    514511         <topicref href="topics/ts_win-host-rdp-client.dita"/>
    515512         <topicref href="topics/ts_win-host-iscsi.dita"/>
    … …  
    635632    <topicref href="topics/ExperimentalFeatures.dita">
    636633      <topicref href="topics/macosxguests.dita"/>
    637     </topicref>
    638     <topicref href="topics/hwvirt.dita">
    639       <topicref href="topics/hwvirt-details.dita"/>
     634      <topicref href="topics/cd-passthrough.dita"/>
     635      <topicref href="topics/pcspeaker_passthrough.dita"/>
     636      <topicref href="topics/virtio-scsi.dita"/>
     637      <topicref href="topics/iscsi-intnet.dita"/>
    640638    </topicref>
    641639    <topicref href="topics/privacy.dita"/>

  • trunk/doc/manual/en_US/dita/topics/ExperimentalFeatures.dita

    r107390 r108750  
    55 
    66  <body>
    7     <p> Some <ph conkeyref="vbox-conkeyref-phrases/product-name"/> features are labeled as experimental. Such features are provided on an "as-is" basis and are not formally supported. However, feedback and suggestions about such features are welcome. A comprehensive list of experimental features is as follows: </p>
     7    <p>These <ph conkeyref="vbox-conkeyref-phrases/product-name"/> features are considered experimental and are not formally supported. However, feedback and suggestions about the features are welcome.</p>
    88    <ul>
     9      <li><xref href="macosxguests.dita"/><p><xref href="cd-passthrough.dita"/></p></li>
     10      <li><xref href="pcspeaker_passthrough.dita"/></li>
    911      <li>
    10         <p>
    11           Hardware 3D acceleration support for Windows, Linux, and
    12           Oracle Solaris guests
    13         </p>
     12        <p><xref href="virtio-scsi.dita"/></p>
    1413      </li>
    1514      <li>
    16         <p>
    17           Mac OS X guests (macOS hosts only)
    18         </p>
    19       </li>
    20       <li>
    21         <p>
    22           ICH9 chipset emulation
    23         </p>
    24       </li>
    25       <li>
    26         <p>
    27           Host CD/DVD drive passthrough
    28         </p>
    29       </li>
    30       <li>
    31         <p>
    32           Support of iSCSI using internal networking
    33         </p>
    34       </li>
    35       <li>
    36         <p> Using <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and Hyper-V on the same host </p>
     15        <p><xref href="iscsi-intnet.dita"/></p>
    3716      </li>
    3817    </ul>

  • trunk/doc/manual/en_US/dita/topics/cloud-using-cloud-networks.dita

    r108599 r108750  
    2828      <li>
    2929        <p>Register the new cloud network with <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. </p>
    30         <p>Use the <b outputclass="bold">Cloud Networks</b> tab in the <b outputclass="bold">Network Manager</b> tool.
    31           See <xref href="edit-network.dita#network-manager-cloud-network-tab"/>. </p>
     30        <p>Use the <uicontrol>Network</uicontrol> tool. See <xref href="config-network.dita"/>.</p>
    3231      </li>
    3332      <li>
    34         <p>Add cloud network adaptors to the local VMs that will use the cloud network. See <xref
    35             href="network_cloud.dita#network_cloud"/>. </p>
     33        <p>Add cloud network adaptors to the local VMs that will use the cloud network. See <xref href="network_cloud.dita#network_cloud"/>.</p>
    3634      </li>
    3735    </ol>

  • trunk/doc/manual/en_US/dita/topics/create-vm-hardware.dita

    r108599 r108750  
    55  <body>
    66    <ol id="ol_ndb_dbx_4bc">
    7       <li>Based on the OS you have chosen, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> suggests a suitable default size for <uicontrol>Base Memory</uicontrol>. This is the amount of RAM that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> should allocate to the virtual machine (VM) every time it is started. The guest OS will report this size as the VM's installed RAM. <note type="caution" id="note_pjs_x1x_4bc">
     7      <li>
     8        <p>Based on the OS you have chosen, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> suggests a suitable default size for <uicontrol>Base Memory</uicontrol>. This is the amount of RAM that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> should allocate to the virtual machine (VM) every time it is started. The guest OS will report this size as the VM's installed RAM. </p>
     9        <note type="caution" id="note_pjs_x1x_4bc">
    810          <p>Choose this setting carefully. The memory you give to the VM will not be available to your host OS while the VM is running.</p>
    9         </note><p>Do not specify more than you can spare, whilst ensuring you allocate enough for your guest OS and applications to run properly. For example, if your host machine has 4 GB of RAM and you enter 2048 MB as the base memory for a VM, you will have 2 GB left for all the other software on your host while that VM is running.</p><p>A guest OS may require at least 1 or 2 GB of memory to install and boot up. If you intend to run more than one VM at a time, plan accordingly. A VM will not start if it does not have enough RAM to boot.</p><p>Always ensure that the host OS has enough RAM remaining. If insufficient RAM remains, the system might excessively swap memory to the hard disk, which will effectively bring the host system to a standstill. </p></li>
    10       <li>For <uicontrol>Processors</uicontrol>, select the number of virtual processors to assign to the VM. Do not assign more than half of the total processor threads from the host machine.</li>
    11       <li>Select <uicontrol>Use EFI</uicontrol> to boot the guest OS using Extended Firmware Interface (EFI).</li>
     11        </note>
     12        <p>Do not specify more than you can spare, whilst ensuring you allocate enough for your guest OS and applications to run properly. For example, if your host machine has 4 GB of RAM and you enter 2048 MB as the base memory for a VM, you will have 2 GB left for all the other software on your host while that VM is running.</p>
     13        <p>A guest OS may require at least 1 or 2 GB of memory to install and boot up. If you intend to run more than one VM at a time, plan accordingly. A VM will not start if it does not have enough RAM to boot.</p>
     14        <p>Always ensure that the host OS has enough RAM remaining. If insufficient RAM remains, the system might excessively swap memory to the hard disk, which will effectively bring the host system to a standstill.</p>
     15      </li>
     16      <li>
     17        <p>For <uicontrol>Processors</uicontrol>, select the number of virtual processors to assign to the VM. Do not assign more than half of the total processor threads from the host machine.</p>
     18      </li>
     19      <li><p>Choose the <uicontrol>Disk Size</uicontrol> for a new, dynamically allocated, virtual hard disk image to be created in the VM folder.</p> For other options when allocating virtual storage, see <xref href="storage.dita"/>.</li>
     20      <li>
     21        <p>Select <uicontrol>Use EFI</uicontrol> to boot the guest OS using Extended Firmware Interface (EFI).</p>
     22      </li>
    1223    </ol>
    1324  </body>

  • trunk/doc/manual/en_US/dita/topics/harddiskcontrollers.dita

    r107390 r108750  
    55 
    66  <body>
    7     <p>In a computing device, hard disks and CD/DVD drives are connected to a device called a hard disk controller,
    8       which drives hard disk operation and data transfers. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can
    9       emulate the most common types of hard disk controllers typically found in computing devices: IDE, SATA (AHCI),
    10       SCSI, SAS, USB-based, NVMe and virtio-scsi mass storage devices. </p>
     7    <p>In a computing device, hard disks and CD/DVD drives are connected to a device called a hard disk controller, which drives hard disk operation and data transfers. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can emulate the most common types of hard disk controllers typically found in computing devices: IDE, SATA (AHCI), SCSI, SAS, USB-based, and NVMe mass storage devices.</p>
    118    <ul>
    129      <li>
    13         <p><b outputclass="bold">IDE (ATA)</b> controllers are a backward-compatible yet very
    14           advanced extension of the disk controller in the IBM PC/AT (1984). Initially, this
    15           interface worked only with hard disks, but was later extended to also support CD-ROM
    16           drives and other types of removable media. In physical PCs, this standard uses flat ribbon
    17           parallel cables with 40 or 80 wires. Each such cable can connect two devices, called
    18           device 0 and device 1, to a controller. Typical PCs had two connectors for such cables. As
    19           a result, support for up to four IDE devices was most common: primary device 0, primary
    20           device 1, secondary device 0, and secondary device 1. </p>
    21         <p>In <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, each virtual machine may have one IDE controller
    22           enabled, which gives you up to four virtual storage devices that you can attach to the machine. By default,
    23           one of these virtual storage devices, device 0 on the secondary channel, is preconfigured to be the virtual
    24           machine's virtual CD/DVD drive. However, you can change the default setting. </p>
    25         <p>Even if your guest OS has no support for SCSI or SATA devices, it should always be able to see an IDE
    26           controller. </p>
    27         <p>You can also select which exact type of IDE controller hardware <ph
    28             conkeyref="vbox-conkeyref-phrases/product-name"/> should present to the virtual machine: PIIX3, PIIX4, or
    29           ICH6. This makes no difference in terms of performance, but if you import a virtual machine from another
    30           virtualization product, the OS in that machine may expect a particular controller type and crash if it is not
    31           found. </p>
    32         <p>After you have created a new virtual machine with the <b outputclass="bold">New Virtual Machine</b> wizard in
    33             <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, you will typically see one IDE controller in the
    34           machine's <b outputclass="bold">Storage</b> settings. The virtual CD/DVD drive will be attached to one of the
    35           four ports of this controller. </p>
     10        <p><b outputclass="bold">IDE (ATA)</b> controllers are a backward-compatible yet very advanced extension of the disk controller in the IBM PC/AT (1984). Initially, this interface worked only with hard disks, but was later extended to also support CD-ROM drives and other types of removable media. In physical PCs, this standard uses flat ribbon parallel cables with 40 or 80 wires. Each such cable can connect two devices, called device 0 and device 1, to a controller. Typical PCs had two connectors for such cables. As a result, support for up to four IDE devices was most common: primary device 0, primary device 1, secondary device 0, and secondary device 1.</p>
     11        <p>In <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, each virtual machine may have one IDE controller enabled, which gives you up to four virtual storage devices that you can attach to the machine. By default, one of these virtual storage devices, device 0 on the secondary channel, is preconfigured to be the virtual machine's virtual CD/DVD drive. However, you can change the default setting.</p>
     12        <p>Even if your guest OS has no support for SCSI or SATA devices, it should always be able to see an IDE controller.</p>
     13        <p>You can also select which exact type of IDE controller hardware <ph conkeyref="vbox-conkeyref-phrases/product-name"/> should present to the virtual machine: PIIX3, PIIX4, or ICH6. This makes no difference in terms of performance, but if you import a virtual machine from another virtualization product, the OS in that machine may expect a particular controller type and crash if it is not found.</p>
     14        <p>After you have created a new virtual machine with the <b outputclass="bold">New Virtual Machine</b> wizard in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, you will typically see one IDE controller in the machine's <b outputclass="bold">Storage</b> settings. The virtual CD/DVD drive will be attached to one of the four ports of this controller.</p>
    3615      </li>
    3716      <li>
    38         <p><b outputclass="bold">Serial ATA (SATA)</b> is a more
    39           recent standard than IDE. Compared to IDE, it supports both
    40           much higher speeds and more devices per controller. Also, with
    41           physical hardware, devices can be added and removed while the
    42           system is running. The standard interface for SATA controllers
    43           is called Advanced Host Controller Interface (AHCI).
    44         </p>
    45         <p>Like a real SATA controller, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s virtual SATA controller
    46           operates faster and also consumes fewer CPU resources than the virtual IDE controller. Also, this enables you
    47           to connect up to 30 virtual hard disks to one machine instead of just three, when compared to the <ph
    48             conkeyref="vbox-conkeyref-phrases/product-name"/> IDE controller with a DVD drive attached. </p>
    49         <p>
    50           For this reason, depending on the selected guest OS,
    51           <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses SATA as the default for newly created
    52           virtual machines. One virtual SATA controller is created by
    53           default, and the default disk that is created with a new VM is
    54           attached to this controller.
    55         </p>
     17        <p><b outputclass="bold">Serial ATA (SATA)</b> is a more recent standard than IDE. Compared to IDE, it supports both much higher speeds and more devices per controller. Also, with physical hardware, devices can be added and removed while the system is running. The standard interface for SATA controllers is called Advanced Host Controller Interface (AHCI).</p>
     18        <p>Like a real SATA controller, <ph conkeyref="vbox-conkeyref-phrases/product-name"/>'s virtual SATA controller operates faster and also consumes fewer CPU resources than the virtual IDE controller. Also, this enables you to connect up to 30 virtual hard disks to one machine instead of just three, when compared to the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> IDE controller with a DVD drive attached.</p>
     19        <p> For this reason, depending on the selected guest OS, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> uses SATA as the default for newly created virtual machines. One virtual SATA controller is created by default, and the default disk that is created with a new VM is attached to this controller.</p>
    5620        <note>
    57           <p>The entire SATA controller and the virtual disks attached to it, including those in IDE compatibility mode,
    58             will not be seen by OSes that do not have device support for AHCI. In particular, <i>there is no support for
    59               AHCI in Windows versions before Windows Vista</i>. Legacy Windows versions such as Windows XP, even with
    60             SP3 installed, will not see such disks unless you install additional drivers. It is possible to switch from
    61             IDE to SATA after installation by installing the SATA drivers and changing the controller type in the VM <b
    62               outputclass="bold">Settings</b> window. </p>
    63           <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> recommends the Intel Matrix Storage drivers, which
    64             can be downloaded from <ph>http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=2101</ph>. </p>
     21          <p>The entire SATA controller and the virtual disks attached to it, including those in IDE compatibility mode, will not be seen by OSes that do not have device support for AHCI. In particular, <i>there is no support for AHCI in Windows versions before Windows Vista</i>. Legacy Windows versions such as Windows XP, even with SP3 installed, will not see such disks unless you install additional drivers. It is possible to switch from IDE to SATA after installation by installing the SATA drivers and changing the controller type in the VM <b outputclass="bold">Settings</b> window.</p>
     22          <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> recommends the Intel Matrix Storage drivers, which can be downloaded from <ph>http://downloadcenter.intel.com/Product_Filter.aspx?ProductID=2101</ph>.</p>
    6523        </note>
    66         <p>To add a SATA controller to a machine for which it has not been enabled by default, either because it was
    67           created by an earlier version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, or because SATA is not
    68           supported by default by the selected guest OS, do the following. Go to the <b outputclass="bold">Storage</b>
    69           page of the machine's <b outputclass="bold">Settings</b> window, click <b outputclass="bold">Add
    70             Controller</b> under the Storage Tree box and then select <b outputclass="bold">Add SATA Controller</b>. The
    71           new controller appears as a separate PCI device in the virtual machine, and you can add virtual disks to it. </p>
     24        <p>To add a SATA controller to a machine for which it has not been enabled by default, either because it was created by an earlier version of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, or because SATA is not supported by default by the selected guest OS, do the following. Go to the <b outputclass="bold">Storage</b> page of the machine's <b outputclass="bold">Settings</b> window, click <b outputclass="bold">Add Controller</b> under the Storage Tree box and then select <b outputclass="bold">Add SATA Controller</b>. The new controller appears as a separate PCI device in the virtual machine, and you can add virtual disks to it.</p>
    7225        <p>To change the IDE compatibility mode settings for the SATA controller, see <xref href="../cli_topics/vboxmanage-storagectl.dita"/>. </p>
    7326      </li>
    7427      <li>
    75         <p><b outputclass="bold">SCSI</b> is another established
    76           industry standard, standing for Small Computer System
    77           Interface. SCSI is as a generic interface for data transfer
    78           between all kinds of devices, including storage devices. SCSI
    79           is still used for connecting some hard disks and tape devices,
    80           but it has mostly been displaced in commodity hardware. It is
    81           still in common use in high-performance workstations and
    82           servers.
    83         </p>
    84         <p>Primarily for compatibility with other virtualization software, <ph
    85             conkeyref="vbox-conkeyref-phrases/product-name"/> optionally supports LSI Logic and BusLogic SCSI
    86           controllers, to each of which up to fifteen virtual hard disks can be attached. </p>
    87         <p>To enable a SCSI controller, on the <b outputclass="bold">Storage</b> page of a virtual machine's <b
    88             outputclass="bold">Settings</b> window, click <b outputclass="bold">Add Controller</b> under the Storage
    89           Tree box and then select <b outputclass="bold">Add SCSI Controller</b>. The new controller appears as a
    90           separate PCI device in the virtual machine. </p>
     28        <p><b outputclass="bold">SCSI</b> is another established industry standard, standing for Small Computer System Interface. SCSI is as a generic interface for data transfer between all kinds of devices, including storage devices. SCSI is still used for connecting some hard disks and tape devices, but it has mostly been displaced in commodity hardware. It is still in common use in high-performance workstations and servers.</p>
     29        <p>Primarily for compatibility with other virtualization software, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> optionally supports LSI Logic and BusLogic SCSI controllers, to each of which up to fifteen virtual hard disks can be attached.</p>
     30        <p>To enable a SCSI controller, on the <b outputclass="bold">Storage</b> page of a virtual machine's <b outputclass="bold">Settings</b> window, click <b outputclass="bold">Add Controller</b> under the Storage Tree box and then select <b outputclass="bold">Add SCSI Controller</b>. The new controller appears as a separate PCI device in the virtual machine.</p>
    9131        <note>
    92           <p>As with the other controller types, a SCSI controller will only be seen by OSes with device support for it.
    93             Windows 2003 and later ships with drivers for the LSI Logic controller, while Windows NT 4.0 and Windows
    94             2000 ships with drivers for the BusLogic controller. Windows XP ships with drivers for neither. </p>
     32          <p>As with the other controller types, a SCSI controller will only be seen by OSes with device support for it. Windows 2003 and later ships with drivers for the LSI Logic controller, while Windows NT 4.0 and Windows 2000 ships with drivers for the BusLogic controller. Windows XP ships with drivers for neither.</p>
    9533        </note>
    9634      </li>
    9735      <li>
    98         <p><b outputclass="bold">Serial Attached SCSI (SAS)</b> is
    99           another bus standard which uses the SCSI command set. As
    100           opposed to SCSI physical devices, serial cables are used
    101           instead of parallel cables. This simplifies physical device
    102           connections. In some ways, therefore, SAS is to SCSI what SATA
    103           is to IDE: it enables more reliable and faster connections.
    104         </p>
    105         <p>To support high-end guests which require SAS controllers, <ph conkeyref="vbox-conkeyref-phrases/product-name"
    106           /> emulates a LSI Logic SAS controller, which can be enabled much the same way as a SCSI controller. At this
    107           time, up to 255 devices can be connected to the SAS controller. </p>
     36        <p><b outputclass="bold">Serial Attached SCSI (SAS)</b> is another bus standard which uses the SCSI command set. As opposed to SCSI physical devices, serial cables are used instead of parallel cables. This simplifies physical device connections. In some ways, therefore, SAS is to SCSI what SATA is to IDE: it enables more reliable and faster connections.</p>
     37        <p>To support high-end guests which require SAS controllers, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> emulates a LSI Logic SAS controller, which can be enabled much the same way as a SCSI controller. At this time, up to 255 devices can be connected to the SAS controller.</p>
    10838        <note>
    109           <p>As with SATA, the SAS controller will only be seen by OSes with device support for it. In particular,
    110               <i>there is no support for SAS in Windows before Windows Vista</i>. So Windows XP, even SP3, will not see
    111             such disks unless you install additional drivers. </p>
     39          <p>As with SATA, the SAS controller will only be seen by OSes with device support for it. In particular, <i>there is no support for SAS in Windows before Windows Vista</i>. So Windows XP, even SP3, will not see such disks unless you install additional drivers.</p>
    11240        </note>
    11341      </li>
    11442      <li>
    115         <p>The <b outputclass="bold">USB mass storage device class</b> is a standard to connect external storage devices
    116           like hard disks or flash drives to a host through USB. All major OSes support these devices and ship generic
    117           drivers making third-party drivers superfluous. In particular, legacy OSes without support for SATA
    118           controllers may benefit from USB mass storage devices. </p>
    119         <p>The virtual USB storage controller offered by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> works
    120           differently to the other storage controller types. While most storage controllers appear as a single PCI
    121           device to the guest with multiple disks attached to it, the USB-based storage controller does not appear as
    122           virtual storage controller. Each disk attached to the controller appears as a dedicated USB device to the
    123           guest. </p>
     43        <p>The <b outputclass="bold">USB mass storage device class</b> is a standard to connect external storage devices like hard disks or flash drives to a host through USB. All major OSes support these devices and ship generic drivers making third-party drivers superfluous. In particular, legacy OSes without support for SATA controllers may benefit from USB mass storage devices.</p>
     44        <p>The virtual USB storage controller offered by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> works differently to the other storage controller types. While most storage controllers appear as a single PCI device to the guest with multiple disks attached to it, the USB-based storage controller does not appear as virtual storage controller. Each disk attached to the controller appears as a dedicated USB device to the guest.</p>
    12445        <note>
    125           <p>Booting from drives attached using USB is only supported when EFI is used as the BIOS lacks USB support. </p>
     46          <p>Booting from drives attached using USB is only supported when EFI is used as the BIOS lacks USB support.</p>
    12647        </note>
    12748      </li>
    12849      <li>
    129         <p><b outputclass="bold">Non volatile memory express
    130           (NVMe)</b> is a standard for connecting non volatile
    131           memory (NVM) directly over PCI Express to lift the bandwidth
    132           limitation of the previously used SATA protocol for
    133           solid-state devices. Unlike other standards the command set is
    134           very simple in order to achieve maximum throughput and is not
    135           compatible with ATA or SCSI. OSes need to support NVMe devices
    136           to make use of them. For example, Windows 8.1 added native
    137           NVMe support. For Windows 7, native support was added with an
    138           update.
    139         </p>
    140         <p>The NVMe controller is part of the extension pack. </p>
     50        <p><b outputclass="bold">Non volatile memory express (NVMe)</b> is a standard for connecting non volatile memory (NVM) directly over PCI Express to lift the bandwidth limitation of the previously used SATA protocol for solid-state devices. Unlike other standards the command set is very simple in order to achieve maximum throughput and is not compatible with ATA or SCSI. OSes need to support NVMe devices to make use of them. For example, Windows 8.1 added native NVMe support. For Windows 7, native support was added with an update.</p>
     51        <p>The NVMe controller is part of the extension pack.</p>
    14152        <note>
    14253          <p>Booting from drives attached using NVMe is only supported when EFI is used as the BIOS lacks the
    … …  
    14455        </note>
    14556      </li>
     57    </ul>
     58    <p>In summary, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> gives you the following categories of virtual storage slots:</p>
     59    <ul>
    14660      <li>
    147         <p><b outputclass="bold">Virtual I/O Device SCSI</b> is a
    148           standard to connect virtual storage devices like hard disks or
    149           optical drives to a VM. Recent Linux and Windows versions
    150           support these devices, but Windows needs additional drivers.
    151           Currently virtio-scsi controller support is experimental.
    152         </p>
    153         <note>
    154           <p>The virtio-scsi controller will only be seen by OSes with device support for it. In particular, <i>there is
    155               no built-in support in Windows</i>. So Windows will not see such disks unless you install additional
    156             drivers. </p>
    157         </note>
     61        <p>Four slots attached to the traditional IDE controller, which are always present. One of these is typically a virtual CD/DVD drive.</p>
     62      </li>
     63      <li>
     64        <p>30 slots attached to the SATA controller, if enabled and supported by the guest OS.</p>
     65      </li>
     66      <li>
     67        <p>15 slots attached to the SCSI controller, if enabled and supported by the guest OS.</p>
     68      </li>
     69      <li>
     70        <p>Up to 255 slots attached to the SAS controller, if enabled and supported by the guest OS.</p>
     71      </li>
     72      <li>
     73        <p>Eight slots attached to the virtual USB controller, if enabled and supported by the guest OS.</p>
     74      </li>
     75      <li>
     76        <p>Up to 255 slots attached to the NVMe controller, if enabled and supported by the guest OS.</p>
    15877      </li>
    15978    </ul>
    160     <p>In summary, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> gives you the following categories of virtual
    161       storage slots: </p>
    162     <ul>
    163       <li>
    164         <p>Four slots attached to the traditional IDE controller, which are always present. One of these is typically a
    165           virtual CD/DVD drive. </p>
    166       </li>
    167       <li>
    168         <p>30 slots attached to the SATA controller, if enabled and supported by the guest OS. </p>
    169       </li>
    170       <li>
    171         <p>15 slots attached to the SCSI controller, if enabled and supported by the guest OS. </p>
    172       </li>
    173       <li>
    174         <p>Up to 255 slots attached to the SAS controller, if enabled and supported by the guest OS. </p>
    175       </li>
    176       <li>
    177         <p>Eight slots attached to the virtual USB controller, if enabled and supported by the guest OS. </p>
    178       </li>
    179       <li>
    180         <p>Up to 255 slots attached to the NVMe controller, if enabled and supported by the guest OS. </p>
    181       </li>
    182       <li>
    183         <p>Up to 256 slots attached to the virtio-scsi controller, if enabled and supported by the guest OS. </p>
    184       </li>
    185     </ul>
    186     <p>Given this large choice of storage controllers, you may not know which one to choose. In general, you should
    187       avoid IDE unless it is the only controller supported by your guest. Whether you use SATA, SCSI, or SAS does not
    188       make any real difference. The variety of controllers is only supplied by <ph
    189         conkeyref="vbox-conkeyref-phrases/product-name"/> for compatibility with existing hardware and other
    190       hypervisors. </p>
     79    <p>Given this large choice of storage controllers, you may not know which one to choose. In general, you should avoid IDE unless it is the only controller supported by your guest. Whether you use SATA, SCSI, or SAS does not make any real difference. The variety of controllers is only supplied by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> for compatibility with existing hardware and other hypervisors.</p>
    19180  </body>
    19281 

  • trunk/doc/manual/en_US/dita/topics/hyperv-support.dita

    r105335 r108750  
    55 
    66  <body>
    7     <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> can be used on a Windows host where Hyper-V is running.
    8       This is an experimental feature. </p>
    9     <p>No configuration is required. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> detects Hyper-V automatically
    10       and uses Hyper-V as the virtualization engine for the host system. The CPU icon in the VM window status bar
    11       indicates that Hyper-V is being used. </p>
    12     <note>
    13       <p>When using this feature, some host systems might experience significant <ph
    14           conkeyref="vbox-conkeyref-phrases/product-name"/> performance degradation. </p>
    15     </note>
     7    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> can be used on a Windows host where Hyper-V is running but host systems might experience significant <ph conkeyref="vbox-conkeyref-phrases/product-name"/> performance degradation.</p>
     8    <p>Assuming Windows Hypervisor Platform is running, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> detects Hyper-V automatically and uses Hyper-V as the virtualization engine for the host system. The CPU icon in the VM window status bar indicates that Hyper-V is being used.</p>
     9    <note>In Windows, <b>Windows Hypervisor Platform</b> must be enabled in addition to <b>Hyper-V</b>.</note>
    1610  </body>
    1711 

  • trunk/doc/manual/en_US/dita/topics/iscsi-intnet.dita

    r107390 r108750  
    66  <body>
    77    <p>As an experimental feature, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables access to an iSCSI target running in a virtual machine which is configured to use Internal Networking mode. See <xref href="storage-iscsi.dita">iSCSI Servers</xref>, <xref href="network_internal.dita">Internal Networking</xref>, and <xref href="../cli_topics/vboxmanage-storageattach.dita"/>.</p>
    8     <p>The IP stack accessing Internal Networking must be configured in the virtual machine which accesses the iSCSI
    9       target. A free static IP and a MAC address not used by other virtual machines must be chosen. In the example
    10       below, adapt the name of the virtual machine, the MAC address, the IP configuration, and the Internal Networking
    11       name (MyIntNet) according to your needs. The following eight commands must first be issued: </p>
     8    <p>The IP stack accessing Internal Networking must be configured in the virtual machine which accesses the iSCSI target. A free static IP and a MAC address not used by other virtual machines must be chosen. In the example below, adapt the name of the virtual machine, the MAC address, the IP configuration, and the Internal Networking name (MyIntNet) according to your needs. The following eight commands must first be issued:</p>
    129    <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> \
    1310VBoxInternal/Devices/IntNetIP/0/Trusted 1
    … …  
    2623$ VBoxManage setextradata <varname>VM-name</varname> \
    2724VBoxInternal/Devices/IntNetIP/0/LUN#0/Config/IsService 1</pre>
    28     <p>Finally the iSCSI disk must be attached with the <codeph>--intnet</codeph> option to tell the iSCSI initiator to
    29       use internal networking, as follows: </p>
     25    <p>Finally the iSCSI disk must be attached with the <codeph>--intnet</codeph> option to tell the iSCSI initiator to use internal networking, as follows:</p>
    3026    <pre xml:space="preserve">$ VBoxManage storageattach ... --medium iscsi --server 10.0.9.30 \
    3127--target iqn.2008-12.com.sun:sampletarget --intnet</pre>
    32     <p>Compared to a regular iSCSI setup, the IP address of the target <i>must</i> be specified as a numeric IP address,
    33       as there is no DNS resolver for internal networking. </p>
    34     <p>The virtual machine with the iSCSI target should be started before the VM using it is powered on. If a virtual
    35       machine using an iSCSI disk is started without having the iSCSI target powered up, it can take up to 200 seconds
    36       to detect this situation. The VM will fail to power up. </p>
     28    <p>Compared to a regular iSCSI setup, the IP address of the target <i>must</i> be specified as a numeric IP address, as there is no DNS resolver for internal networking.</p>
     29    <p>The virtual machine with the iSCSI target should be started before the VM using it is powered on. If a virtual machine using an iSCSI disk is started without having the iSCSI target powered up, it can take up to 200 seconds to detect this situation. The VM will fail to power up.</p>
    3730  </body>
    3831 

  • trunk/doc/manual/en_US/dita/topics/macosxguests.dita

    r107390 r108750  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="macosxguests">
    4   <title><?oxy_comment_start author="Mhari Duncan" timestamp="20241217T143119+0000" comment="Tidy up this topic"?>macOS Guests<?oxy_comment_end?></title>
     4  <title>macOS Guests</title>
    55  <body>
    6     <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to install and execute unmodified versions of macOS and OS X guests on supported host hardware. This feature is experimental and thus unsupported. </p>
    7     <p>Be aware of the following important issues before you try to install a macOS guest: </p>
     6    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> enables you to install and execute unmodified versions of macOS and Mac OS X guests on supported host hardware. This feature is experimental and thus unsupported.</p>
     7    <p>Be aware of the following important issues before you try to install a macOS guest:</p>
    88    <ul>
    99      <li>
    10         <p>macOS is commercial, licensed software and contains <b outputclass="bold">both license and technical restrictions</b> that limit its use to certain hardware and usage scenarios. You must understand and comply with these restrictions. </p>
    11         <p>In particular, Apple prohibits the installation of most versions of macOS on non-Apple hardware. </p>
    12         <p>These license restrictions are also enforced on a technical level. macOS verifies that it is running on Apple hardware. Most DVDs that accompany Apple hardware check for the exact model. These restrictions are <i>not</i> circumvented by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and continue to apply. </p>
     10        <p>macOS is commercial, licensed software and contains <b outputclass="bold">both license and technical restrictions</b> that limit its use to certain hardware and usage scenarios. You must understand and comply with these restrictions.</p>
     11        <p>In particular, Apple prohibits the installation of most versions of macOS on non-Apple hardware.</p>
     12        <p>These license restrictions are also enforced on a technical level. macOS verifies that it is running on Apple hardware. Most DVDs that accompany Apple hardware check for the exact model. These restrictions are <i>not</i> circumvented by <ph conkeyref="vbox-conkeyref-phrases/product-name"/> and continue to apply.</p>
    1313      </li>
    1414      <li>
    15         <p>Only <b outputclass="bold">CPUs</b> that are known and tested by Apple are supported. As a result, if your Intel CPU is newer than the macOS build, or if you have a non-Intel CPU, you will likely encounter a panic during bootup with an "Unsupported CPU" exception. </p>
    16         <p>Ensure that you use the macOS DVD that comes with your Apple hardware. </p>
     15        <p>Only CPUs that are known and tested by Apple are supported. As a result, if your Intel CPU is newer than the macOS build, or if you have a non-Intel CPU, you will likely encounter a panic during bootup with an <uicontrol>Unsupported CPU</uicontrol> exception.</p>
     16        <p>Ensure that you use the macOS DVD that comes with your Apple hardware.</p>
    1717      </li>
    1818      <li>
    19         <p>The macOS installer expects the hard disk to be <i>partitioned</i>. So, the installer will not offer a partition selection to you. Before you can install the software successfully, start the Disk Utility from the Tools menu and partition the hard disk. Close the Disk Utility and proceed with the installation. </p>
     19        <p>The macOS installer expects the hard disk to be <i>partitioned</i>. So, the installer will not offer a partition selection to you. Before you can install the software successfully, start the <uicontrol>Disk Utility</uicontrol> from the <uicontrol>Tools</uicontrol> menu and partition the hard disk. Close the Disk Utility and proceed with the installation.</p>
    2020      </li>
    2121    </ul>
    2222    <p>Limitations<ul>
    2323        <li>
    24           <p>Mac OS X guests can only run on a certain host hardware. For details about license and host hardware limitations. See <xref href="macosxguests.dita">Mac OS X Guests</xref> and check the Apple software license conditions.</p>
     24          <p>The graphics resolution currently defaults to 1024x768 as macOS falls back to the built-in EFI display support. See <xref href="efividmode.dita">Video Modes in EFI</xref> for more information on how to change EFI video modes.</p>
    2525        </li>
    2626        <li>
    27           <p>The graphics resolution currently defaults to 1024x768 as Mac OS X falls back to the built-in EFI display support. See <xref href="efividmode.dita">Video Modes in EFI</xref> for more information on how to change EFI video modes.</p>
     27          <p>Depending on your system and version of macOS, you might experience guest hangs after some time. This can be fixed by turning off energy saving. Set the timeout to <uicontrol>Never </uicontrol>in the system preferences.</p>
    2828        </li>
    2929        <li>
    30           <p>Depending on your system and version of Mac OS X, you might experience guest hangs after some time. This can be fixed by turning off energy saving. Set the timeout to "Never" in the system preferences.</p>
    31         </li>
    32         <li>
    33           <p>By default, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> EFI enables debug output of the Mac OS X kernel to help you diagnose boot problems. Note that there is a lot of output and not all errors are fatal. They would also show when using a physical Apple Macintosh computer. You can turn off these messages by using the following command:</p>
     30          <p>By default, the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> EFI enables debug output of the macOS kernel to help you diagnose boot problems. Note that there is a lot of output and not all errors are fatal. They would also show when using a physical Apple computer. You can turn off these messages by using the following command:</p>
    3431          <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> "VBoxInternal2/EfiBootArgs" "  "</pre>
    35           <p> To revert to the previous behavior, use the following command: </p>
     32          <p> To revert to the previous behavior, use the following command:</p>
    3633          <pre xml:space="preserve">$ VBoxManage setextradata <varname>VM-name</varname> "VBoxInternal2/EfiBootArgs" ""</pre>
    3734        </li>
    3835        <li>
    39           <p>It is currently not possible to start a Mac OS X guest in safe mode by specifying the <codeph>-x</codeph> option in <codeph>VBoxInternal2/EfiBootArgs</codeph> extradata. </p>
     36          <p>It is currently not possible to start a macOS guest in safe mode by specifying the <codeph>-x</codeph> option in <codeph>VBoxInternal2/EfiBootArgs</codeph> extradata.</p>
    4037        </li>
    4138      </ul></p>

  • trunk/doc/manual/en_US/dita/topics/nested-virt.dita

    r107390 r108750  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="nested-virt">
    4   <title>Nested Virtualization</title>
     4  <title><?oxy_comment_start author="Mhari Duncan" timestamp="20250314T143917+0000" comment="Nested hyper-V to be added after 7.2"?>Nested Virtualization<?oxy_comment_end?></title>
    55 
    66  <body>
    7     <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports <i>nested virtualization</i>. This feature enables
    8       the passthrough of hardware virtualization functions to the guest VM. That means that you can install a
    9       hypervisor, such as <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, Oracle VM Server or KVM, on an <ph
    10         conkeyref="vbox-conkeyref-phrases/product-name"/> guest. You can then create and run VMs within the guest VM. </p>
    11     <p>Hardware virtualization features not present on the host CPU will not be exposed to the guest. In addition, some
    12       features such as nested paging are not yet supported for passthrough to the guest. </p>
    13     <p>You can enable the nested virtualization feature in one of the following ways: </p>
     7    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports <i>nested virtualization</i>. This feature enables the passthrough of hardware virtualization functions to the guest VM. That means that you can install a hypervisor, such as <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, Oracle VM Server or KVM, on an <ph conkeyref="vbox-conkeyref-phrases/product-name"/> guest. You can then create and run VMs within the guest VM.</p>
     8    <p>Hardware virtualization features not present on the host CPU will not be exposed to the guest. In addition, some features such as nested paging are not yet supported for passthrough to the guest.</p>
     9    <p>You can enable the nested virtualization feature in one of the following ways:</p>
    1410    <ul>
    1511      <li>
    16         <p>From <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, select the <b outputclass="bold">Enable Nested
    17             VT-x/AMD-V</b> check box on the <b outputclass="bold">Processor</b> tab. To disable the feature, deselect
    18           the check box. </p>
     12        <p>From <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>, select the <b outputclass="bold">Enable Nested VT-x/AMD-V</b> check box on the <b outputclass="bold">Processor</b> tab. To disable the feature, deselect the check box.</p>
    1913      </li>
    2014      <li>

  • trunk/doc/manual/en_US/dita/topics/network_cloud.dita

    r108599 r108750  
    55 
    66  <body>
    7     <p>Cloud networks can be used for connections from a local VM to a subnet on a remote <ph
    8         conkeyref="vbox-conkeyref-phrases/oci"/> instance. See <xref
    9         href="edit-network.dita#network-manager-cloud-network-tab"/> for details of how to create
    10       and configure a cloud network using the Network Manager tool in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>. </p>
     7    <p>Cloud networks can be used for connections from a local VM to a subnet on a remote <ph conkeyref="vbox-conkeyref-phrases/oci"/> instance. See <xref href="config-network.dita"/> for details of how to create and configure a cloud network using the <uicontrol>Network</uicontrol> tool in <ph conkeyref="vbox-conkeyref-phrases/vbox-mgr"/>.</p>
    118    <p>To enable a cloud network interface for a virtual machine, do either of the following: </p>
    129    <ul>

  • trunk/doc/manual/en_US/dita/topics/otherextpacks.dita

    r105335 r108750  
    55 
    66  <body>
    7     <p>Another extension pack called VNC is available. This extension pack is open source and replaces the previous
    8       integration of the VNC remote access protocol. This is experimental code, and is initially available in the <ph
    9         conkeyref="vbox-conkeyref-phrases/product-name"/> source code package only. It is to a large portion code
    10       contributed by users, and is not supported in any way by Oracle. </p>
    11     <p>The keyboard handling is severely limited, and only the US keyboard layout works. Other keyboard layouts will
    12       have at least some keys which produce the wrong results, often with quite surprising effects, and for layouts
    13       which have significant differences to the US keyboard layout it is most likely unusable. </p>
    14     <p>It is possible to install both the <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/> and VNC, but only one VRDE
    15       module can be active at any time. The following command switches to the VNC VRDE module in VNC: </p>
     7    <p>Another extension pack called VNC is available. This extension pack is open source and replaces the previous integration of the VNC remote access protocol. This is available in the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> source code package but it is code contributed by users, and is not supported in any way by Oracle.</p>
     8    <p>The keyboard handling is severely limited, and only the US keyboard layout works. Other keyboard layouts will have at least some keys which produce the wrong results, often with quite surprising effects, and for layouts which have significant differences to the US keyboard layout it is most likely unusable.</p>
     9    <p>It is possible to install both the <ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/> and VNC, but only one VRDE module can be active at any time. The following command switches to the VNC VRDE module in VNC:</p>
    1610    <pre xml:space="preserve">VBoxManage setproperty vrdeextpack VNC</pre>
    17     <p>Configuring the remote access works very similarly to VRDP, see <xref href="vrde.dita#vrde"/>, with some
    18       limitations. VNC does not support specifying several port numbers, and the authentication is done differently. VNC
    19       can only deal with password authentication, and there is no option to use password hashes. This leaves no other
    20       choice than having a clear-text password in the VM configuration, which can be set with the following command: </p>
     11    <p>Configuring the remote access works very similarly to VRDP, see <xref href="vrde.dita#vrde"/>, with some limitations. VNC does not support specifying several port numbers, and the authentication is done differently. VNC can only deal with password authentication, and there is no option to use password hashes. This leaves no other choice than having a clear-text password in the VM configuration, which can be set with the following command:</p>
    2112    <pre xml:space="preserve">VBoxManage modifyvm <varname>VM-name</varname> --vrde-property VNCPassword=secret</pre>
    22     <p>The user is responsible for keeping this password secret, and it should be removed when a VM configuration is
    23       passed to another person, for whatever purpose. Some VNC servers claim to have encrypted passwords in the
    24       configuration. This is not true encryption, it is only concealing the passwords, which is only as secure as using
    25       clear-text passwords. </p>
    26     <p>The following command switches back to VRDP, if installed: </p>
     13    <p>The user is responsible for keeping this password secret, and it should be removed when a VM configuration is passed to another person, for whatever purpose. Some VNC servers claim to have encrypted passwords in the configuration. This is not true encryption, it is only concealing the passwords, which is only as secure as using clear-text passwords.</p>
     14    <p>The following command switches back to VRDP, if installed:</p>
    2715    <pre xml:space="preserve">VBoxManage setproperty vrdeextpack "<ph conkeyref="vbox-conkeyref-phrases/vbox-ext"/>"</pre>
    2816  </body>

  • trunk/doc/manual/en_US/dita/topics/pcspeaker_passthrough.dita

    r105335 r108750  
    55 
    66  <body>
    7     <p>As an experimental feature, primarily due to being limited to Linux host only and unknown Linux distribution
    8       coverage, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports passing through the PC speaker to the
    9       host. The PC speaker, sometimes called the system speaker, is a way to produce audible feedback such as beeps
    10       without the need for regular audio and sound card support. </p>
    11     <p>The PC speaker passthrough feature in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> handles beeps only.
    12       Advanced PC speaker use by the VM, such as PCM audio, will not work, resulting in undefined host behavior. </p>
    13     <p>Producing beeps on Linux is a very complex topic. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> offers a
    14       collection of options, in an attempt to make this work deterministically and reliably on as many Linux
    15       distributions and system configurations as possible. These are summarized in the following table. </p>
     7    <p>As an experimental feature, primarily due to being limited to Linux host only and unknown Linux distribution coverage, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports passing through the PC speaker to the host. The PC speaker, sometimes called the system speaker, is a way to produce audible feedback such as beeps without the need for regular audio and sound card support.</p>
     8    <p>The PC speaker passthrough feature in <ph conkeyref="vbox-conkeyref-phrases/product-name"/> handles beeps only. Advanced PC speaker use by the VM, such as PCM audio, will not work, resulting in undefined host behavior.</p>
     9    <p>Producing beeps on Linux is a very complex topic. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> offers a collection of options, in an attempt to make this work deterministically and reliably on as many Linux distributions and system configurations as possible. These are summarized in the following table.</p>
    1610    <table id="table-pcspeaker-config">
    1711      <title>PC Speaker Configuration Options</title>
    … …  
    7872            </entry>
    7973            <entry>
    80               <p><filepath>/dev/tty0</filepath> or
    81                 <filepath>/dev/vc/0</filepath>
    82                               </p>
     74              <p><filepath>/dev/tty0</filepath> or <filepath>/dev/vc/0</filepath></p>
    8375            </entry>
    8476            <entry>
    85               <p>
    86                 Can only be used by user <codeph>root</codeph> or
    87                 users with <codeph>cap_sys_tty_config</codeph>
    88                 capability.
    89               </p>
     77              <p>Can only be used by user <codeph>root</codeph> or users with <codeph>cap_sys_tty_config</codeph> capability.</p>
    9078            </entry>
    9179          </row>
    … …  
    9785            </entry>
    9886            <entry>
    99               <p>
    100                 A user-specified console or evdev device path.
    101               </p>
     87              <p>A user-specified console or evdev device path.</p>
    10288            </entry>
    10389            <entry>
    104               <p>
    105                 As for codes 1 to 3, but with a custom device path.
    106               </p>
     90              <p>As for codes 1 to 3, but with a custom device path.</p>
    10791            </entry>
    10892          </row>
    … …  
    11498            </entry>
    11599            <entry>
    116               <p>
    117                 <filepath>/dev/tty</filepath>
    118               </p>
     100              <p><filepath>/dev/tty</filepath></p>
    119101            </entry>
    120102            <entry>
    121               <p>
    122                 Standard beep only. Loses frequency and length. See code
    123                 2.
    124               </p>
     103              <p>Standard beep only. Loses frequency and length. See code 2.</p>
    125104            </entry>
    126105          </row>
    … …  
    132111            </entry>
    133112            <entry>
    134               <p>
    135                 A user-specified terminal device path.
    136               </p>
     113              <p>A user-specified terminal device path.</p>
    137114            </entry>
    138115            <entry>
    139               <p>
    140                 As for code 70, but with a custom device path.
    141               </p>
     116              <p>As for code 70, but with a custom device path.</p>
    142117            </entry>
    143118          </row>
    … …  
    149124            </entry>
    150125            <entry>
    151               <p>
    152                 All of the above.
    153               </p>
     126              <p>All of the above.</p>
    154127            </entry>
    155128            <entry>
    156               <p>
    157                 Tries all the available codes.
    158               </p>
     129              <p>Tries all the available codes.</p>
    159130            </entry>
    160131          </row>
    … …  
    162133      </tgroup>
    163134    </table>
    164     <p>To enable PC speaker passthrough use the following command: </p>
     135    <p>To enable PC speaker passthrough use the following command:</p>
    165136    <pre xml:space="preserve">VBoxManage setextradata <varname>VM-name</varname> "VBoxInternal/Devices/i8254/0/Config/PassthroughSpeaker" <varname>N</varname>
    166137               </pre>
    167     <p>Replace <varname>N</varname> with the code representing the case you want to use. Changing this setting takes
    168       effect when you next start the VM. It is safe to enable PC speaker passthrough on all host OSes. It will only have
    169       an effect on Linux. </p>
    170     <p>The VM log file, <filepath>VBox.log</filepath>, contains lines with the prefix <codeph>PIT: speaker:</codeph>
    171       showing the PC speaker passthrough setup activities. It gives hints which device it picked or why it failed. </p>
    172     <p>Enabling PC speaker passthrough for the VM is usually the simple part. The real difficulty is making sure that
    173         <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can access the necessary device, because in a typical
    174       Linux install most of them can only be accessed by user <codeph>root</codeph>. You should follow the preferred way
    175       to persistently change this, such as by referring to your distribution's documentation. Since there are countless
    176       Linux distribution variants, we can only give the general hints that there is often a way to give the X11 session
    177       user access to additional devices, or you need to find a working solution using a udev configuration file. If
    178       everything fails you might try setting the permissions using a script which is run late enough in the host system
    179       startup. </p>
    180     <p>Sometimes additional rules are applied by the kernel to limit access. For example, that the VM process must have
    181       the same controlling terminal as the device configured to be used for beeping, something which is often very
    182       difficult to achieve for GUI applications such as <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. The table
    183       above contains some hints, but in general refer to the Linux documentation. </p>
    184     <p>If you have trouble getting any beeps even if the device permissions are set up and VBox.log confirms that it
    185       uses evdev or console for the PC speaker control, check if your system has a PC speaker. Some systems do not have
    186       one. Other complications can arise from Linux rerouting the PC speaker output to a sound card. Check if the beeps
    187       are audible if you connect speakers to your sound card. Today almost all systems have one. Finally, check if the
    188       audio mixer control has a channel named <i>beep</i>, which could be hidden in the mixer settings, and that it is
    189       not muted. </p>
     138    <p>Replace <varname>N</varname> with the code representing the case you want to use. Changing this setting takes effect when you next start the VM. It is safe to enable PC speaker passthrough on all host OSes. It will only have an effect on Linux.</p>
     139    <p>The VM log file, <filepath>VBox.log</filepath>, contains lines with the prefix <codeph>PIT: speaker:</codeph> showing the PC speaker passthrough setup activities. It gives hints which device it picked or why it failed.</p>
     140    <p>Enabling PC speaker passthrough for the VM is usually the simple part. The real difficulty is making sure that <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can access the necessary device, because in a typical Linux install most of them can only be accessed by user <codeph>root</codeph>. You should follow the preferred way to persistently change this, such as by referring to your distribution's documentation. Since there are countless Linux distribution variants, we can only give the general hints that there is often a way to give the X11 session user access to additional devices, or you need to find a working solution using a udev configuration file. If everything fails you might try setting the permissions using a script which is run late enough in the host system startup.</p>
     141    <p>Sometimes additional rules are applied by the kernel to limit access. For example, that the VM process must have the same controlling terminal as the device configured to be used for beeping, something which is often very difficult to achieve for GUI applications such as <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. The table above contains some hints, but in general refer to the Linux documentation.</p>
     142    <p>If you have trouble getting any beeps even if the device permissions are set up and VBox.log confirms that it uses evdev or console for the PC speaker control, check if your system has a PC speaker. Some systems do not have one. Other complications can arise from Linux rerouting the PC speaker output to a sound card. Check if the beeps are audible if you connect speakers to your sound card. Today almost all systems have one. Finally, check if the audio mixer control has a channel named <i>beep</i>, which could be hidden in the mixer settings, and that it is not muted.</p>
    190143  </body>
    191144 

  • trunk/doc/manual/en_US/dita/topics/settings-acceleration.dita

    r107390 r108750  
    55 
    66  <body>
    7     <p>On this tab, you can configure <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to use hardware virtualization extensions that your host CPU supports. </p>
     7    <p>On this tab, you can configure <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to use hardware virtualization extensions that your host CPU supports.</p>
    88    <ul>
    99      <li>
    1010        <p><b outputclass="bold">Paravirtualization Interface:</b>
    11           <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides paravirtualization interfaces to improve time-keeping accuracy and performance of guest OSes. The options available are documented under the <codeph>--paravirt-provider</codeph> option in <xref href="vboxmanage.dita"/>
    12           <cmdname>modifyvm</cmdname>. For further details on the paravirtualization providers, see <xref href="gimproviders.dita">Paravirtualization Providers</xref>. </p>
     11          <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides paravirtualization interfaces to improve time-keeping accuracy and performance of guest OSs. The options available are documented under the <codeph>--paravirt-provider</codeph> option in <xref href="vboxmanage.dita"/>
     12          <cmdname>modifyvm</cmdname>. For further details on the paravirtualization providers, see <xref href="gimproviders.dita">Paravirtualization Providers</xref>.</p>
    1313      </li>
    1414      <li>
    15         <p><b outputclass="bold">Hardware Virtualization:</b>
    16             You can configure hardware virtualization features for each
    17             virtual machine.
    18           </p>
     15        <p><b outputclass="bold">Hardware Virtualization:</b></p>
    1916        <ul>
    2017          <li>
    21             <p><b outputclass="bold">Enable Nested Paging:</b>
    22                 If the host CPU supports the nested paging (AMD-V) or
    23                 EPT (Intel VT-x) features, then you can expect a
    24                 significant performance increase by enabling nested
    25                 paging in addition to hardware virtualization. For
    26                 technical details, see <xref href="nestedpaging.dita">Nested Paging and VPIDs</xref>.
    27                 For Intel EPT security recommendations, see
    28                 <xref href="sec-rec-cve-2018-3646.dita">CVE-2018-3646</xref>.
    29               </p>
     18            <p><b outputclass="bold">Enable Nested Paging:</b> If the host CPU supports the nested paging (AMD-V) or EPT (Intel VT-x) features, then you can expect a significant performance increase by enabling nested paging in addition to hardware virtualization. For technical details, see <xref href="nestedpaging.dita">Nested Paging and VPIDs</xref>. For Intel EPT security recommendations, see <xref href="sec-rec-cve-2018-3646.dita">CVE-2018-3646</xref>.</p>
    3019          </li>
    3120        </ul>
    32         <p>Advanced users may be interested in technical details about hardware virtualization. See <xref
    33             href="hwvirt.dita">Hardware Virtualization</xref>. </p>
    3421      </li>
    3522    </ul>
    36     <p>In most cases, the default settings on the <b outputclass="bold">Acceleration</b> tab will work well. <ph conkeyref="vbox-conkeyref-phrases/product-name"/> selects sensible defaults, depending on the OS that you selected when you created the virtual machine. In certain situations, however, you may want to change the preconfigured defaults. </p>
    3723  </body>
    3824 

  • trunk/doc/manual/en_US/dita/topics/settings-motherboard.dita

    r108599 r108750  
    1414      </li>
    1515      <li>
    16         <p><b outputclass="bold">Boot Order:</b> Determines the
    17             order in which the guest OS will attempt to boot from the
    18             various virtual boot devices. Analogous to a real PC's BIOS
    19             setting, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can tell a guest OS to start from
    20             the virtual floppy, the virtual CD/DVD drive, the virtual
    21             hard drive (each of these as defined by the other VM
    22             settings), the network, or none of these.
    23           </p>
     16        <p><b outputclass="bold">Boot Order:</b> Determines the order in which the guest OS will attempt to boot from the various virtual boot devices. Analogous to a real PC's BIOS setting, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can tell a guest OS to start from the virtual floppy, the virtual CD/DVD drive, the virtual hard drive (each of these as defined by the other VM settings), the network, or none of these. </p>
    2417        <p>If you select <b outputclass="bold">Network</b>, the VM will attempt to boot from a network using the PXE mechanism. This needs to be configured in detail on the command line. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    2518      </li>
    2619      <li>
    27         <p><b outputclass="bold">Chipset (Can't be changed on VMs with an Arm architecture):</b> You can select which chipset will be presented to the virtual machine. PIIX3 is the default chipset for most guests. For some guest OSes such as Mac OS X, the PIIX3 chipset is not well supported. As a result, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports an emulation of the ICH9 chipset, which supports PCI express, three PCI buses, PCI-to-PCI bridges and Message Signaled Interrupts (MSI). This enables modern OSes to address more PCI devices and no longer requires IRQ sharing. Using the ICH9 chipset it is also possible to configure up to 36 network cards, compared to a maximum of eight network adapters with PIIX3. Note that ICH9 support is experimental and not recommended for guest OSes which do not require it. </p>
     20        <p><b outputclass="bold">Chipset (Can't be changed on VMs with an Arm architecture):</b> You can select which chipset will be presented to the virtual machine. PIIX3 is the default chipset for most guests. For some guest OSs, the PIIX3 chipset is not well supported. As a result, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> provides an emulation of the ICH9 chipset, which supports PCI express, three PCI buses, PCI-to-PCI bridges and Message Signaled Interrupts (MSI). This enables modern OSs to address more PCI devices and no longer requires IRQ sharing. Using the ICH9 chipset it is also possible to configure up to 36 network cards, compared to a maximum of eight network adapters with PIIX3.</p>
    2821      </li>
    2922      <li>
    30         <p><b outputclass="bold">TPM (Can't be changed on VMs with an Arm architecture):</b> Enables support for a Trusted Platform Module (TPM) security processor. Choose from the supported TPM versions. </p>
     23        <p><b outputclass="bold">TPM (Can't be changed on VMs with an Arm architecture):</b> Enables support for a Trusted Platform Module (TPM) security processor. Choose from the available TPM versions.</p>
    3124      </li>
    3225      <li>
    33         <p><b outputclass="bold">Pointing Device:</b> The
    34             default virtual pointing device for some guest OSes is the
    35             traditional PS/2 mouse. If set to <b outputclass="bold">USB
    36             Tablet</b>, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> reports to the virtual
    37             machine that a USB tablet device is present and communicates
    38             mouse events to the virtual machine through this device.
    39             Another setting is <b outputclass="bold">USB Multi-Touch
    40             Tablet</b>, which is suitable for guests running
    41             Windows 8 or later.
    42           </p>
    43         <p>Using the virtual USB tablet has the advantage that movements are reported in absolute coordinates, instead
    44           of as relative position changes. This enables <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to
    45           translate mouse events over the VM window into tablet events without having to "capture" the mouse in the
    46           guest as described in <xref href="keyb_mouse_normal.dita#keyb_mouse_normal"/>. This makes using the VM less
    47           tedious even if Guest Additions are not installed. </p>
     26        <p><b outputclass="bold">Pointing Device:</b> The default virtual pointing device for some guest OSs is the traditional PS/2 mouse. If set to <b outputclass="bold">USB Tablet</b>, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> reports to the virtual machine that a USB tablet device is present and communicates mouse events to the virtual machine through this device. Another setting is <b outputclass="bold">USB Multi-Touch Tablet</b>, which is suitable for guests running Windows 8 or later.</p>
     27        <p>Using the virtual USB tablet has the advantage that movements are reported in absolute coordinates, instead of as relative position changes. This enables <ph conkeyref="vbox-conkeyref-phrases/product-name"/> to translate mouse events over the VM window into tablet events without having to capture the mouse in the guest as described in <xref href="keyb_mouse_normal.dita#keyb_mouse_normal"/>. This makes using the VM less tedious even if Guest Additions are not installed.</p>
    4828      </li>
    4929      <li>
    50         <p><b outputclass="bold">Enable I/O APIC (Can't be changed on VMs with an Arm architecture):</b> Advanced Programmable Interrupt Controllers (APICs) are an x86 hardware feature that have replaced Programmable Interrupt Controllers (PICs). With an I/O APIC, OSes can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability. </p>
     30        <p><b outputclass="bold">Enable I/O APIC (Can't be changed on VMs with an Arm architecture):</b> Advanced Programmable Interrupt Controllers (APICs) are an x86 hardware feature that have replaced Programmable Interrupt Controllers (PICs). With an I/O APIC, OSs can use more than 16 interrupt requests (IRQs) and therefore avoid IRQ sharing for improved reliability.</p>
    5131        <note>
    52           <p>Enabling the I/O APIC is <i>required</i>, especially for 64-bit Windows guest OSes. It is also required if
    53             you want to use more than one virtual CPU in a virtual machine. </p>
     32          <p>Enabling the I/O APIC is <i>required</i>, especially for 64-bit Windows guest OSs. It is also required if you want to use more than one virtual CPU in a virtual machine.</p>
    5433        </note>
    55         <p>However, software support for I/O APICs has been unreliable with some OSes other than Windows. Also, the use
    56           of an I/O APIC slightly increases the overhead of virtualization and therefore slows down the guest OS a
    57           little. </p>
     34        <p>However, software support for I/O APICs has been unreliable with some OSs other than Windows. Also, the use of an I/O APIC slightly increases the overhead of virtualization and therefore slows down the guest OS a little.</p>
    5835        <note>
    59           <p>All Windows OSes install different kernels, depending on whether an I/O APIC is available. As with ACPI,
    60             the I/O APIC therefore <i>must not be turned off after installation</i> of a Windows guest OS. Turning it on
    61             after installation will have no effect however. </p>
     36          <p>All Windows OSs install different kernels, depending on whether an I/O APIC is available. As with ACPI, the I/O APIC therefore <i>must not be turned off after installation</i> of a Windows guest OS. Turning it on after installation will have no effect however.</p>
    6237        </note>
    6338      </li>
    6439      <li>
    65         <p><b outputclass="bold">Hardware Clock in UTC Time:</b>
    66             If selected, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will report the system time in
    67             UTC format to the guest instead of the local (host) time.
    68             This affects how the virtual real-time clock (RTC) operates
    69             and may be useful for UNIX-like guest OSes, which typically
    70             expect the hardware clock to be set to UTC.
    71           </p>
     40        <p><b outputclass="bold">Hardware Clock in UTC Time:</b> If selected, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> will report the system time in UTC format to the guest instead of the local (host) time. This affects how the virtual real-time clock (RTC) operates and may be useful for UNIX-like guest OSs, which typically expect the hardware clock to be set to UTC. </p>
    7241      </li>
    7342      <li>
    … …  
    8150      </li>
    8251    </ul>
    83     <p>In addition, you can turn off the <b outputclass="bold">Advanced Configuration and Power Interface (ACPI)</b>
    84       which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to the guest OS by default. </p>
     52    <p>In addition, you can turn off the <b outputclass="bold">Advanced Configuration and Power Interface (ACPI)</b> which <ph conkeyref="vbox-conkeyref-phrases/product-name"/> presents to the guest OS by default. </p>
    8553    <p>ACPI is the current industry standard to allow OSs to recognize hardware, configure motherboards and other devices and manage power. As most computers contain this feature and Windows and Linux support ACPI, it is also enabled by default in <ph conkeyref="vbox-conkeyref-phrases/product-name"/>. However, no ACPI information, such as battery status or power source, is reported to Oracle Solaris guests.</p>
    8654    <p>ACPI can only be turned off using the command line. See <xref href="../cli_topics/vboxmanage-modifyvm.dita"/>.</p>
    8755    <note>
    88       <p>All Windows OSes install different kernels, depending on whether ACPI is available. This means that ACPI
    89           <i>must not be turned off</i> after installation of a Windows guest OS. However, turning it on after
    90         installation will have no effect. </p>
     56      <p>All Windows OSs install different kernels, depending on whether ACPI is available. This means that ACPI <i>must not be turned off</i> after installation of a Windows guest OS. However, turning it on after installation will have no effect. </p>
    9157    </note>
    9258  </body>

  • trunk/doc/manual/en_US/dita/topics/sharedfolders.dita

    r107390 r108750  
    66           
    77            <body>
    8                <p>With the <i>shared folders</i> feature of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you
    9       can access files of your host system from within the guest system. This is similar to how you would use network
    10       shares in Windows networks, except that shared folders do not require networking, only the Guest Additions. Shared
    11       folders are supported with Windows 2000 or later, Linux, and Oracle Solaris guests. <ph
    12         conkeyref="vbox-conkeyref-phrases/product-name"/> includes experimental support for Mac OS X and OS/2 guests. </p>
     8               <p>With the <i>shared folders</i> feature of <ph conkeyref="vbox-conkeyref-phrases/product-name"/>, you can access files of your host system from within the guest system. This is similar to how you would use network shares in Windows networks, except that shared folders do not require networking, only the Guest Additions. Shared folders are supported with Windows 2000 or later, Linux, and Oracle Solaris guests.</p>
    139               <p>Shared folders physically reside on the <i>host</i> and are then shared with the guest, which uses a
    1410      special file system driver in the Guest Additions to talk to the host. For Windows guests, shared folders are

  • trunk/doc/manual/en_US/dita/topics/storage-cds.dita

    r107390 r108750  
    66           
    77            <body>
    8                <p>Virtual CD/DVD drives by default support only reading. The medium configuration is changeable at
    9       runtime. You can select between the following options to provide the medium data: </p>
     8               <p>Virtual CD/DVD drives by default support only reading. The medium configuration is changeable at runtime. You can select between the following options to provide the medium data:</p>
    109               <ul>
    1110                  <li>
    12                      <p><b outputclass="bold">Host Drive</b> defines that the guest can read from the medium in the host
    13           drive. </p>
     11                     <p><b outputclass="bold">Host Drive</b> defines that the guest can read from the medium in the host drive.</p>
    1412                  </li>
    1513                  <li>
    16                      <p><b outputclass="bold">Image file</b> gives the guest read-only access to the data in the image.
    17           This is typically an ISO file. </p>
     14                     <p><b outputclass="bold">Image file</b> gives the guest read-only access to the data in the image. This is typically an ISO file.</p>
    1815                  </li>
    1916                  <li>
    20                      <p><b outputclass="bold">Empty</b> means a drive without an inserted medium. </p>
     17                     <p><b outputclass="bold">Empty</b> means a drive without an inserted medium.</p>
    2118                  </li>
    2219               </ul>
    23                <p>Changing between the above, or changing a medium in the host drive that is accessed by a machine, or
    24       changing an image file will signal a medium change to the guest OS. The guest OS can then react to the change, for
    25       example by starting an installation program. </p>
    26                <p>Medium changes can be prevented by the guest, and <ph conkeyref="vbox-conkeyref-phrases/product-name"
    27       /> reflects that by locking the host drive if appropriate. You can force a medium removal in such situations by
    28       using the VirtualBox Manager or the <userinput>VBoxManage</userinput> command line tool. Effectively this is the
    29       equivalent of the emergency eject which many CD/DVD drives provide, with all associated side effects. The guest OS
    30       can issue error messages, just like on real hardware, and guest applications may misbehave. Use this with caution. </p>
     20               <p>Changing between the above, or changing a medium in the host drive that is accessed by a machine, or changing an image file will signal a medium change to the guest OS. The guest OS can then react to the change, for example by starting an installation program.</p>
     21               <p>Medium changes can be prevented by the guest, and <ph conkeyref="vbox-conkeyref-phrases/product-name"/> reflects that by locking the host drive if appropriate. You can force a medium removal in such situations by using the VirtualBox Manager or the <userinput>VBoxManage</userinput> command line tool. Effectively this is the equivalent of the emergency eject which many CD/DVD drives provide, with all associated side effects. The guest OS can issue error messages, just like on real hardware, and guest applications may misbehave. Use this with caution.</p>
    3122               <note>
    32                   <p>The identification string of the drive provided to the guest, displayed by configuration tools such
    33         as the Windows Device Manager, is always VBOX CD-ROM, irrespective of the current configuration of the virtual
    34         drive. This is to prevent hardware detection from being triggered in the guest OS every time the configuration
    35         is changed. </p>
     23                  <p>The identification string of the drive provided to the guest, displayed by configuration tools such as the Windows Device Manager, is always VBOX CD-ROM, irrespective of the current configuration of the virtual drive. This is to prevent hardware detection from being triggered in the guest OS every time the configuration is changed.</p>
    3624               </note>
    37                <p>The standard CD/DVD emulation enables reading of standard data CD and DVD formats only. As an
    38       experimental feature, for additional capabilities, it is possible to give the guest direct access to the CD/DVD
    39       host drive by enabling <i>passthrough</i> mode. Depending on the host hardware, this may potentially enable the
    40       following things to work: </p>
    41                <ul>
    42                   <li>
    43                      <p>CD/DVD writing from within the guest, if the host DVD drive is a CD/DVD writer </p>
    44                   </li>
    45                   <li>
    46                      <p>Playing audio CDs </p>
    47                   </li>
    48                   <li>
    49                      <p>Playing encrypted DVDs </p>
    50                   </li>
    51                </ul>
    52                <p>To enable host drive passthrough you can use the <codeph>--passthrough</codeph> option of the <userinput>VBoxManage storageattach</userinput> command. See <xref href="../cli_topics/vboxmanage-storageattach.dita"/>. </p>
    53                <p>Even if passthrough is enabled, unsafe commands, such as updating the drive firmware, will be blocked.
    54       Video CD formats are never supported, not even in passthrough mode, and cannot be played from a virtual machine. </p>
    55                <p>On Oracle Solaris hosts, passthrough requires running <ph
    56         conkeyref="vbox-conkeyref-phrases/product-name"/> with real root permissions due to security measures enforced
    57       by the host. </p>
    5825            </body>
    5926           

  • trunk/doc/manual/en_US/dita/topics/vboxsvc-session-0-known-issues.dita

    r107390 r108750  
    22<!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
    33<topic xml:lang="en-us" id="vboxsvc-session-0-known-issues">
    4   <title>Known Issues</title>
     4  <title>Issues Accessing Network Shares When VBoxSVC running in Windows Session 0</title>
    55 
    66  <body>
    77    <ul>
    88      <li>
    9         <p>Due to different Windows sessions having their own set of resources, there might be some issues with
    10           accessing network shares created in the interactive user session when at least one of the <ph
    11             conkeyref="vbox-conkeyref-phrases/product-name"/> processes are running in session 0. </p>
    12         <p>For accessing network shares within session 0, a possible workaround is to establish permanent access to the
    13           share and then restart the host. </p>
     9        <p>Due to different Windows sessions having their own set of resources, there might be some issues with accessing network shares created in the interactive user session when at least one of the <ph conkeyref="vbox-conkeyref-phrases/product-name"/> processes are running in session 0.</p>
     10        <p>For accessing network shares within session 0, a possible workaround is to establish permanent access to the share and then restart the host.</p>
    1411      </li>
    1512    </ul>

  • trunk/doc/manual/en_US/dita/topics/vboxsvc-session-0.dita

    r107390 r108750  
    55 
    66  <body>
    7     <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports executing the VBoxSVC in Windows session 0. This
    8       allows VBoxSVC to run like a regular Windows service, which in turn enables headless VMs to continue running even
    9       if the user logs out. <note>
    10         <p>This is currently an experimental feature. </p>
    11       </note>
    12                </p>
    13     <p>The feature is disabled by default and can be enabled by creating a REG_DWORD value
    14         <codeph>ServerSession0</codeph> in the key
    15         <codeph>HKEY_LOCAL_MACHINE\Software\Oracle\VirtualBox\VBoxSDS</codeph> of the Windows registry. Specify
    16         <codeph>1</codeph> as the value's data to enable the feature, or <codeph>0</codeph> to disable the feature. A
    17       host reboot is needed in order to make the change effective. </p>
     7    <p><ph conkeyref="vbox-conkeyref-phrases/product-name"/> supports executing the VBoxSVC in Windows session 0. This allows VBoxSVC to run like a regular Windows service, which in turn enables headless VMs to continue running even if the user logs out.</p>
     8    <p>The feature is disabled by default and can be enabled by creating a REG_DWORD value <codeph>ServerSession0</codeph> in the key <codeph>HKEY_LOCAL_MACHINE\Software\Oracle\VirtualBox\VBoxSDS</codeph> of the Windows registry. Specify <codeph>1</codeph> as the value's data to enable the feature, or <codeph>0</codeph> to disable the feature. A host reboot is needed in order to make the change effective.</p>
    189  </body>
    1910</topic>
Note: See TracChangeset for help on using the changeset viewer.

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