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="emul-hardware">
|
---|
4 | <title>Emulated Hardware</title>
|
---|
5 |
|
---|
6 | <body>
|
---|
7 | <p>
|
---|
8 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> virtualizes nearly all hardware of the host.
|
---|
9 | Depending on a VM's configuration, the guest will see the
|
---|
10 | following virtual hardware:
|
---|
11 | </p>
|
---|
12 | <ul>
|
---|
13 | <li>
|
---|
14 | <p><b outputclass="bold">Input devices.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
|
---|
15 | can emulate a standard PS/2 keyboard and mouse. These devices
|
---|
16 | are supported by most guest OSes.
|
---|
17 | </p>
|
---|
18 | <p>
|
---|
19 | In addition, <ph conkeyref="vbox-conkeyref-phrases/product-name"/> can provide virtual USB input
|
---|
20 | devices to avoid having to capture mouse and keyboard, as
|
---|
21 | described in <xref href="keyb_mouse_normal.dita#keyb_mouse_normal"/>.
|
---|
22 | </p>
|
---|
23 | </li>
|
---|
24 | <li>
|
---|
25 | <p><b outputclass="bold">Graphics.</b> The default
|
---|
26 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> graphics device for Windows guests is an SVGA
|
---|
27 | device. For Linux guests, the default graphics device emulates
|
---|
28 | a VMware SVGA graphics device. See
|
---|
29 | <xref href="settings-screen.dita#settings-screen"/>.
|
---|
30 | </p>
|
---|
31 | <p>
|
---|
32 | For legacy guest OSes, a VGA-compatible graphics device is
|
---|
33 | available.
|
---|
34 | </p>
|
---|
35 | </li>
|
---|
36 | <li>
|
---|
37 | <p><b outputclass="bold">Storage.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/>
|
---|
38 | emulates the most common types of hard disk controllers. See
|
---|
39 | <xref href="harddiskcontrollers.dita#harddiskcontrollers"/>. Whereas supporting
|
---|
40 | only one of these controllers would be enough for
|
---|
41 | <ph conkeyref="vbox-conkeyref-phrases/product-name"/> by itself, this multitude of storage adapters
|
---|
42 | is required for compatibility with other hypervisors. Windows
|
---|
43 | is very selective about its boot devices, and migrating VMs
|
---|
44 | between hypervisors is very difficult or impossible if the
|
---|
45 | storage controllers are different.
|
---|
46 | </p>
|
---|
47 | </li>
|
---|
48 | <li>
|
---|
49 | <p><b outputclass="bold">Networking.</b> See
|
---|
50 | <xref href="nichardware.dita#nichardware"/>.
|
---|
51 | </p>
|
---|
52 | </li>
|
---|
53 | <li>
|
---|
54 | <p><b outputclass="bold">USB.</b> <ph conkeyref="vbox-conkeyref-phrases/product-name"/> emulates
|
---|
55 | these types of USB host controllers: xHCI, EHCI, and OHCI.
|
---|
56 | While xHCI handles all USB transfer speeds, some legacy guest
|
---|
57 | OSes may not support xHCI. Note that for some legacy Windows
|
---|
58 | guests, third party drivers must be installed for xHCI
|
---|
59 | support.
|
---|
60 | </p>
|
---|
61 | <p>
|
---|
62 | Legacy guest OSes typically support OHCI and EHCI. These two
|
---|
63 | controllers are needed because OHCI only handles USB low-speed
|
---|
64 | and full-speed devices (both USB 1.x and 2.0), while EHCI only
|
---|
65 | handles high-speed devices (USB 2.0 only).
|
---|
66 | </p>
|
---|
67 | <p>
|
---|
68 | The emulated USB controllers do not communicate directly with
|
---|
69 | devices on the host. Instead they communicate with a virtual
|
---|
70 | USB layer which abstracts the USB protocol and enables the use
|
---|
71 | of remote USB devices.
|
---|
72 | </p>
|
---|
73 | </li>
|
---|
74 | <li>
|
---|
75 | <p><b outputclass="bold">Audio.</b> See
|
---|
76 | <xref href="settings-audio.dita#settings-audio"/>.
|
---|
77 | </p>
|
---|
78 | </li>
|
---|
79 | </ul>
|
---|
80 | </body>
|
---|
81 |
|
---|
82 | </topic>
|
---|