- Timestamp:
- Nov 16, 2011 1:06:31 PM (13 years ago)
- Location:
- trunk/doc/manual/en_US
- Files:
-
- 4 edited
-
user_AdvancedTopics.xml (modified) (4 diffs)
-
user_BasicConcepts.xml (modified) (1 diff)
-
user_KnownIssues.xml (modified) (1 diff)
-
user_Storage.xml (modified) (7 diffs)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_AdvancedTopics.xml
r39020 r39331 809 809 performance difference for image files vs. raw disk varies greatly 810 810 depending on the overhead of the host file system, whether dynamically 811 growing images are used and on host OS caching strategies. The caching811 growing images are used, and on host OS caching strategies. The caching 812 812 indirectly also affects other aspects such as failure behavior, i.e. 813 813 whether the virtual disk contains all data written before a host OS … … 828 828 defines where the data will be stored. After creating such a special 829 829 VMDK image, you can use it like a regular virtual disk image. For 830 example, you can use the Virtual MediaManager (<xref linkend="vdis" />)830 example, you can use the VirtualBox Manager (<xref linkend="vdis" />) 831 831 or <computeroutput>VBoxManage</computeroutput> to assign the image to a 832 832 virtual machine.</para> … … 859 859 <para>Creating the image requires read/write access for the given 860 860 device. Read/write access is also later needed when using the image 861 from a virtual machine.</para> 861 from a virtual machine. On some host platforms (e.g. Windows Vista 862 and later), raw disk access may be restricted and not permitted by 863 the host OS in some situations.</para> 862 864 863 865 <para>Just like with regular disk images, this does not automatically … … 977 979 "VBoxInternal/Devices/piix3ide/0/Config/PrimaryMaster/ModelNumber" "model"</screen> 978 980 979 <para>For hard disks it's also possible (experimental!)to mark the981 <para>For hard disks it's also possible to mark the 980 982 drive as having a non-rotational medium with:</para> 981 983 -
trunk/doc/manual/en_US/user_BasicConcepts.xml
r38047 r39331 502 502 three PCI buses, PCI-to-PCI bridges and Message Signalled 503 503 Interrupts (MSI). This allows modern operating systems to 504 address more PCI devices and no longer requires IRQ 505 sharing.</para> 504 address more PCI devices and no longer requires IRQ sharing. 505 Note that the ICH9 support is experimental and not recommended 506 for guest operating systems which do not require it.</para> 506 507 </glossdef> 507 508 </glossentry> -
trunk/doc/manual/en_US/user_KnownIssues.xml
r39177 r39331 4 4 <chapter id="KnownIssues"> 5 5 <title>Known limitations</title> 6 7 <para>This sections describes known problems with VirtualBox 8 $VBOX_VERSION_STRING. Unless marked otherwise, these issues are planned to 9 be fixed in later releases.</para> 10 11 <itemizedlist> 12 <listitem> 13 <para>The following <emphasis role="bold">Guest SMP (multiprocessor) 14 limitations</emphasis> exist:<itemizedlist> 15 <listitem> 16 <para><emphasis role="bold">Poor performance</emphasis> with 17 32-bit guests on AMD CPUs. This affects mainly Windows and Solaris 18 guests, but possibly also some Linux kernel revisions. Partially 19 solved in 3.0.6 for 32 bits Windows NT, 2000, XP and 2003 guests. 20 Requires 3.0.6 or higher Guest Additions to be installed.</para> 21 </listitem> 22 23 <listitem> 24 <para><emphasis role="bold">Poor performance</emphasis> with 25 32-bit guests on certain Intel CPU models that do not include 26 virtual APIC hardware optimization support. This affects mainly 27 Windows and Solaris guests, but possibly also some Linux kernel 28 revisions. Partially solved in 3.0.12 for 32 bits Windows NT, 29 2000, XP and 2003 guests. Requires 3.0.12 or higher Guest 30 Additions to be installed.</para> 31 </listitem> 32 </itemizedlist></para> 33 </listitem> 34 35 <listitem> 36 <para><emphasis role="bold">64-bit guests on some 32-bit host systems 37 with VT-x</emphasis> can cause instabilities to your system. If you 38 experience this, do not attempt to execute 64-bit guests. Refer to the 39 VirtualBox user forum for additional information.</para> 40 </listitem> 41 42 <listitem> 43 <para>For <emphasis role="bold">basic Direct3D support in Windows 44 guests</emphasis> to work, the Guest Additions must be installed in 45 Windows "safe mode". Press F8 when the Windows guest is booting and 46 select "Safe mode", then install the Guest Additions. Otherwise Windows' 47 file protection mechanism will interfere with the replacement DLLs 48 installed by VirtualBox and keep restoring the original Windows system 49 DLLs. <note> 50 <para>This does <emphasis role="bold">not</emphasis> apply to the 51 experimental WDDM Direct3D video 52 driver available for Vista and Windows 7 guests shipped with 53 VirtualBox 4.1.</para> 54 </note></para> 55 </listitem> 56 57 <listitem> 58 <para><emphasis role="bold">Guest control.</emphasis> On Windows guests, 59 a process lauched via the guest control execute support will not be able 60 to display a graphical user interface <emphasis>unless</emphasis> the 61 user account under which it is running is currently logged in and has a 62 desktop session.</para> 63 64 <para>Also, to use accounts without or with an empty password, the 65 guest's group policy must be changed. To do so, open the group policy 66 editor on the command line by typing 67 <computeroutput>gpedit.msc</computeroutput>, open the key 68 <emphasis>Computer Configuration\Windows Settings\Security 69 Settings\Local Policies\Security Options</emphasis> and change the value 70 of <emphasis>Accounts: Limit local account use of blank passwords to 71 console logon only</emphasis> to <emphasis>Disabled</emphasis>.</para> 72 </listitem> 73 74 <listitem> 75 <para><emphasis role="bold">Compacting virtual disk images is limited to 76 VDI files.</emphasis> The <code>VBoxManage modifyhd --compact</code> 77 command is currently only implemented for VDI files. At the moment the 78 only way to optimize the size of a virtual disk images in other formats 79 (VMDK, VHD) is to clone the image and then use the cloned image in the 80 VM configuration.</para> 81 </listitem> 82 83 <listitem> 84 <para><emphasis role="bold">OVF import/export:</emphasis><itemizedlist> 85 <listitem> 86 <para>OVF localization (multiple languages in one OVF file) is not 87 yet supported.</para> 88 </listitem> 89 90 <listitem> 91 <para>Some OVF sections like StartupSection, 92 DeploymentOptionSection and InstallSection are ignored.</para> 93 </listitem> 94 95 <listitem> 96 <para>OVF environment documents, including their property sections 97 and appliance configuration with ISO images, are not yet 98 supported.</para> 99 </listitem> 100 101 <listitem> 102 <para>Remote files via HTTP or other mechanisms are not yet 103 supported.</para> 104 </listitem> 105 </itemizedlist></para> 106 </listitem> 107 108 <listitem> 109 <para>Neither <emphasis role="bold">scale mode</emphasis> nor <emphasis 110 role="bold">seamless mode</emphasis> work correctly with guests using 111 OpenGL 3D features (such as with compiz-enabled window managers).</para> 112 </listitem> 113 114 <listitem> 115 <para>Preserving the aspect ratio in scale mode works only on Windows 116 hosts and on Mac OS X hosts.</para> 117 </listitem> 118 119 <listitem> 120 <para>On <emphasis role="bold">Mac OS X hosts,</emphasis> the following 121 features are not yet implemented:</para> 122 123 <para><itemizedlist> 124 <listitem> 125 <para>Numlock emulation</para> 126 </listitem> 127 128 <listitem> 129 <para>CPU frequency metric</para> 130 </listitem> 131 132 <listitem> 133 <para>Memory ballooning</para> 134 </listitem> 135 </itemizedlist></para> 136 </listitem> 137 138 <listitem> 139 <para><emphasis role="bold">Mac OS X Server guests:</emphasis> 6 <sect1 id="ExperimentalFeatures"> 7 <title>Experimental Features</title> 8 <para>Some VirtualBox features are labeled as experimental. Such 9 features are provided on an "as-is" basis and are not formally 10 supported. However, feedback and suggestions about such features are 11 welcome. A comprehensive list of experimental features follows:</para> 12 <itemizedlist> 13 <listitem> 14 WDDM Direct3D video driver for Windows guests 15 </listitem> 16 <listitem> 17 Hardware 3D acceleration support for Windows, Linux, and Solaris 18 guests 19 </listitem> 20 <listitem> 21 Hardware 2D video playback acceleration support for Windows 22 guests 23 </listitem> 24 <listitem> 25 PCI pass-through (Linux hosts only) 26 </listitem> 27 <listitem> 28 Mac OS X guests (Mac hosts only) 29 </listitem> 30 <listitem> 31 ICH9 chipset emulation 32 </listitem> 33 <listitem> 34 EFI firmware 35 </listitem> 36 <listitem> 37 Host CD/DVD drive pass-through 38 </listitem> 39 <listitem> 40 Support of iSCSI via internal networking 41 </listitem> 42 </itemizedlist> 43 </sect1> 44 <sect1 id="KnownProblems"> 45 <title>Known Issues</title> 46 <para>The following section describes known problems with VirtualBox 47 $VBOX_VERSION_STRING. Unless marked otherwise, these issues are planned to 48 be fixed in later releases.</para> 49 140 50 <itemizedlist> 141 <listitem> 142 <para>Mac OS X Server guests can only run on a certain host 143 hardware. For details about license and host hardware limitations, 144 please see <xref linkend="intro-macosxguests" />.</para> 145 </listitem> 146 147 <listitem> 148 <para>VirtualBox does not provide Guest Additions for Mac OS X 149 Server at this time.</para> 150 </listitem> 151 152 <listitem> 153 <para>The graphics resolution currently defaults to 1024x768 as 154 Mac OS X Server falls back to the built-in EFI display support. 155 See <xref linkend="efividmode" /> for more information on how to 156 change EFI video modes.</para> 157 </listitem> 158 159 <listitem> 160 <para>Even when idle, Mac OS X Server guests currently burn 100% 161 CPU. This is a power management issue that will be addressed in a 162 future release.</para> 163 </listitem> 164 165 <listitem> 166 <para>Mac OS X Server guests only work with one CPU assigned to 167 the VM. Support for SMP will be provided in a future 168 release.</para> 169 </listitem> 170 171 <listitem> 172 <para>Depending on your system and version of Mac OS X Server, you 173 might experience guest hangs after some time. This can be fixed by 174 turning off energy saving (set timeout to "Never") in the system 175 preferences.</para> 176 </listitem> 177 178 <listitem> 179 <para>By default, the VirtualBox EFI enables debug output of the 180 Mac OS X Server kernel to help you diagnose boot problems. Note 181 that there is a lot of output and not all errors are fatal (they 182 would also show on your physical Mac). You can turn off these 183 messages by issuing this command:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" " "</screen>To 184 revert to the previous behavior, use:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" ""</screen></para> 185 </listitem> 186 </itemizedlist></para> 187 </listitem> 188 189 <listitem> 190 <para><emphasis role="bold">Solaris hosts:</emphasis> <itemizedlist> 191 <listitem> 192 <para>There is no support for USB devices connected to Solaris 10 193 hosts.</para> 194 </listitem> 195 196 <listitem> 197 <para>USB support on Solaris hosts requires Solaris 11 version 198 snv_124 or higher. Webcams and other isochronous devices are known 199 to have poor performance.</para> 200 </listitem> 201 202 <listitem> 203 <para>No ACPI information (battery status, power source) is 204 reported to the guest.</para> 205 </listitem> 206 207 <listitem> 208 <para>No support for using wireless adapters with bridged 209 networking.</para> 210 </listitem> 211 212 <listitem> 213 <para>Crossbow based bridged networking on Solaris 11 hosts does 214 not work directly with aggregate links. However, you can manually 215 create a VNIC (using <computeroutput>dladm</computeroutput>) over 216 the aggregate link and use that with a VM. This technical 217 limitation between VirtualBox and Solaris will be addressed in a 218 future release.</para> 219 </listitem> 220 </itemizedlist></para> 221 </listitem> 222 223 <listitem> 224 <para><emphasis role="bold">Guest Additions of version 4.1, 4.1.2 and 4.1.4 for Windows</emphasis> 225 Thus VirtualBox WDDM Video driver may be installed and kept in guest system 226 if Guest additions uninstallation is performed. 227 This is caused by a bug in Guest Additions uninstaller. 228 <note> 229 <para>This does <emphasis role="bold">not</emphasis> apply to Guest Additions update, 230 i.e. installing a one version of Guest Additions on top of another works correctly.</para> 231 </note> 232 To solve this problem, one should uninstall the VirtualBox WDDM Video driver manually. 233 To do that open Device Manager, and check whether the Display Adapter is named 234 "VirtualBox Graphics Adapter ..". If no - there is nothing to be done. If yes - right-clik 235 the VirtualBox Graphics Adapter in Device Manager, select "Uninstall", check "Delete the driver software for this device" 236 and click "OK". Once uninstallation is done - in Device Manager go to menu "Action" and select 237 "Scan for hardware changes" to make the propper (Windows default) driver be picked up for the Graphics adapter. 238 </para> 239 </listitem> 240 241 <listitem> 242 <para><emphasis role="bold">Guest Additions for OS/2.</emphasis> Shared 243 folders are not yet supported with OS/2 guests. In addition, seamless 244 windows and automatic guest resizing will probably never be implemented 245 due to inherent limitations of the OS/2 graphics system.</para> 246 </listitem> 247 </itemizedlist> 51 <listitem> 52 <para>The following <emphasis role="bold">Guest SMP (multiprocessor) 53 limitations</emphasis> exist:<itemizedlist> 54 <listitem> 55 <para><emphasis role="bold">Poor performance</emphasis> with 56 32-bit guests on AMD CPUs. This affects mainly Windows and Solaris 57 guests, but possibly also some Linux kernel revisions. Partially 58 solved in 3.0.6 for 32 bits Windows NT, 2000, XP and 2003 guests. 59 Requires 3.0.6 or higher Guest Additions to be installed.</para> 60 </listitem> 61 62 <listitem> 63 <para><emphasis role="bold">Poor performance</emphasis> with 64 32-bit guests on certain Intel CPU models that do not include 65 virtual APIC hardware optimization support. This affects mainly 66 Windows and Solaris guests, but possibly also some Linux kernel 67 revisions. Partially solved in 3.0.12 for 32 bits Windows NT, 68 2000, XP and 2003 guests. Requires 3.0.12 or higher Guest 69 Additions to be installed.</para> 70 </listitem> 71 </itemizedlist></para> 72 </listitem> 73 74 <listitem> 75 <para><emphasis role="bold">64-bit guests on some 32-bit host systems 76 with VT-x</emphasis> can cause instabilities to your system. If you 77 experience this, do not attempt to execute 64-bit guests. Refer to the 78 VirtualBox user forum for additional information.</para> 79 </listitem> 80 81 <listitem> 82 <para>For <emphasis role="bold">basic Direct3D support in Windows 83 guests</emphasis> to work, the Guest Additions must be installed in 84 Windows "safe mode". Press F8 when the Windows guest is booting and 85 select "Safe mode", then install the Guest Additions. Otherwise Windows' 86 file protection mechanism will interfere with the replacement DLLs 87 installed by VirtualBox and keep restoring the original Windows system 88 DLLs. <note> 89 <para>This does <emphasis role="bold">not</emphasis> apply to the 90 experimental WDDM Direct3D video 91 driver available for Vista and Windows 7 guests shipped with 92 VirtualBox 4.1.</para> 93 </note></para> 94 </listitem> 95 96 <listitem> 97 <para><emphasis role="bold">Guest control.</emphasis> On Windows guests, 98 a process lauched via the guest control execute support will not be able 99 to display a graphical user interface <emphasis>unless</emphasis> the 100 user account under which it is running is currently logged in and has a 101 desktop session.</para> 102 103 <para>Also, to use accounts without or with an empty password, the 104 guest's group policy must be changed. To do so, open the group policy 105 editor on the command line by typing 106 <computeroutput>gpedit.msc</computeroutput>, open the key 107 <emphasis>Computer Configuration\Windows Settings\Security 108 Settings\Local Policies\Security Options</emphasis> and change the value 109 of <emphasis>Accounts: Limit local account use of blank passwords to 110 console logon only</emphasis> to <emphasis>Disabled</emphasis>.</para> 111 </listitem> 112 113 <listitem> 114 <para><emphasis role="bold">Compacting virtual disk images is limited to 115 VDI files.</emphasis> The <code>VBoxManage modifyhd --compact</code> 116 command is currently only implemented for VDI files. At the moment the 117 only way to optimize the size of a virtual disk images in other formats 118 (VMDK, VHD) is to clone the image and then use the cloned image in the 119 VM configuration.</para> 120 </listitem> 121 122 <listitem> 123 <para><emphasis role="bold">OVF import/export:</emphasis><itemizedlist> 124 <listitem> 125 <para>OVF localization (multiple languages in one OVF file) is not 126 yet supported.</para> 127 </listitem> 128 129 <listitem> 130 <para>Some OVF sections like StartupSection, 131 DeploymentOptionSection and InstallSection are ignored.</para> 132 </listitem> 133 134 <listitem> 135 <para>OVF environment documents, including their property sections 136 and appliance configuration with ISO images, are not yet 137 supported.</para> 138 </listitem> 139 140 <listitem> 141 <para>Remote files via HTTP or other mechanisms are not yet 142 supported.</para> 143 </listitem> 144 </itemizedlist></para> 145 </listitem> 146 147 <listitem> 148 <para>Neither <emphasis role="bold">scale mode</emphasis> nor <emphasis 149 role="bold">seamless mode</emphasis> work correctly with guests using 150 OpenGL 3D features (such as with compiz-enabled window managers).</para> 151 </listitem> 152 153 <listitem> 154 <para>Preserving the aspect ratio in scale mode works only on Windows 155 hosts and on Mac OS X hosts.</para> 156 </listitem> 157 158 <listitem> 159 <para>On <emphasis role="bold">Mac OS X hosts,</emphasis> the following 160 features are not yet implemented:</para> 161 162 <para><itemizedlist> 163 <listitem> 164 <para>Numlock emulation</para> 165 </listitem> 166 167 <listitem> 168 <para>CPU frequency metric</para> 169 </listitem> 170 171 <listitem> 172 <para>Memory ballooning</para> 173 </listitem> 174 </itemizedlist></para> 175 </listitem> 176 177 <listitem> 178 <para><emphasis role="bold">Mac OS X Server guests:</emphasis> 179 <itemizedlist> 180 <listitem> 181 <para>Mac OS X Server guests can only run on a certain host 182 hardware. For details about license and host hardware limitations, 183 please see <xref linkend="intro-macosxguests" />.</para> 184 </listitem> 185 186 <listitem> 187 <para>VirtualBox does not provide Guest Additions for Mac OS X 188 Server at this time.</para> 189 </listitem> 190 191 <listitem> 192 <para>The graphics resolution currently defaults to 1024x768 as 193 Mac OS X Server falls back to the built-in EFI display support. 194 See <xref linkend="efividmode" /> for more information on how to 195 change EFI video modes.</para> 196 </listitem> 197 198 <listitem> 199 <para>Even when idle, Mac OS X Server guests currently burn 100% 200 CPU. This is a power management issue that will be addressed in a 201 future release.</para> 202 </listitem> 203 204 <listitem> 205 <para>Mac OS X Server guests only work with one CPU assigned to 206 the VM. Support for SMP will be provided in a future 207 release.</para> 208 </listitem> 209 210 <listitem> 211 <para>Depending on your system and version of Mac OS X Server, you 212 might experience guest hangs after some time. This can be fixed by 213 turning off energy saving (set timeout to "Never") in the system 214 preferences.</para> 215 </listitem> 216 217 <listitem> 218 <para>By default, the VirtualBox EFI enables debug output of the 219 Mac OS X Server kernel to help you diagnose boot problems. Note 220 that there is a lot of output and not all errors are fatal (they 221 would also show on your physical Mac). You can turn off these 222 messages by issuing this command:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" " "</screen>To 223 revert to the previous behavior, use:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" ""</screen></para> 224 </listitem> 225 </itemizedlist></para> 226 </listitem> 227 228 <listitem> 229 <para><emphasis role="bold">Solaris hosts:</emphasis> <itemizedlist> 230 <listitem> 231 <para>There is no support for USB devices connected to Solaris 10 232 hosts.</para> 233 </listitem> 234 235 <listitem> 236 <para>USB support on Solaris hosts requires Solaris 11 version 237 snv_124 or higher. Webcams and other isochronous devices are known 238 to have poor performance.</para> 239 </listitem> 240 241 <listitem> 242 <para>No ACPI information (battery status, power source) is 243 reported to the guest.</para> 244 </listitem> 245 246 <listitem> 247 <para>No support for using wireless adapters with bridged 248 networking.</para> 249 </listitem> 250 251 <listitem> 252 <para>Crossbow based bridged networking on Solaris 11 hosts does 253 not work directly with aggregate links. However, you can manually 254 create a VNIC (using <computeroutput>dladm</computeroutput>) over 255 the aggregate link and use that with a VM. This technical 256 limitation between VirtualBox and Solaris will be addressed in a 257 future release.</para> 258 </listitem> 259 </itemizedlist></para> 260 </listitem> 261 262 <listitem> 263 <para><emphasis role="bold">Guest Additions of version 4.1, 4.1.2 and 4.1.4 for Windows</emphasis> 264 Thus VirtualBox WDDM Video driver may be installed and kept in guest system 265 if Guest additions uninstallation is performed. 266 This is caused by a bug in Guest Additions uninstaller. 267 <note> 268 <para>This does <emphasis role="bold">not</emphasis> apply to Guest Additions update, 269 i.e. installing a one version of Guest Additions on top of another works correctly.</para> 270 </note> 271 To solve this problem, one should uninstall the VirtualBox WDDM Video driver manually. 272 To do that open Device Manager, and check whether the Display Adapter is named 273 "VirtualBox Graphics Adapter ..". If no - there is nothing to be done. If yes - right-clik 274 the VirtualBox Graphics Adapter in Device Manager, select "Uninstall", check "Delete the driver software for this device" 275 and click "OK". Once uninstallation is done - in Device Manager go to menu "Action" and select 276 "Scan for hardware changes" to make the propper (Windows default) driver be picked up for the Graphics adapter. 277 </para> 278 </listitem> 279 280 <listitem> 281 <para><emphasis role="bold">Guest Additions for OS/2.</emphasis> Shared 282 folders are not yet supported with OS/2 guests. In addition, seamless 283 windows and automatic guest resizing will probably never be implemented 284 due to inherent limitations of the OS/2 graphics system.</para> 285 </listitem> 286 </itemizedlist> 287 </sect1> 248 288 </chapter> -
trunk/doc/manual/en_US/user_Storage.xml
r38503 r39331 24 24 25 25 <listitem> 26 <para>Finally, as an experimentalfeature, you can allow a virtual26 <para>Finally, as an advanced feature, you can allow a virtual 27 27 machine to access one of your host disks directly; this advanced feature 28 28 is described in <xref linkend="rawdisk" />.</para> … … 50 50 </footnote><itemizedlist> 51 51 <listitem> 52 <para><emphasis role="bold">IDE (ATA)</emphasis> controllers have 53 been in use since the 1980s. Initially, this type of interface 52 <para><emphasis role="bold">IDE (ATA)</emphasis> controllers are a 53 backwards compatible yet very advanced extension of the disk 54 controller in the IBM PC/AT (1984). Initially, this interface 54 55 worked only with hard disks, but was later extended to also support 55 56 CD-ROM drives and other types of removable media. In physical PCs, 56 57 this standard uses flat ribbon parallel cables with 40 or 80 wires. 57 58 Each such cable can connect two devices to a controller, which have 58 traditionally been called "master" and "slave". Typical hard disk59 controllers have two connectors for such cables; as a result, most60 PCs support up to four devices.</para>61 62 <para>In VirtualBox, each virtual machine has one IDE controller63 enabled by default, which gives you up to four virtual storage59 traditionally been called "master" and "slave". Typical PCs had 60 two connectors for such cables; as a result, support for up to four 61 IDE devices was most common.</para> 62 63 <para>In VirtualBox, each virtual machine may have one IDE 64 contoller enabled, which gives you up to four virtual storage 64 65 devices that you can attach to the machine. (By default, one of 65 66 these four -- the secondary master -- is preconfigured to be the … … 72 73 73 74 <para>So even if your guest operating system has no support for SCSI 74 or SATA devices, it should always be able to see the default IDE75 controller that is enabled by default.</para>75 or SATA devices, it should always be able to see an IDE controller. 76 </para> 76 77 77 78 <para>You can also select which exact type of IDE controller … … 80 81 but if you import a virtual machine from another virtualization 81 82 product, the operating system in that machine may expect a 82 particular controller and crash if it isn't found.</para>83 particular controller type and crash if it isn't found.</para> 83 84 84 85 <para>After you have created a new virtual machine with the "New … … 92 93 <para><emphasis role="bold">Serial ATA (SATA)</emphasis> is a newer 93 94 standard introduced in 2003. Compared to IDE, it supports both much 94 higher speeds and more devices per hard diskcontroller. Also, with95 higher speeds and more devices per controller. Also, with 95 96 physical hardware, devices can be added and removed while the system 96 97 is running. The standard interface for SATA controllers is called … … 124 125 AHCI. In particular, <emphasis role="bold">there is no support 125 126 for AHCI in Windows before Windows Vista</emphasis>, so Windows 126 XP (even SP 2) will not see such disks unless you install127 XP (even SP3) will not see such disks unless you install 127 128 additional drivers. It is possible to switch from IDE to SATA 128 129 after installation by installing the SATA drivers and changing … … 195 196 operating systems with device support for it. In particular, 196 197 <emphasis role="bold">there is no support for SAS in Windows 197 before Windows Vista</emphasis>, so Windows XP (even SP 2) will not198 before Windows Vista</emphasis>, so Windows XP (even SP3) will not 198 199 see such disks unless you install additional drivers.</para> 199 200 </warning>
Note:
See TracChangeset
for help on using the changeset viewer.
