Changeset 35174 in vbox
- Timestamp:
- Dec 16, 2010 12:30:08 PM (14 years ago)
- Location:
- trunk/doc/manual/en_US
- Files:
-
- 5 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/en_US/user_BasicConcepts.xml
r35065 r35174 353 353 installed in the VM. This is the same setting that was specified 354 354 in the "New Virtual Machine" wizard, as described in <xref 355 linkend="gui-createvm" />. 355 linkend="gui-createvm" />.</para> 356 356 357 357 <para>Whereas the default settings of a newly created VM depend on … … 750 750 <title>Storage settings</title> 751 751 752 <para>In the VM Settings window, the "Storage" section allows you to 753 connect virtual hard disk, CD/DVD and floppy images and drives to your 754 virtual machine:<mediaobject> 752 <para>The "Storage" category in the VM settings allows you to connect 753 virtual hard disk, CD/DVD and floppy images and drives to your virtual 754 machine.</para> 755 756 <para>In a real PC, so-called "storage controllers" connect physical disk 757 drives to the rest of the computer. Similarly, VirtualBox presents virtual 758 storage controllers to a virtual machine. Under each controller, the 759 virtual devices (hard disks, CD/DVD or floppy drives) attached to the 760 controller are shown.<note> 761 <para>This section can only give you a quick introduction to the 762 VirtualBox storage settings. Since VirtualBox gives you an enormous 763 wealth of options in this area, we have dedicated an entire chapter of 764 this User Manual to explaining all the details: please see <xref 765 linkend="storage" />.</para> 766 </note></para> 767 768 <para>If you have used the "Create VM" wizard to create a machine, you 769 will normally see something like the following:</para> 770 771 <para><mediaobject> 755 772 <imageobject> 756 773 <imagedata align="center" fileref="images/vm-settings-harddisk.png" … … 759 776 </mediaobject></para> 760 777 761 <para>In a real PC, so-called "storage controllers" connect physical disk 762 drives to the rest of the computer. Similarly, VirtualBox presents virtual 763 storage controllers to a virtual machine. Under each controller, the 764 virtual devices (hard disks, CD/DVD or floppy drives) are shown that are 765 attached to the controller.</para> 766 767 <para>If you have used the "Create VM" wizard to create a machine, you 768 will normally see the following devices:<itemizedlist> 769 <listitem> 770 <para>You will see an IDE controller, under which there are two 771 devices:<itemizedlist> 772 <listitem> 773 <para>one virtual hard disk connected to the IDE slot called 774 "primary master"; this is represented by the disk images that 775 you created with the machine;</para> 776 </listitem> 777 778 <listitem> 779 <para>one virtual CD/DVD drive connected to the "secondary 780 master".</para> 781 </listitem> 782 </itemizedlist></para> 783 </listitem> 784 785 <listitem> 786 <para>In addition, there is a floppy controller to which a virtual 787 floppy drive is attached.</para> 778 <para>Depending on the guest operating system type that you selected when 779 you created the VM, the typical layout of storage devices in a new VM is 780 as follows:<itemizedlist> 781 <listitem> 782 <para>You will see an <emphasis role="bold">IDE 783 controller,</emphasis> to which a virtual CD/DVD drive has been 784 attached (to the "secondary master" port of the IDE 785 controller).</para> 786 </listitem> 787 788 <listitem> 789 <para>You will also see a <emphasis role="bold">SATA 790 controller,</emphasis> which is a more modern type of storage 791 controller for higher hard disk data throughput, to which the 792 virtual hard disks are attached. Initially you will normally have 793 one such virtual disk, but as you can see in the above screenshot, 794 you can have more than one, each represented by a disk image file 795 (VDI files, in this case).</para> 788 796 </listitem> 789 797 </itemizedlist></para> 798 799 <para>If you created your VM with an older version of VirtualBox, the 800 default storage layout may differ. You might then only have an IDE 801 controller to which both the CD/DVD drive and the hard disks have been 802 attached. This might also apply if you selected an older operating system 803 type when you created the VM. Since older operating systems do not support 804 SATA without additional drivers, VirtualBox will make sure that no such 805 devices are present initially. Please see <xref 806 linkend="harddiskcontrollers" /> for additional information.</para> 807 808 <para>VirtualBox also provides a <emphasis role="bold">floppy 809 controller</emphasis>, which is special: you cannot add devices other than 810 floppy drives to it. Virtual floppy drives, like virtual CD/DVD drives, 811 can be connected to either a host floppy drive (if you have one) or a disk 812 image, which in this case must be in RAW format.</para> 790 813 791 814 <para>You can modify these media attachments freely. For example, if you 792 815 wish to copy some files from another virtual disk that you created, you 793 can connect that disk as a second hard disk. You could also add a second 794 virtual CD/DVD drive, or change where these items are attached.</para> 795 796 <para>In addition to the IDE controller, VirtualBox can also present a 797 SATA controller and a SCSI controller to the guest, which gives you 30 or 798 16 additional slots to attach devices to, respectively. This, however, may 799 require that you run a modern guest operating system. See <xref 800 linkend="harddiskcontrollers" /> for details.</para> 801 802 <para>To <emphasis role="bold">add another virtual hard disk or CD/DVD 803 drive,</emphasis> select the storage controller to which it should be 804 added (IDE, SATA or SCSI) and then click on the "add disk" button below 805 the tree. You can then either select "Add CD/DVD device" or "Add Hard 806 Disk". Alternatively, right-click on the storage controller and select a 807 menu item there.</para> 808 809 <para>On the right part of the window, you can then select to which slot 810 of the controller the virtual disk should be connected to and which image 811 file to use.<itemizedlist> 812 <listitem> 813 <para>For virtual hard disks, a drop-down list appears on the right, 814 listing all the hard disk images that VirtualBox currently knows 815 about.</para> 816 817 <para>The folder icon next to the drop-down allow you to select a 818 different disk image using a standard file dialog.</para> 819 820 <para>The second icon next to the drop-down allows you to create a 821 new disk image; this will bring up the "Create new disk" wizard, 822 which was described in <xref linkend="gui-createvm" />.</para> 823 </listitem> 824 825 <listitem> 826 <para>For virtual CD/DVD drives, there are two kinds of options in 827 the drop-down list.<itemizedlist> 816 can connect that disk as a second hard disk, as in the above screenshot. 817 You could also add a second virtual CD/DVD drive, or change where these 818 items are attached. The following options are available:<itemizedlist> 819 <listitem> 820 <para>To <emphasis role="bold">add another virtual hard disk, or a 821 CD/DVD or floppy drive,</emphasis> select the storage controller to 822 which it should be added (IDE, SATA, SCSI, SAS, floppy controller) 823 and then click on the "add disk" button below the tree. You can then 824 either select "Add CD/DVD device" or "Add Hard Disk". (If you 825 clicked on a floppy controller, you can add a floppy drive instead.) 826 Alternatively, right-click on the storage controller and select a 827 menu item there.</para> 828 829 <para>On the right part of the window, you can then set the 830 following:<orderedlist> 828 831 <listitem> 829 <para>If you select "Empty", then VirtualBox will present a 830 virtual CD/DVD drive to the guest which has no media 831 inserted.</para> 832 <para>You can then select to which <emphasis 833 role="bold">device slot</emphasis> of the controller the 834 virtual disk should be connected to. IDE controllers have four 835 slots which have traditionally been called "primary master", 836 "primary slave", "secondary master" and "secondary slave". By 837 contrast, SATA and SCSI controllers offer you up to 30 slots 838 to which virtual devices can be attached.</para> 832 839 </listitem> 833 840 834 841 <listitem> 835 <para>If you select "Host drive" from the list, then the 836 physical device of the host computer is connected to the VM, 837 so that the guest operating system can read from and write to 838 your physical device. This is, for instance, useful if you 839 want to install Windows from a real installation CD. In this 840 case, select your host drive from the drop-down list 841 presented.</para> 842 843 <para>If you want to write (burn) CDs or DVDs using the host 844 drive, you need to enable the <emphasis 845 role="bold">"Passthrough"</emphasis> option; see <xref 846 linkend="storage-cds" />.</para> 842 <para>You can select which <emphasis role="bold">image 843 file</emphasis> to use.<itemizedlist> 844 <listitem> 845 <para>For virtual hard disks, a button with a drop-down 846 list appears on the right, offering you to either select 847 a <emphasis role="bold">virtual hard disk 848 file</emphasis> using a standard file dialog or to 849 <emphasis role="bold">create a new hard disk</emphasis> 850 (image file), which will bring up the "Create new disk" 851 wizard, which was described in <xref 852 linkend="gui-createvm" />.</para> 853 854 <para>For details on the image file types that are 855 supported, please see <xref 856 linkend="vdidetails" />.</para> 857 </listitem> 858 859 <listitem> 860 <para>For virtual CD/DVD drives, the image files will 861 typically be in the standard ISO format instead. Most 862 commonly, you will select this option when installing an 863 operating system from an ISO file that you have obtained 864 from the Internet. For example, most Linux distributions 865 are available in this way.</para> 866 867 <para>For virtual CD/DVD drives, the following 868 additional options are available:</para> 869 870 <para><itemizedlist> 871 <listitem> 872 <para>If you select <emphasis role="bold">"Host 873 drive"</emphasis> from the list, then the physical 874 device of the host computer is connected to the VM, 875 so that the guest operating system can read from and 876 write to your physical device. This is, for 877 instance, useful if you want to install Windows from 878 a real installation CD. In this case, select your 879 host drive from the drop-down list presented.</para> 880 881 <para>If you want to write (burn) CDs or DVDs using 882 the host drive, you need to also enable the 883 <emphasis role="bold">"Passthrough"</emphasis> 884 option; see <xref linkend="storage-cds" />.</para> 885 </listitem> 886 887 <listitem> 888 <para>If you select <emphasis role="bold">"Remove 889 disk from virtual drive",</emphasis> VirtualBox will 890 present an empty CD/DVD drive to the guest into 891 which no media has been inserted.</para> 892 </listitem> 893 </itemizedlist></para> 894 </listitem> 895 </itemizedlist></para> 847 896 </listitem> 848 849 <listitem> 850 <para>The other items in the list, like virtual hard disk 851 images, will be image files on your host. The file format here 852 is the ISO format. Most commonly, you will select this option 853 when installing an operating system from an ISO file that you 854 have obtained from the Internet. For example, most Linux 855 distributions are available in this way.</para> 856 </listitem> 857 </itemizedlist></para> 858 859 <note> 860 <para>The identification string of the drive provided to the guest 861 (which, in the guest, would be displayed by configuration tools 862 such as the Windows Device Manager) is always "VBOX CD-ROM", 863 irrespective of the current configuration of the virtual drive. 864 This is to prevent hardware detection from being triggered in the 865 guest operating system every time the configuration is 866 changed.</para> 867 </note> 897 </orderedlist></para> 898 </listitem> 899 900 <listitem> 901 <para>To <emphasis role="bold">remove an attachment,</emphasis> 902 select it and click on the "remove" icon at the bottom (or 903 right-click on it and select the menu item).</para> 868 904 </listitem> 869 905 </itemizedlist></para> 870 871 <para>Note that the floppy controller is special: you cannot add devices872 other than floppy drives to it. Virtual floppy drives, like virtual CD/DVD873 drives, can be connected to either a host floppy drive (if you have one)874 or a disk image, which in this case must be in RAW format.</para>875 876 <para>To <emphasis role="bold">remove a virtual disk or drive,</emphasis>877 select it and click on the "remove" icon at the bottom (or right-click on878 it and select the menu item).</para>879 906 880 907 <para>Removable media (CD/DVDs and floppies) can be changed while the … … 882 909 time, you can also access these settings from the "Devices" menu of your 883 910 virtual machine window.</para> 884 885 <para>We have dedicated an entire chapter of this User Manual to virtual886 storage: please see <xref linkend="storage" /> for every single detail887 about storage configuration.</para>888 911 </sect1> 889 912 … … 922 945 outside world using the host's networking and the outside world can 923 946 connect to services on the guest which you choose to make visible outside 924 of the virtual machine. In most cases, this default setup will work fine 925 for you.</para> 926 927 <para>However, VirtualBox is extremely flexible in how it can virtualize 928 networking. It supports up to eight virtual network cards per virtual 929 machine, the first four of which can be configured in detail in the 930 graphical user interface. All eight network cards can be configured on the 931 command line with VBoxManage. Because of this, we have dedicated an entire 932 chapter of this manual to discussing networking configuration; please see 933 <xref linkend="networkingdetails" />.</para> 947 of the virtual machine.</para> 948 949 <para>This default setup is good for probably 95% of VirtualBox users. 950 However, VirtualBox is extremely flexible in how it can virtualize 951 networking. It supports many virtual network cards per virtual machine, 952 the first four of which can be configured in detail in the Manager window. 953 Additional network cards can be configured on the command line with 954 VBoxManage. </para> 955 956 <para>Because of the vast array of options available, we have dedicated an 957 entire chapter of this manual to discussing networking configuration; 958 please see <xref linkend="networkingdetails" />.</para> 934 959 </sect1> 935 960 … … 944 969 <para>Ever since the original IBM PC, personal computers have been 945 970 equipped with one or two serial ports (also called COM ports by DOS and 946 Windows). While these are no longer as important as they were until a few 947 years ago (especially since mice are no longer connected to serial ports 948 these days), there are still some important uses left for them. For 949 example, serial ports can be used to set up a primitive network over a 950 null-modem cable, in case Ethernet is not available. Also, serial ports 951 are indispensable for system programmers needing to do kernel debugging, 952 since kernel debugging software usually interacts with developers over a 953 serial port. In other words, with virtual serial ports, system programmers 954 can do kernel debugging on a virtual machine instead of needing a real 955 computer to connect to.</para> 971 Windows). Most importantly, computer mice used to be connected to serial 972 ports before USB became commonplace. </para> 973 974 <para>While serial ports are no longer as important as they used to be, 975 there are still some important uses left for them. For example, serial 976 ports can be used to set up a primitive network over a null-modem cable, 977 in case Ethernet is not available. Also, serial ports are indispensable 978 for system programmers needing to do kernel debugging, since kernel 979 debugging software usually interacts with developers over a serial port. 980 With virtual serial ports, system programmers can do kernel debugging on a 981 virtual machine instead of needing a real computer to connect to.</para> 956 982 957 983 <para>If a virtual serial port is enabled, the guest operating system sees 958 it a standard 16450-type serial port. Both receiving and transmitting data959 is supported. How this virtual serial port is then connected to the host960 is configurable, anddetails depend on your host operating system.</para>984 a standard 16450-type device. Both receiving and transmitting data is 985 supported. How this virtual serial port is then connected to the host is 986 configurable, and the details depend on your host operating system.</para> 961 987 962 988 <para>You can use either the graphical user interface or the command-line … … 1005 1031 <listitem> 1006 1032 <para>You can elect to have the virtual serial port 1007 "disconnected", which means that the guest will see it as1008 hardware, but it will behave as if no cable had been connected1033 "disconnected", which means that the guest will see the 1034 device, but it will behave as if no cable had been connected 1009 1035 to it.</para> 1010 1036 </listitem> … … 1014 1040 serial port on your host. (On a Windows host, this will be a 1015 1041 name like <computeroutput>COM1</computeroutput>; on Linux or 1016 OpenSolaris hosts, it will be a device node like1042 Solaris hosts, it will be a device node like 1017 1043 <computeroutput>/dev/ttyS0</computeroutput>). VirtualBox will 1018 1044 then simply redirect all data received from and sent to the -
trunk/doc/manual/en_US/user_Glossary.xml
r35153 r35174 370 370 371 371 <glossdiv> 372 <title>T</title> 373 374 <glossentry> 375 <glossterm>TAR</glossterm> 376 377 <glossdef> 378 <para>A widely used file format for archiving. Originally, this stood 379 for "Tape ARchive" and was already supported by very early Unix 380 versions for backing up data on tape. The file format is still widely 381 used today, for example, with OVF archives (with an 382 <computeroutput>.ova</computeroutput> file extension); see <xref 383 linkend="ovf" />.</para> 384 </glossdef> 385 </glossentry> 386 </glossdiv> 387 388 <glossdiv> 372 389 <title>U</title> 373 390 -
trunk/doc/manual/en_US/user_GuestAdditions.xml
r35141 r35174 1215 1215 guests. In particular:<itemizedlist> 1216 1216 <listitem> 1217 <para>3D acceleration with Windows guests requires Windows 2000, 1218 Windows XP, Vista or Windows 7. Both OpenGL and Direct3D 8/9 1219 (not with Windows 2000) are supported (experimental).</para> 1217 <para>3D acceleration with Windows guests requires Windows 1218 2000, Windows XP, Vista or Windows 7. Both OpenGL and 1219 Direct3D 8/9 (not with Windows 2000) are supported 1220 (experimental).</para> 1220 1221 </listitem> 1221 1222 1222 1223 <listitem> 1223 1224 <para>OpenGL on Linux requires kernel 2.6.27 and higher as 1224 well as X.org server version 1.5 and higher. Ubuntu 10.10 and 1225 Fedora 14 have been tested and confirmed as working.</para> 1225 well as X.org server version 1.5 and higher. Ubuntu 10.10 1226 and Fedora 14 have been tested and confirmed as 1227 working.</para> 1226 1228 </listitem> 1227 1229 … … 1344 1346 <para><mediaobject> 1345 1347 <imageobject> 1346 <imagedata align="center" fileref="images/seamless.png" width="1 0cm" />1348 <imagedata align="center" fileref="images/seamless.png" width="14cm" /> 1347 1349 </imageobject> 1348 1350 </mediaobject>To enable seamless mode, after starting the virtual … … 1503 1505 guest directories is available.</para> 1504 1506 1505 <para>To use these features, use the VirtualBox command line, see 1506 <xreflinkend="vboxmanage-guestcontrol" />.</para>1507 <para>To use these features, use the VirtualBox command line, see <xref 1508 linkend="vboxmanage-guestcontrol" />.</para> 1507 1509 </sect1> 1508 1510 -
trunk/doc/manual/en_US/user_Introduction.xml
r35090 r35174 22 22 up to datacenter deployments and even Cloud environments.</para> 23 23 24 <para>The following screenshot shows you how VirtualBox, installed on a 25 Linux machine, is running Windows 7 in a virtual machine window:</para>24 <para>The following screenshot shows you how VirtualBox, installed on a Mac 25 computer, is running Windows 7 in a virtual machine window:</para> 26 26 27 27 <para><mediaobject> 28 28 <imageobject> 29 29 <imagedata align="center" fileref="images/vm-vista-running.png" 30 width="1 0cm" />30 width="14cm" /> 31 31 </imageobject> 32 32 </mediaobject></para> … … 546 546 To install an extension, simply double-click on the package file, 547 547 and the VirtualBox Manager will guide you through the required 548 steps. 548 steps.</para> 549 549 550 550 <para>To view the extension packs that are currently installed, … … 595 595 width="10cm" /> 596 596 </imageobject> 597 </mediaobject>This is the VirtualBox Manager window. On the left, you 598 can see a pane that will later list all your virtual machines. Since you 599 have not created any, the list is empty. A row of buttons above it allows 600 you to create new VMs and work on existing VMs, once you have some. The 601 pane on the right displays the properties of the virtual machine currently 597 </mediaobject>This window is called the <emphasis 598 role="bold">"VirtualBox Manager".</emphasis> On the left, you can see a 599 pane that will later list all your virtual machines. Since you have not 600 created any, the list is empty. A row of buttons above it allows you to 601 create new VMs and work on existing VMs, once you have some. The pane on 602 the right displays the properties of the virtual machine currently 602 603 selected, if any. Again, since you don't have any machines yet, the pane 603 604 displays a welcome message.</para> … … 711 712 </mediaobject></para> 712 713 713 <para> In the wizard,you have the following options:</para>714 <para>Here you have the following options:</para> 714 715 715 716 <para><itemizedlist> … … 1132 1133 <imageobject> 1133 1134 <imagedata align="center" fileref="images/vm-close.png" 1134 width=" 7cm" />1135 width="11cm" /> 1135 1136 </imageobject> 1136 1137 </mediaobject>The difference between these three options is crucial. … … 1252 1253 <imageobject> 1253 1254 <imagedata align="center" fileref="images/snapshots-1.png" 1254 width="1 0cm" />1255 width="12cm" /> 1255 1256 </imageobject> 1256 1257 </mediaobject></para> 1257 1258 1258 <para>VirtualBox allows you to take an unlimited number of1259 snapshots -- the only limitation is the size of your disks. Keep1260 in mind that each snapshot stores the state of the virtual machine1261 and thus needs some disk space; see the next section for1262 details.</para>1259 <para>VirtualBox imposes no limits on the number of snapshots you 1260 can take. The only practical limitation is disk space on your 1261 host: each snapshot stores the state of the virtual machine and 1262 thus occupies some disk space. (See the next section for details 1263 on what exactly is stored in a snapshot.)</para> 1263 1264 </listitem> 1264 1265 … … 1268 1269 snapshots. By restoring a snapshot, you go back (or forward) in 1269 1270 time: the current state of the machine is lost, and the machine is 1270 restored to exactly the same state as it waswhen the snapshot was1271 restored to the exact state it was in when the snapshot was 1271 1272 taken.<footnote> 1272 1273 <para>Both the terminology and the functionality of restoring … … 1340 1341 the hard disk configuration or the VM's system settings, that 1341 1342 change is undone when you restore the snapshot.)</para> 1343 1344 <para>The copy of the settings is stored in the machine 1345 configuration, an XML text file, and thus occupies very little 1346 space.</para> 1342 1347 </listitem> 1343 1348 … … 1362 1367 less disk space. For the details, which can be complex, please see 1363 1368 <xref linkend="diffimages" />.)</para> 1369 1370 <para>Creating the differencing image as such does not occupy much 1371 space on the host disk initially, since the differencing image 1372 will initially be empty (and grow dynamically later with each 1373 write operation to the disk). The longer you use the machine after 1374 having created the snapshot, however, the more the differencing 1375 image will grow in size.</para> 1364 1376 </listitem> 1365 1377 … … 1370 1382 VM window). When you restore such a snapshot, execution resumes at 1371 1383 exactly the point when the snapshot was taken.</para> 1384 1385 <para>The memory state file can be as large as the memory size of 1386 the virtual machine and will therefore occupy quite some disk 1387 space as well.</para> 1372 1388 </listitem> 1373 1389 </itemizedlist></para> … … 1459 1475 1460 1476 <listitem> 1461 <para>Alternatively, the above files can be packed together into one 1462 archive file, typically with an 1463 <computeroutput>.ova</computeroutput> extension; such archive files 1464 use a variant of the TAR archive format.</para> 1477 <para>Alternatively, the above files can be packed together into a 1478 single archive file, typically with an 1479 <computeroutput>.ova</computeroutput> extension. (Such archive files 1480 use a variant of the TAR archive format and can therefore be 1481 unpacked outside of VirtualBox with any utility that can unpack 1482 standard TAR files.)</para> 1465 1483 </listitem> 1466 1484 </orderedlist></para> … … 1482 1500 <imageobject> 1483 1501 <imagedata align="center" fileref="images/ovf-import.png" 1484 width="1 0cm" />1502 width="12cm" /> 1485 1503 </imageobject> 1486 1504 </mediaobject>This presents the virtual machines described in the OVF -
trunk/doc/manual/en_US/user_Storage.xml
r35143 r35174 348 348 <imageobject> 349 349 <imagedata align="center" fileref="images/virtual-disk-manager.png" 350 width="1 0cm" />350 width="12cm" /> 351 351 </imageobject> 352 352 </mediaobject>The known media are conveniently grouped in three tabs for … … 545 545 <para>Technically, a "multiattach" image behaves identically to an 546 546 "immutable" image except the differencing image is not reset every 547 time the machine starts. 547 time the machine starts.</para> 548 548 </listitem> 549 549 … … 616 616 <imageobject> 617 617 <imagedata align="center" fileref="images/virtual-disk-manager2.png" 618 width="1 0cm" />618 width="12cm" /> 619 619 </imageobject> 620 620 </mediaobject></para> … … 863 863 eject which many CD/DVD drives provide, with all associated side effects: 864 864 the guest OS can issue error messages, just like on real hardware, and 865 guest applications may misbehave. Use this with caution.</para> 865 guest applications may misbehave. Use this with caution.<note> 866 <para>The identification string of the drive provided to the guest 867 (which, in the guest, would be displayed by configuration tools such 868 as the Windows Device Manager) is always "VBOX CD-ROM", irrespective 869 of the current configuration of the virtual drive. This is to prevent 870 hardware detection from being triggered in the guest operating system 871 every time the configuration is changed.</para> 872 </note></para> 866 873 867 874 <para>The standard CD/DVD emulation allows for reading standard data CD
Note:
See TracChangeset
for help on using the changeset viewer.