Changeset 40467 in vbox for trunk/doc/manual
- Timestamp:
- Mar 14, 2012 3:53:52 PM (13 years ago)
- svn:sync-xref-src-repo-rev:
- 76834
- Location:
- trunk/doc/manual/en_US
- Files:
-
- 2 edited
-
user_BasicConcepts.xml (modified) (6 diffs)
-
user_KnownIssues.xml (modified) (1 diff)
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_BasicConcepts.xml
r40461 r40467 127 127 128 128 <glossentry> 129 <glossterm>Mac OS X Server</glossterm>129 <glossterm>Mac OS X</glossterm> 130 130 131 131 <glossdef> 132 132 <para>VirtualBox 3.2 added experimental support for Mac OS X 133 Server guests, but this comes with restrictions. Please see the 134 following section as well as <xref 135 linkend="KnownIssues" />.</para> 133 guests, but this comes with restrictions. Please see the following 134 section as well as <xref linkend="KnownIssues" />.</para> 136 135 </glossdef> 137 136 </glossentry> … … 139 138 140 139 <sect2 id="intro-macosxguests"> 141 <title>Mac OS X Serverguests</title>140 <title>Mac OS X guests</title> 142 141 143 142 <para>Starting with version 3.2, VirtualBox has experimental support for 144 Mac OS X Server guests. This allows you to install and execute 145 unmodified versions of Mac OS X Server on supported host 146 hardware.</para> 143 Mac OS X guests. This allows you to install and execute unmodified 144 versions of Mac OS X on supported host hardware.</para> 147 145 148 146 <para>Whereas competing solutions perform modifications to the Mac OS X 149 Server install DVDs (e.g. different boot loader and replaced files),150 VirtualBox is the first product to provide the modern PC architecture151 expected byOS X without requiring any "hacks".</para>147 install DVDs (e.g. different boot loader and replaced files), VirtualBox 148 is the first product to provide the modern PC architecture expected by 149 OS X without requiring any "hacks".</para> 152 150 153 151 <para>You should be aware of a number of <emphasis role="bold">important 154 issues</emphasis> before attempting to install a Mac OS X Server 155 guest:<orderedlist> 152 issues</emphasis> before attempting to install a Mac OS X guest:<orderedlist> 156 153 <listitem> 157 154 <para>Mac OS X is commercial, licensed software and contains 158 <emphasis role="bold">both license and technical 159 restrictions</emphasis> that limit its use to certain hardware and 160 usage scenarios. It is important that you understand and obey 161 these restrictions.</para> 162 163 <para>In particular, for most versions of Mac OS X Server, Apple 164 prohibits installing them on non-Apple hardware. Also, only the 165 server versions of Mac OS X are designed to be used in a virtual 166 environment; as a result, VirtualBox does not support client 167 versions of Mac OS X as a guest.</para> 155 <emphasis role="bold">both license and technical restrictions</emphasis> 156 that limit its use to certain hardware and usage scenarios. It is 157 important that you understand and obey these restrictions.</para> 158 159 <para>In particular, for most versions of Mac OS X, Apple prohibits 160 installing them on non-Apple hardware.</para> 168 161 169 162 <para>These license restrictions are also enforced on a technical 170 level. Mac OS X Server verifies whether it is running on Apple 171 hardware, and most DVDs that that come with Apple hardware even 172 check for an exact model. These restrictions are 173 <emphasis>not</emphasis> circumvented by VirtualBox and continue 174 to apply.</para> 163 level. Mac OS X verifies whether it is running on Apple hardware, 164 and most DVDs that that come with Apple hardware even check for an 165 exact model. These restrictions are <emphasis>not</emphasis> 166 circumvented by VirtualBox and continue to apply.</para> 175 167 </listitem> 176 168 … … 178 170 <para>Only <emphasis role="bold">CPUs</emphasis> known and tested 179 171 by Apple are supported. As a result, if your Intel CPU is newer 180 than the build of Mac OS X Server, or if you have a non-Intel CPU,181 it willmost likely panic during bootup with an "Unsupported CPU"182 exception. It is generally best to use the Mac OS X Server DVD183 that camewith your Apple hardware.</para>172 than the build of Mac OS X, or if you have a non-Intel CPU, it will 173 most likely panic during bootup with an "Unsupported CPU" 174 exception. It is generally best to use the Mac OS X DVD that came 175 with your Apple hardware.</para> 184 176 </listitem> 185 177 186 178 <listitem> 187 <para>The Mac OS X Serverinstaller expects the harddisk to be179 <para>The Mac OS X installer expects the harddisk to be 188 180 <emphasis role="bold">partitioned</emphasis> so when it does not 189 181 offer a selection, you have to launch the Disk Utility from the … … 193 185 194 186 <listitem> 195 <para>In addition, as Mac OS X Server support in VirtualBox is 196 currently still experimental, please refer also to <xref 197 linkend="KnownIssues" />.</para> 187 <para>In addition, as Mac OS X support in VirtualBox is currently 188 still experimental, please refer also to <xref linkend="KnownIssues" />.</para> 198 189 </listitem> 199 190 </orderedlist></para> … … 498 489 virtual machine. Before VirtualBox 4.0, PIIX3 was the only 499 490 available option here. For modern guest operating systems such 500 as Mac OS X server, that old chipset is no longer well501 supported. As a result, VirtualBox 4.0 introduced an emulation502 of the more modern ICH9 chipset, which supports PCI express,503 three PCI buses, PCI-to-PCI bridges and Message Signalled504 Interrupts (MSI). This allows modern operating systems to505 address more PCI devices and no longer requires IRQ sharing.506 Note that the ICH9 support is experimental and not recommended 507 for guest operatingsystems which do not require it.</para>491 as Mac OS X, that old chipset is no longer well supported. As a 492 result, VirtualBox 4.0 introduced an emulation of the more 493 modern ICH9 chipset, which supports PCI express, three PCI 494 buses, PCI-to-PCI bridges and Message Signalled Interrupts 495 (MSI). This allows modern operating systems to address more PCI 496 devices and no longer requires IRQ sharing. Note that the ICH9 497 support is experimental and not recommended for guest operating 498 systems which do not require it.</para> 508 499 </glossdef> 509 500 </glossentry> … … 1314 1305 line interface like this: <screen>VBoxManage modifyvm "VM name" --firmware efi</screen> 1315 1306 To switch back to using the BIOS, use: <screen>VBoxManage modifyvm "VM name" --firmware bios</screen>One 1316 notable user of EFI is Apple's Mac OS X, but recent Linuxes (such as 1317 Fedora 11) and Windows (starting with Vista) offer special versions that can1318 b e booted using EFI as well.</para>1307 notable user of EFI is Apple's Mac OS X, but recent Linuxes (such as Fedora 1308 11) and Windows (starting with Vista) offer special versions that can be 1309 booted using EFI as well.</para> 1319 1310 1320 1311 <para>Another possible use of EFI in VirtualBox is development and testing -
trunk/doc/manual/en_US/user_KnownIssues.xml
r39331 r40467 176 176 177 177 <listitem> 178 <para><emphasis role="bold">Mac OS X Serverguests:</emphasis>178 <para><emphasis role="bold">Mac OS X guests:</emphasis> 179 179 <itemizedlist> 180 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> 181 <para>Mac OS X guests can only run on a certain host hardware. 182 For details about license and host hardware limitations, please 183 see <xref linkend="intro-macosxguests" /> and check the Apple 184 software license conditions.</para> 184 185 </listitem> 185 186 186 187 <listitem> 187 188 <para>VirtualBox does not provide Guest Additions for Mac OS X 188 Serverat this time.</para>189 at this time.</para> 189 190 </listitem> 190 191 191 192 <listitem> 192 193 <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 to194 Mac OS X falls back to the built-in EFI display support. See 195 <xref linkend="efividmode" /> for more information on how to 195 196 change EFI video modes.</para> 196 197 </listitem> 197 198 198 199 <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 a200 <para>Even when idle, Mac OS X guests currently burn 100% CPU. 201 This is a power management issue that will be addressed in a 201 202 future release.</para> 202 203 </listitem> 203 204 204 205 <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> 206 <para>Mac OS X guests only work with one CPU assigned to the 207 VM. Support for SMP will be provided in a future release.</para> 208 </listitem> 209 210 <listitem> 211 <para>Depending on your system and version of Mac OS X, you 212 might experience guest hangs after some time. This can be fixed 213 by turning off energy saving (set timeout to "Never") in the 214 system preferences.</para> 215 215 </listitem> 216 216 217 217 <listitem> 218 218 <para>By default, the VirtualBox EFI enables debug output of the 219 Mac OS X Server kernel to help you diagnose boot problems. Note220 th at there is a lot of output and not all errors are fatal (they219 Mac OS X kernel to help you diagnose boot problems. Note that 220 there is a lot of output and not all errors are fatal (they 221 221 would also show on your physical Mac). You can turn off these 222 222 messages by issuing this command:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" " "</screen>To
Note:
See TracChangeset
for help on using the changeset viewer.
