| 1 | <?xml version='1.0' encoding='UTF-8'?>
|
|---|
| 2 | <!DOCTYPE topic PUBLIC "-//OASIS//DTD DITA Topic//EN" "topic.dtd">
|
|---|
| 3 | <topic xml:lang="en-us" id="harddiskcontrollers">
|
|---|
| 4 | <title>Hard Disk Controllers</title>
|
|---|
| 5 |
|
|---|
| 6 | <body>
|
|---|
| 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>
|
|---|
| 8 | <ul>
|
|---|
| 9 | <li>
|
|---|
| 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 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>
|
|---|
| 15 | </li>
|
|---|
| 16 | <li>
|
|---|
| 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>
|
|---|
| 20 | <note>
|
|---|
| 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>
|
|---|
| 23 | </note>
|
|---|
| 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>
|
|---|
| 25 | <p>To change the IDE compatibility mode settings for the SATA controller, see <xref href="../cli_topics/vboxmanage-storagectl.dita"/>. </p>
|
|---|
| 26 | </li>
|
|---|
| 27 | <li>
|
|---|
| 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>
|
|---|
| 31 | <note>
|
|---|
| 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>
|
|---|
| 33 | </note>
|
|---|
| 34 | </li>
|
|---|
| 35 | <li>
|
|---|
| 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>
|
|---|
| 38 | <note>
|
|---|
| 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>
|
|---|
| 40 | </note>
|
|---|
| 41 | </li>
|
|---|
| 42 | <li>
|
|---|
| 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>
|
|---|
| 45 | <note>
|
|---|
| 46 | <p>Booting from drives attached using USB is only supported when EFI is used as the BIOS lacks USB support.</p>
|
|---|
| 47 | </note>
|
|---|
| 48 | </li>
|
|---|
| 49 | <li>
|
|---|
| 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>
|
|---|
| 52 | <note>
|
|---|
| 53 | <p>Booting from drives attached using NVMe is only supported when EFI is used as the BIOS lacks the
|
|---|
| 54 | appropriate driver. </p>
|
|---|
| 55 | </note>
|
|---|
| 56 | </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>
|
|---|
| 60 | <li>
|
|---|
| 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>
|
|---|
| 77 | </li>
|
|---|
| 78 | </ul>
|
|---|
| 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>
|
|---|
| 80 | </body>
|
|---|
| 81 |
|
|---|
| 82 | </topic>
|
|---|
