| 1 | <?xml version="1.0" encoding="UTF-8"?>
|
|---|
| 2 | <!DOCTYPE topic
|
|---|
| 3 | PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 4 | <topic xml:lang="en-us" id="storage-cds">
|
|---|
| 5 | <title>CD/DVD Support</title>
|
|---|
| 6 |
|
|---|
| 7 | <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>
|
|---|
| 10 | <ul>
|
|---|
| 11 | <li>
|
|---|
| 12 | <p><b outputclass="bold">Host Drive</b> defines that the guest can read from the medium in the host
|
|---|
| 13 | drive. </p>
|
|---|
| 14 | </li>
|
|---|
| 15 | <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>
|
|---|
| 18 | </li>
|
|---|
| 19 | <li>
|
|---|
| 20 | <p><b outputclass="bold">Empty</b> means a drive without an inserted medium. </p>
|
|---|
| 21 | </li>
|
|---|
| 22 | </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>
|
|---|
| 31 | <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>
|
|---|
| 36 | </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>
|
|---|
| 58 | </body>
|
|---|
| 59 |
|
|---|
| 60 | </topic>
|
|---|
