VirtualBox

Changeset 32331 in vbox for trunk


Ignore:
Timestamp:
Sep 8, 2010 8:01:07 PM (14 years ago)
Author:
vboxsync
Message:

doc/manual: cosmetical fixes

Location:
trunk/doc/manual
Files:
8 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/manual/Makefile.kmk

    r32321 r32331  
    479479        $(QUIET)$(REDIRECT) -C $(@D) -- $(PDFLATEX) UserManual.tex
    480480        $(QUIET)$(REDIRECT) -C $(@D) -- $(PDFLATEX) UserManual.tex
     481        $(QUIET)$(REDIRECT) -C $(@D) -- $(PDFLATEX) UserManual.tex
    481482##@todo restore this when above has been converted to INSTALLS target.  $(call MSG_L1,Fresh LaTeX-generated PDF is now at $@)
    482483
  • trunk/doc/manual/en_US/user_AdvancedTopics.xml

    r32018 r32331  
    296296      Windows <computeroutput>SYSTEM32</computeroutput> directory. Then, in
    297297      the registry, create the following key:
    298       <screen>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\
    299            Winlogon\GinaDLL</screen>
     298      <screen>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Winlogon\GinaDLL</screen>
    300299      with a value of <computeroutput>VBoxGINA.dll</computeroutput>.</para>
    301300
     
    310309      and copy the file <computeroutput>VBoxCredProv.dll</computeroutput> to
    311310      the Windows <computeroutput>SYSTEM32</computeroutput> directory. Then,
    312       in the registry, create the following keys:<screen>
    313       HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
     311      in the registry, create the following keys:<screen>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\
    314312           Authentication\Credential Providers\{275D3BCC-22BB-4948-A7F6-3A3054EBA92B}
    315313
     
    329327      <emphasis>running</emphasis> VM:</para>
    330328
    331       <screen>VBoxManage controlvm "Windows XP"
    332       setcredentials "John Doe" "secretpassword" "DOMTEST"</screen>
     329      <screen>VBoxManage controlvm "Windows XP" setcredentials "John Doe" "secretpassword" "DOMTEST"</screen>
    333330
    334331      <para>While the VM is running, the credentials can be queried by the
     
    370367
    371368      <para>The following command forces VirtualBox to keep the credentials
    372       after they were read by the guest and on VM reset: <screen>VBoxManage setextradata "Windows XP"
    373       VBoxInternal/Devices/VMMDev/0/Config/KeepCredentials 1</screen>Note that
     369      after they were read by the guest and on VM reset: <screen>VBoxManage setextradata "Windows XP" VBoxInternal/Devices/VMMDev/0/Config/KeepCredentials 1</screen>Note that
    374370      this is a potential security risk as a malicious application running on
    375371      the guest could request this information using the proper
     
    535531    <para>At this time, CPU hot-plugging requires using the VBoxManage
    536532    command-line interface. First, hot-plugging needs to be enabled for a
    537     virtual machine:<screen>VBoxManage modifyvm &lt;vmname&gt; --cpuhotplug on</screen></para>
     533    virtual machine:<screen>VBoxManage modifyvm "VM name" --cpuhotplug on</screen></para>
    538534
    539535    <para>After that, the --cpus option specifies the maximum number of CPUs
    540     that the virtual machine can have:<screen>VBoxManage modifyvm &lt;vmname&gt; --cpus 8</screen>When
     536    that the virtual machine can have:<screen>VBoxManage modifyvm "VM name" --cpus 8</screen>When
    541537    the VM is off, you can then add and remove virtual CPUs with the modifyvm
    542538    --plugcpu and --unplugcpu subcommands, which take the number of the
    543     virtual CPU as a parameter, like this:<screen>VBoxManage modifyvm &lt;vmname&gt; --plugcpu 3
    544 VBoxManage modifyvm &lt;vmname&gt; --unplugcpu 3</screen>Note that CPU 0 can
     539    virtual CPU as a parameter, like this:<screen>VBoxManage modifyvm "VM name" --plugcpu 3
     540VBoxManage modifyvm "VM name" --unplugcpu 3</screen>Note that CPU 0 can
    545541    never be removed.</para>
    546542
    547543    <para>While the VM is running, CPUs can be added with the
    548544    <computeroutput>controlvm plugcpu/unplugcpu</computeroutput> commands
    549     instead:<screen>VBoxManage controlvm &lt;vmname&gt; plugcpu 3
    550 VBoxManage controlvm &lt;vmname&gt; unplugcpu 3</screen></para>
     545    instead:<screen>VBoxManage controlvm "VM name" plugcpu 3
     546VBoxManage controlvm "VM name" unplugcpu 3</screen></para>
    551547
    552548    <para>See <xref linkend="vboxmanage-modifyvm" /> and <xref
     
    583579      display resolution of many notebook computers:</para>
    584580
    585       <screen>VBoxManage setextradata "VM name"
    586       "CustomVideoMode1" "1400x1050x16"</screen>
     581      <screen>VBoxManage setextradata "VM name" "CustomVideoMode1" "1400x1050x16"</screen>
    587582
    588583      <para>The VESA mode IDs for custom video modes start at
     
    614609      <para>will remove all limits on guest resolutions.</para>
    615610
    616       <screen>VBoxManage setextradata global GUI/MaxGuestResolution
    617       &gt;width,height&lt;</screen>
     611      <screen>VBoxManage setextradata global GUI/MaxGuestResolution &gt;width,height&lt;</screen>
    618612
    619613      <para>manually specifies a maximum resolution.</para>
     
    896890      number. These can be changed using the following commands:</para>
    897891
    898       <screen>VBoxManage setextradata "My VM"
     892      <screen>VBoxManage setextradata "VM name"
    899893      "VBoxInternal/Devices/ahci/0/Config/Port0/SerialNumber"
    900894      "serial"
    901 VBoxManage setextradata "My VM"
     895VBoxManage setextradata "VM name"
    902896      "VBoxInternal/Devices/ahci/0/Config/Port0/FirmwareRevision"
    903897      "firmware"
    904 VBoxManage setextradata "My VM"
     898VBoxManage setextradata "VM name"
    905899      "VBoxInternal/Devices/ahci/0/Config/Port0/ModelNumber"
    906900      "model"</screen>
     
    914908      the vendor product data:</para>
    915909
    916       <screen>VBoxManage setextradata "My VM"
     910      <screen>VBoxManage setextradata "VM name"
    917911      "VBoxInternal/Devices/ahci/0/Config/Port0/ATAPIVendorId"
    918912      "vendor"
    919 VBoxManage setextradata "My VM"
     913VBoxManage setextradata "VM name"
    920914      "VBoxInternal/Devices/ahci/0/Config/Port0/ATAPIProductId"
    921915      "product"
    922 VBoxManage setextradata "My VM"
     916VBoxManage setextradata "VM name"
    923917      "VBoxInternal/Devices/ahci/0/Config/Port0/ATAPIRevision"
    924918      "revision"</screen>
     
    967961
    968962    <para>The old sequence of configuring a serial port used the following 6
    969     commands:<screen>VBoxManage setextradata "YourVM"
     963    commands:<screen>VBoxManage setextradata "VM name"
    970964      "VBoxInternal/Devices/serial/0/Config/IRQ" 4
    971 VBoxManage setextradata "YourVM"
     965VBoxManage setextradata "VM name"
    972966      "VBoxInternal/Devices/serial/0/Config/IOBase" 0x3f8
    973 VBoxManage setextradata "YourVM"
     967VBoxManage setextradata "VM name"
    974968      "VBoxInternal/Devices/serial/0/LUN#0/Driver" Char
    975 VBoxManage setextradata "YourVM"
     969VBoxManage setextradata "VM name"
    976970      "VBoxInternal/Devices/serial/0/LUN#0/AttachedDriver/Driver" NamedPipe
    977 VBoxManage setextradata "YourVM"
     971VBoxManage setextradata "VM name"
    978972      "VBoxInternal/Devices/serial/0/LUN#0/AttachedDriver/Config/Location"
    979973      "\\.\pipe\vboxCOM1"
    980 VBoxManage setextradata "YourVM"
     974VBoxManage setextradata "VM name"
    981975      "VBoxInternal/Devices/serial/0/LUN#0/AttachedDriver/Config/IsServer"
    982976      1</screen>This sets up a serial port in the guest with the default
     
    10131007      be achieved with the following command:</para>
    10141008
    1015       <screen>VBoxManage modifyvm "My VM" --natnet1 "192.168/16"</screen>
     1009      <screen>VBoxManage modifyvm "VM name" --natnet1 "192.168/16"</screen>
    10161010
    10171011      <para>This command would reserve the network addresses from
    10181012      <computeroutput>192.168.0.0</computeroutput> to
    10191013      <computeroutput>192.168.254.254</computeroutput> for the first NAT
    1020       network instance of "My VM". The guest IP would be assigned to
     1014      network instance of "VM name". The guest IP would be assigned to
    10211015      <computeroutput>192.168.0.15</computeroutput> and the default gateway
    10221016      could be found at <computeroutput>192.168.0.2</computeroutput>.</para>
     
    10311025      should work fine for typical remote-booting scenarios. However, it is
    10321026      possible to change the boot server IP and the location of the boot image
    1033       with the following commands: <screen>VBoxManage modifyvm "My VM" --nattftpserver1 10.0.2.2
    1034 VBoxManage modifyvm "My VM" --nattftpfile1 /srv/tftp/boot/MyPXEBoot.pxe</screen></para>
     1027      with the following commands: <screen>VBoxManage modifyvm "VM name" --nattftpserver1 10.0.2.2
     1028VBoxManage modifyvm "VM name" --nattftpfile1 /srv/tftp/boot/MyPXEBoot.pxe</screen></para>
    10351029    </sect2>
    10361030
     
    10441038      might want to adjust the buffer size for a better performance. This can
    10451039      by achieved using the following commands (values are in kilobytes and
    1046       can range from 8 to 1024): <screen>VBoxManage modifyvm "My VM" --natsettings1 16000,128,128,0,0</screen>
     1040      can range from 8 to 1024): <screen>VBoxManage modifyvm "VM name" --natsettings1 16000,128,128,0,0</screen>
    10471041      This example illustrates tuning the NAT settings. The first parameter is
    10481042      the MTU, then the size of the socket's send buffer and the size of the
     
    10631057      communication.) If, for some reason, you want to change this behavior,
    10641058      you can tell the NAT engine to bind to a particular IP address instead.
    1065       Use the following command: <screen>VBoxManage modifyvm "My VM" --natbindip1 "10.45.0.2"</screen></para>
     1059      Use the following command: <screen>VBoxManage modifyvm "VM name" --natbindip1 "10.45.0.2"</screen></para>
    10661060
    10671061      <para>After this, all outgoing traffic will be sent through the
     
    10781072      information can change on the host due to expiring DHCP leases. In this
    10791073      case, you can tell the NAT engine to act as DNS proxy using the
    1080       following command: <screen>VBoxManage modifyvm "My VM" --natdnsproxy1 on</screen></para>
     1074      following command: <screen>VBoxManage modifyvm "VM name" --natdnsproxy1 on</screen></para>
    10811075    </sect2>
    10821076
     
    10891083      settings, thereby forcing the VirtualBox NAT engine to intercept DNS
    10901084      requests and forward them to host's resolver, use the following command:
    1091       <screen>VBoxManage modifyvm "My VM" --natdnshostresolver1 on</screen>
     1085      <screen>VBoxManage modifyvm "VM name" --natdnshostresolver1 on</screen>
    10921086      Note that this setting is similar to the DNS proxy mode, however whereas
    10931087      the proxy mode just forwards DNS requests to the appropriate servers,
     
    11041098      more transparent behavior or may depend on the real port number the
    11051099      packet was sent from. It is possible to change the NAT mode via the
    1106       VBoxManage frontend with the following commands: <screen>VBoxManage modifyvm "My VM" --nataliasmode proxyonly</screen>
     1100      VBoxManage frontend with the following commands: <screen>VBoxManage modifyvm "VM name" --nataliasmode proxyonly</screen>
    11071101      and <screen>VBoxManage modifyvm "Linux Guest" --nataliasmode sameports</screen>
    11081102      The first example disables aliasing and switches NAT into transparent
     
    11191113    information:</para>
    11201114
    1121     <screen>VBoxManage setextradata "My VM"
     1115    <screen>VBoxManage setextradata "VM name"
    11221116      "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVendor"        "BIOS Vendor"
    1123 VBoxManage setextradata "My VM"
     1117VBoxManage setextradata "VM name"
    11241118      "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVersion"       "BIOS Version"
    1125 VBoxManage setextradata "My VM"
     1119VBoxManage setextradata "VM name"
    11261120      "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseDate"   "BIOS Release Date"
    1127 VBoxManage setextradata "My VM"
     1121VBoxManage setextradata "VM name"
    11281122      "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMajor"  1
    1129 VBoxManage setextradata "My VM"
     1123VBoxManage setextradata "VM name"
    11301124      "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMinor"  2
    1131 VBoxManage setextradata "My VM"
     1125VBoxManage setextradata "VM name"
    11321126      "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMajor" 3
    1133 VBoxManage setextradata "My VM"
     1127VBoxManage setextradata "VM name"
    11341128      "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMinor" 4
    1135 VBoxManage setextradata "My VM"
     1129VBoxManage setextradata "VM name"
    11361130      "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVendor"      "System Vendor"
    1137 VBoxManage setextradata "My VM"
     1131VBoxManage setextradata "VM name"
    11381132      "VBoxInternal/Devices/pcbios/0/Config/DmiSystemProduct"     "System Product"
    1139 VBoxManage setextradata "My VM"
     1133VBoxManage setextradata "VM name"
    11401134      "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVersion"     "System Version"
    1141 VBoxManage setextradata "My VM"
     1135VBoxManage setextradata "VM name"
    11421136      "VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial"      "System Serial"
    1143 VBoxManage setextradata "My VM"
     1137VBoxManage setextradata "VM name"
    11441138      "VBoxInternal/Devices/pcbios/0/Config/DmiSystemFamily"      "System Family"
    1145 VBoxManage setextradata "My VM"
     1139VBoxManage setextradata "VM name"
    11461140      "VBoxInternal/Devices/pcbios/0/Config/DmiSystemUuid"
    11471141                                               "9852bf98-b83c-49db-a8de-182c42c7226b"</screen>
     
    11571151    <computeroutput>VERR_CFGM_NOT_STRING</computeroutput> error. In that case,
    11581152    use <computeroutput>"string:&lt;value&gt;"</computeroutput>, for instance
    1159     <screen>VBoxManage setextradata "My VM"
     1153    <screen>VBoxManage setextradata "VM name"
    11601154      "VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial"      "string:1234"</screen></para>
    11611155
     
    11861180      virtualization. To enable this mode use the following command:</para>
    11871181
    1188       <screen>VBoxManage setextradata "My VM" "VBoxInternal/TM/TSCTiedToExecution" 1</screen>
     1182      <screen>VBoxManage setextradata "VM name" "VBoxInternal/TM/TSCTiedToExecution" 1</screen>
    11891183
    11901184      <para>To revert to the default TSC handling mode use:</para>
    11911185
    1192       <screen>VBoxManage setextradata "My VM" "VBoxInternal/TM/TSCTiedToExecution"</screen>
     1186      <screen>VBoxManage setextradata "VM name" "VBoxInternal/TM/TSCTiedToExecution"</screen>
    11931187
    11941188      <para>Note that if you use the special TSC handling mode with a guest
     
    12051199      down the (virtual) guest clock. This can be achieved as follows:</para>
    12061200
    1207       <screen>VBoxManage setextradata "My VM"
    1208       "VBoxInternal/TM/WarpDrivePercentage" 200</screen>
     1201      <screen>VBoxManage setextradata "VM name" "VBoxInternal/TM/WarpDrivePercentage" 200</screen>
    12091202
    12101203      <para>The above example will double the speed of the guest clock
    12111204      while</para>
    12121205
    1213       <screen>VBoxManage setextradata "My VM"
    1214       "VBoxInternal/TM/WarpDrivePercentage" 50</screen>
     1206      <screen>VBoxManage setextradata "VM name" "VBoxInternal/TM/WarpDrivePercentage" 50</screen>
    12151207
    12161208      <para>will halve the speed of the guest clock. Note that changing the
     
    13921384    <para>Furthermore, you can disallow certain actions when terminating a VM
    13931385      from the GUI. To disallow specific actions, type:</para>
    1394     <para><screen>VBoxManage setextradata "My VM" GUI/RestrictedCloseActions OPTION[,OPTION...]</screen></para>
     1386    <para><screen>VBoxManage setextradata "VM name" GUI/RestrictedCloseActions OPTION[,OPTION...]</screen></para>
    13951387    <para>where <computeroutput>OPTION</computeroutput> is one of the following
    13961388      keywords:<glosslist>
  • trunk/doc/manual/en_US/user_BasicConcepts.xml

    r31735 r32331  
    12241224
    12251225      <para>To control GOP, use the following
    1226       <computeroutput>VBoxManage</computeroutput> command: <screen>
    1227                 VBoxManage setextradata vmname VBoxInternal2/EfiGopMode N </screen>
     1226      <computeroutput>VBoxManage</computeroutput> command: <screen>VBoxManage setextradata "VM name" VBoxInternal2/EfiGopMode N</screen>
    12281227      Where N can be one of 0,1,2,3,4 referring to the 640x480, 800x600,
    12291228      1024x768, 1280x1024, 1440x900 screen resolution respectively.</para>
    12301229
    1231       <para>To change the UGA resolution: <screen>
    1232                 VBoxManage setextradata vmname VBoxInternal2/UgaHorizontalResolution 1440
    1233                 VBoxManage setextradata vmname VBoxInternal2/UgaVerticalResolution    900</screen></para>
     1230      <para>To change the UGA resolution: <screen>VBoxManage setextradata "VM name" VBoxInternal2/UgaHorizontalResolution 1440
     1231VBoxManage setextradata "VM name" VBoxInternal2/UgaVerticalResolution    900</screen></para>
    12341232
    12351233      <para>The video mode for both GOP and UGA can only be changed when the
  • trunk/doc/manual/en_US/user_Frontends.xml

    r32177 r32331  
    7575            find it under "Start" -&gt; "All Programs" -&gt; "Accessories"
    7676            -&gt; "Remote Desktop Connection". If you use the "Run" dialog,
    77             you can type in options directly:<screen>mstsc 1.2.3.4[:3389] </screen></para>
     77            you can type in options directly:<screen>mstsc 1.2.3.4[:3389]</screen></para>
    7878
    7979            <para>Replace "1.2.3.4" with the host IP address, and 3389 with a
     
    388388            <computeroutput>VBoxManage setproperty vrdpauthlibrary "VRDPAuthSimple"</computeroutput>.
    389389            To enable the library for a VM, switch authentication to external using
    390             <computeroutput>VBoxManage modifyvm "VMNAME" --vrdpauthtype external</computeroutput>.
     390            <computeroutput>VBoxManage modifyvm "VM name" --vrdpauthtype external</computeroutput>.
    391391            Last but not least, you have to configure users and passwords. Here is an example
    392392            for the user "john" with the password "secret":
    393             <computeroutput>VBoxManage setextradata "VMNAME" "VRDPAuthSimple/users/john" "secret"</computeroutput>
     393            <computeroutput>VBoxManage setextradata "VM name" "VRDPAuthSimple/users/john" "secret"</computeroutput>
    394394            To specify an empty password, use the special reserved value
    395395            <computeroutput>[NULL]</computeroutput>.
     
    528528      <para>The following commands change corresponding server settings:</para>
    529529
    530       <screen>VBoxManage setextradata VMNAME "VRDP/Feature/Client/DisableDisplay" 1</screen>
    531       <screen>VBoxManage setextradata VMNAME "VRDP/Feature/Client/DisableInput" 1</screen>
    532       <screen>VBoxManage setextradata VMNAME "VRDP/Feature/Client/DisableUSB" 1</screen>
    533       <screen>VBoxManage setextradata VMNAME "VRDP/Feature/Client/DisableAudio" 1</screen>
    534       <screen>VBoxManage setextradata VMNAME "VRDP/Feature/Client/DisableClipboard" 1</screen>
     530      <screen>VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableDisplay" 1
     531VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableInput" 1
     532VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableUSB" 1
     533VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableAudio" 1
     534VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableClipboard" 1</screen>
    535535
    536536      <para>To reenable a feature use a similar command without the trailing 1. For example:
    537       <screen>VBoxManage setextradata VMNAME "VRDP/Feature/Client/DisableDisplay"</screen></para>
     537      <screen>VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableDisplay"</screen></para>
    538538    </sect2>
    539539  </sect1>
  • trunk/doc/manual/en_US/user_GuestAdditions.xml

    r31735 r32331  
    329329        launcher:</para>
    330330
    331         <screen>
    332         VBoxWindowsAdditions.exe /S
    333       </screen>
     331        <screen>VBoxWindowsAdditions.exe /S</screen>
    334332
    335333        <para>This automatically installs the right files and drivers for the
     
    345343        consult the command line help by using the command:</para>
    346344
    347         <screen>
    348         VBoxWindowsAdditions.exe /?
    349       </screen>
     345        <screen>VBoxWindowsAdditions.exe /?</screen>
    350346      </sect3>
    351347
     
    782778        the current Guest Additions with the "uninstall" parameter from the
    783779        path that the CD image is mounted on in the guest:
    784         <screen>
    785         sh ./VBoxLinuxAdditions-x86.run uninstall
    786         </screen>
     780        <screen>sh ./VBoxLinuxAdditions-x86.run uninstall</screen>
    787781        <para>(substituting <computeroutput>VBoxLinuxAdditions-amd64</computeroutput>
    788782          on a 64-bit guest).  While this will normally work
     
    13971391Name: /VirtualBox/GuestInfo/OS/Version, value: #59-Ubuntu SMP Thu Jan 28 01:23:03 UTC 2010,
    13981392    timestamp: 1265813265836305000, flags: &lt;NULL&gt;
    1399       ...
    1400 </screen></para>
     1393      ...</screen></para>
    14011394
    14021395    <para>For more complex needs, you can use the VirtualBox programming
  • trunk/doc/manual/en_US/user_KnownIssues.xml

    r31735 r32331  
    196196            that there is a lot of output and not all errors are fatal (they
    197197            would also show on your physical Mac). You can turn off these
    198             messages by issuing this command:<screen>VBoxManage setextradata vmname "VBoxInternal2/EfiBootArgs" "  "</screen>To
    199             revert to the previous behavior, use:<screen>VBoxManage setextradata vmname "VBoxInternal2/EfiBootArgs" ""</screen></para>
     198            messages by issuing this command:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" "  "</screen>To
     199            revert to the previous behavior, use:<screen>VBoxManage setextradata "VM name" "VBoxInternal2/EfiBootArgs" ""</screen></para>
    200200          </listitem>
    201201        </itemizedlist></para>
  • trunk/doc/manual/en_US/user_Storage.xml

    r31735 r32331  
    920920      address, the IP configuration and the Internal Networking name
    921921      ("MyIntNet") according to your needs. The following seven commands must
    922       be issued:<screen>VBoxManage setextradata "VM name"
    923       VBoxInternal/Devices/IntNetIP/0/Trusted 1
    924 VBoxManage setextradata "VM name"
    925       VBoxInternal/Devices/IntNetIP/0/Config/MAC 08:00:27:01:02:0f
    926 VBoxManage setextradata "VM name"
    927       VBoxInternal/Devices/IntNetIP/0/Config/IP 10.0.9.1
    928 VBoxManage setextradata "VM name"
    929       VBoxInternal/Devices/IntNetIP/0/Config/Netmask 255.255.255.0
    930 VBoxManage setextradata "VM name"
    931       VBoxInternal/Devices/IntNetIP/0/LUN#0/Driver IntNet
    932 VBoxManage setextradata "VM name"
    933       VBoxInternal/Devices/IntNetIP/0/LUN#0/Config/Network MyIntNet
    934 VBoxManage setextradata "VM name"
    935       VBoxInternal/Devices/IntNetIP/0/LUN#0/Config/IsService 1</screen></para>
     922      be issued:<screen>VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/Trusted 1
     923VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/Config/MAC 08:00:27:01:02:0f
     924VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/Config/IP 10.0.9.1
     925VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/Config/Netmask 255.255.255.0
     926VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/LUN#0/Driver IntNet
     927VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/LUN#0/Config/Network MyIntNet
     928VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/LUN#0/Config/IsService 1</screen></para>
    936929
    937930      <para>Finally the iSCSI disk must be registered with the
    938931      <code>--intnet</code> option to tell the iSCSI initiator to use internal
    939       networking:<screen>VBoxManage addiscsidisk --server 10.0.9.30
    940       --target iqn.2008-12.com.sun:sampletarget --intnet</screen></para>
     932      networking:<screen>VBoxManage addiscsidisk --server 10.0.9.30 --target iqn.2008-12.com.sun:sampletarget --intnet</screen></para>
    941933
    942934      <para>The target address must be specified as a numeric IP address, as
  • trunk/doc/manual/en_US/user_Troubleshooting.xml

    r31735 r32331  
    578578      command:</para>
    579579
    580       <screen>VBoxManage setextradata "VM name"
    581       "VBoxInternal/Devices/piix3ide/0/Config/IRQDelay" 1</screen>
     580      <screen>VBoxManage setextradata "VM name" "VBoxInternal/Devices/piix3ide/0/Config/IRQDelay" 1</screen>
    582581
    583582      <para>This sets the delay to one millisecond. In case this doesn't help,
Note: See TracChangeset for help on using the changeset viewer.

© 2024 Oracle Support Privacy / Do Not Sell My Info Terms of Use Trademark Policy Automated Access Etiquette