- Timestamp:
- Sep 8, 2010 8:01:07 PM (14 years ago)
- Location:
- trunk/doc/manual
- Files:
-
- 8 edited
Legend:
- Unmodified
- Added
- Removed
-
trunk/doc/manual/Makefile.kmk
r32321 r32331 479 479 $(QUIET)$(REDIRECT) -C $(@D) -- $(PDFLATEX) UserManual.tex 480 480 $(QUIET)$(REDIRECT) -C $(@D) -- $(PDFLATEX) UserManual.tex 481 $(QUIET)$(REDIRECT) -C $(@D) -- $(PDFLATEX) UserManual.tex 481 482 ##@todo restore this when above has been converted to INSTALLS target. $(call MSG_L1,Fresh LaTeX-generated PDF is now at $@) 482 483 -
trunk/doc/manual/en_US/user_AdvancedTopics.xml
r32018 r32331 296 296 Windows <computeroutput>SYSTEM32</computeroutput> directory. Then, in 297 297 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> 300 299 with a value of <computeroutput>VBoxGINA.dll</computeroutput>.</para> 301 300 … … 310 309 and copy the file <computeroutput>VBoxCredProv.dll</computeroutput> to 311 310 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\ 314 312 Authentication\Credential Providers\{275D3BCC-22BB-4948-A7F6-3A3054EBA92B} 315 313 … … 329 327 <emphasis>running</emphasis> VM:</para> 330 328 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> 333 330 334 331 <para>While the VM is running, the credentials can be queried by the … … 370 367 371 368 <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 374 370 this is a potential security risk as a malicious application running on 375 371 the guest could request this information using the proper … … 535 531 <para>At this time, CPU hot-plugging requires using the VBoxManage 536 532 command-line interface. First, hot-plugging needs to be enabled for a 537 virtual machine:<screen>VBoxManage modifyvm <vmname>--cpuhotplug on</screen></para>533 virtual machine:<screen>VBoxManage modifyvm "VM name" --cpuhotplug on</screen></para> 538 534 539 535 <para>After that, the --cpus option specifies the maximum number of CPUs 540 that the virtual machine can have:<screen>VBoxManage modifyvm <vmname>--cpus 8</screen>When536 that the virtual machine can have:<screen>VBoxManage modifyvm "VM name" --cpus 8</screen>When 541 537 the VM is off, you can then add and remove virtual CPUs with the modifyvm 542 538 --plugcpu and --unplugcpu subcommands, which take the number of the 543 virtual CPU as a parameter, like this:<screen>VBoxManage modifyvm <vmname>--plugcpu 3544 VBoxManage modifyvm <vmname>--unplugcpu 3</screen>Note that CPU 0 can539 virtual CPU as a parameter, like this:<screen>VBoxManage modifyvm "VM name" --plugcpu 3 540 VBoxManage modifyvm "VM name" --unplugcpu 3</screen>Note that CPU 0 can 545 541 never be removed.</para> 546 542 547 543 <para>While the VM is running, CPUs can be added with the 548 544 <computeroutput>controlvm plugcpu/unplugcpu</computeroutput> commands 549 instead:<screen>VBoxManage controlvm <vmname>plugcpu 3550 VBoxManage controlvm <vmname>unplugcpu 3</screen></para>545 instead:<screen>VBoxManage controlvm "VM name" plugcpu 3 546 VBoxManage controlvm "VM name" unplugcpu 3</screen></para> 551 547 552 548 <para>See <xref linkend="vboxmanage-modifyvm" /> and <xref … … 583 579 display resolution of many notebook computers:</para> 584 580 585 <screen>VBoxManage setextradata "VM name" 586 "CustomVideoMode1" "1400x1050x16"</screen> 581 <screen>VBoxManage setextradata "VM name" "CustomVideoMode1" "1400x1050x16"</screen> 587 582 588 583 <para>The VESA mode IDs for custom video modes start at … … 614 609 <para>will remove all limits on guest resolutions.</para> 615 610 616 <screen>VBoxManage setextradata global GUI/MaxGuestResolution 617 >width,height<</screen> 611 <screen>VBoxManage setextradata global GUI/MaxGuestResolution >width,height<</screen> 618 612 619 613 <para>manually specifies a maximum resolution.</para> … … 896 890 number. These can be changed using the following commands:</para> 897 891 898 <screen>VBoxManage setextradata " My VM"892 <screen>VBoxManage setextradata "VM name" 899 893 "VBoxInternal/Devices/ahci/0/Config/Port0/SerialNumber" 900 894 "serial" 901 VBoxManage setextradata " My VM"895 VBoxManage setextradata "VM name" 902 896 "VBoxInternal/Devices/ahci/0/Config/Port0/FirmwareRevision" 903 897 "firmware" 904 VBoxManage setextradata " My VM"898 VBoxManage setextradata "VM name" 905 899 "VBoxInternal/Devices/ahci/0/Config/Port0/ModelNumber" 906 900 "model"</screen> … … 914 908 the vendor product data:</para> 915 909 916 <screen>VBoxManage setextradata " My VM"910 <screen>VBoxManage setextradata "VM name" 917 911 "VBoxInternal/Devices/ahci/0/Config/Port0/ATAPIVendorId" 918 912 "vendor" 919 VBoxManage setextradata " My VM"913 VBoxManage setextradata "VM name" 920 914 "VBoxInternal/Devices/ahci/0/Config/Port0/ATAPIProductId" 921 915 "product" 922 VBoxManage setextradata " My VM"916 VBoxManage setextradata "VM name" 923 917 "VBoxInternal/Devices/ahci/0/Config/Port0/ATAPIRevision" 924 918 "revision"</screen> … … 967 961 968 962 <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" 970 964 "VBoxInternal/Devices/serial/0/Config/IRQ" 4 971 VBoxManage setextradata " YourVM"965 VBoxManage setextradata "VM name" 972 966 "VBoxInternal/Devices/serial/0/Config/IOBase" 0x3f8 973 VBoxManage setextradata " YourVM"967 VBoxManage setextradata "VM name" 974 968 "VBoxInternal/Devices/serial/0/LUN#0/Driver" Char 975 VBoxManage setextradata " YourVM"969 VBoxManage setextradata "VM name" 976 970 "VBoxInternal/Devices/serial/0/LUN#0/AttachedDriver/Driver" NamedPipe 977 VBoxManage setextradata " YourVM"971 VBoxManage setextradata "VM name" 978 972 "VBoxInternal/Devices/serial/0/LUN#0/AttachedDriver/Config/Location" 979 973 "\\.\pipe\vboxCOM1" 980 VBoxManage setextradata " YourVM"974 VBoxManage setextradata "VM name" 981 975 "VBoxInternal/Devices/serial/0/LUN#0/AttachedDriver/Config/IsServer" 982 976 1</screen>This sets up a serial port in the guest with the default … … 1013 1007 be achieved with the following command:</para> 1014 1008 1015 <screen>VBoxManage modifyvm " My VM" --natnet1 "192.168/16"</screen>1009 <screen>VBoxManage modifyvm "VM name" --natnet1 "192.168/16"</screen> 1016 1010 1017 1011 <para>This command would reserve the network addresses from 1018 1012 <computeroutput>192.168.0.0</computeroutput> to 1019 1013 <computeroutput>192.168.254.254</computeroutput> for the first NAT 1020 network instance of " My VM". The guest IP would be assigned to1014 network instance of "VM name". The guest IP would be assigned to 1021 1015 <computeroutput>192.168.0.15</computeroutput> and the default gateway 1022 1016 could be found at <computeroutput>192.168.0.2</computeroutput>.</para> … … 1031 1025 should work fine for typical remote-booting scenarios. However, it is 1032 1026 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.21034 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 1028 VBoxManage modifyvm "VM name" --nattftpfile1 /srv/tftp/boot/MyPXEBoot.pxe</screen></para> 1035 1029 </sect2> 1036 1030 … … 1044 1038 might want to adjust the buffer size for a better performance. This can 1045 1039 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> 1047 1041 This example illustrates tuning the NAT settings. The first parameter is 1048 1042 the MTU, then the size of the socket's send buffer and the size of the … … 1063 1057 communication.) If, for some reason, you want to change this behavior, 1064 1058 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> 1066 1060 1067 1061 <para>After this, all outgoing traffic will be sent through the … … 1078 1072 information can change on the host due to expiring DHCP leases. In this 1079 1073 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> 1081 1075 </sect2> 1082 1076 … … 1089 1083 settings, thereby forcing the VirtualBox NAT engine to intercept DNS 1090 1084 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> 1092 1086 Note that this setting is similar to the DNS proxy mode, however whereas 1093 1087 the proxy mode just forwards DNS requests to the appropriate servers, … … 1104 1098 more transparent behavior or may depend on the real port number the 1105 1099 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> 1107 1101 and <screen>VBoxManage modifyvm "Linux Guest" --nataliasmode sameports</screen> 1108 1102 The first example disables aliasing and switches NAT into transparent … … 1119 1113 information:</para> 1120 1114 1121 <screen>VBoxManage setextradata " My VM"1115 <screen>VBoxManage setextradata "VM name" 1122 1116 "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVendor" "BIOS Vendor" 1123 VBoxManage setextradata " My VM"1117 VBoxManage setextradata "VM name" 1124 1118 "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSVersion" "BIOS Version" 1125 VBoxManage setextradata " My VM"1119 VBoxManage setextradata "VM name" 1126 1120 "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseDate" "BIOS Release Date" 1127 VBoxManage setextradata " My VM"1121 VBoxManage setextradata "VM name" 1128 1122 "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMajor" 1 1129 VBoxManage setextradata " My VM"1123 VBoxManage setextradata "VM name" 1130 1124 "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSReleaseMinor" 2 1131 VBoxManage setextradata " My VM"1125 VBoxManage setextradata "VM name" 1132 1126 "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMajor" 3 1133 VBoxManage setextradata " My VM"1127 VBoxManage setextradata "VM name" 1134 1128 "VBoxInternal/Devices/pcbios/0/Config/DmiBIOSFirmwareMinor" 4 1135 VBoxManage setextradata " My VM"1129 VBoxManage setextradata "VM name" 1136 1130 "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVendor" "System Vendor" 1137 VBoxManage setextradata " My VM"1131 VBoxManage setextradata "VM name" 1138 1132 "VBoxInternal/Devices/pcbios/0/Config/DmiSystemProduct" "System Product" 1139 VBoxManage setextradata " My VM"1133 VBoxManage setextradata "VM name" 1140 1134 "VBoxInternal/Devices/pcbios/0/Config/DmiSystemVersion" "System Version" 1141 VBoxManage setextradata " My VM"1135 VBoxManage setextradata "VM name" 1142 1136 "VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "System Serial" 1143 VBoxManage setextradata " My VM"1137 VBoxManage setextradata "VM name" 1144 1138 "VBoxInternal/Devices/pcbios/0/Config/DmiSystemFamily" "System Family" 1145 VBoxManage setextradata " My VM"1139 VBoxManage setextradata "VM name" 1146 1140 "VBoxInternal/Devices/pcbios/0/Config/DmiSystemUuid" 1147 1141 "9852bf98-b83c-49db-a8de-182c42c7226b"</screen> … … 1157 1151 <computeroutput>VERR_CFGM_NOT_STRING</computeroutput> error. In that case, 1158 1152 use <computeroutput>"string:<value>"</computeroutput>, for instance 1159 <screen>VBoxManage setextradata " My VM"1153 <screen>VBoxManage setextradata "VM name" 1160 1154 "VBoxInternal/Devices/pcbios/0/Config/DmiSystemSerial" "string:1234"</screen></para> 1161 1155 … … 1186 1180 virtualization. To enable this mode use the following command:</para> 1187 1181 1188 <screen>VBoxManage setextradata " My VM" "VBoxInternal/TM/TSCTiedToExecution" 1</screen>1182 <screen>VBoxManage setextradata "VM name" "VBoxInternal/TM/TSCTiedToExecution" 1</screen> 1189 1183 1190 1184 <para>To revert to the default TSC handling mode use:</para> 1191 1185 1192 <screen>VBoxManage setextradata " My VM" "VBoxInternal/TM/TSCTiedToExecution"</screen>1186 <screen>VBoxManage setextradata "VM name" "VBoxInternal/TM/TSCTiedToExecution"</screen> 1193 1187 1194 1188 <para>Note that if you use the special TSC handling mode with a guest … … 1205 1199 down the (virtual) guest clock. This can be achieved as follows:</para> 1206 1200 1207 <screen>VBoxManage setextradata "My VM" 1208 "VBoxInternal/TM/WarpDrivePercentage" 200</screen> 1201 <screen>VBoxManage setextradata "VM name" "VBoxInternal/TM/WarpDrivePercentage" 200</screen> 1209 1202 1210 1203 <para>The above example will double the speed of the guest clock 1211 1204 while</para> 1212 1205 1213 <screen>VBoxManage setextradata "My VM" 1214 "VBoxInternal/TM/WarpDrivePercentage" 50</screen> 1206 <screen>VBoxManage setextradata "VM name" "VBoxInternal/TM/WarpDrivePercentage" 50</screen> 1215 1207 1216 1208 <para>will halve the speed of the guest clock. Note that changing the … … 1392 1384 <para>Furthermore, you can disallow certain actions when terminating a VM 1393 1385 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> 1395 1387 <para>where <computeroutput>OPTION</computeroutput> is one of the following 1396 1388 keywords:<glosslist> -
trunk/doc/manual/en_US/user_BasicConcepts.xml
r31735 r32331 1224 1224 1225 1225 <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> 1228 1227 Where N can be one of 0,1,2,3,4 referring to the 640x480, 800x600, 1229 1228 1024x768, 1280x1024, 1440x900 screen resolution respectively.</para> 1230 1229 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 1231 VBoxManage setextradata "VM name" VBoxInternal2/UgaVerticalResolution 900</screen></para> 1234 1232 1235 1233 <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 75 75 find it under "Start" -> "All Programs" -> "Accessories" 76 76 -> "Remote Desktop Connection". If you use the "Run" dialog, 77 you can type in options directly:<screen>mstsc 1.2.3.4[:3389] 77 you can type in options directly:<screen>mstsc 1.2.3.4[:3389]</screen></para> 78 78 79 79 <para>Replace "1.2.3.4" with the host IP address, and 3389 with a … … 388 388 <computeroutput>VBoxManage setproperty vrdpauthlibrary "VRDPAuthSimple"</computeroutput>. 389 389 To enable the library for a VM, switch authentication to external using 390 <computeroutput>VBoxManage modifyvm "VM NAME" --vrdpauthtype external</computeroutput>.390 <computeroutput>VBoxManage modifyvm "VM name" --vrdpauthtype external</computeroutput>. 391 391 Last but not least, you have to configure users and passwords. Here is an example 392 392 for the user "john" with the password "secret": 393 <computeroutput>VBoxManage setextradata "VM NAME" "VRDPAuthSimple/users/john" "secret"</computeroutput>393 <computeroutput>VBoxManage setextradata "VM name" "VRDPAuthSimple/users/john" "secret"</computeroutput> 394 394 To specify an empty password, use the special reserved value 395 395 <computeroutput>[NULL]</computeroutput>. … … 528 528 <para>The following commands change corresponding server settings:</para> 529 529 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 531 VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableInput" 1 532 VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableUSB" 1 533 VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableAudio" 1 534 VBoxManage setextradata "VM name" "VRDP/Feature/Client/DisableClipboard" 1</screen> 535 535 536 536 <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> 538 538 </sect2> 539 539 </sect1> -
trunk/doc/manual/en_US/user_GuestAdditions.xml
r31735 r32331 329 329 launcher:</para> 330 330 331 <screen> 332 VBoxWindowsAdditions.exe /S 333 </screen> 331 <screen>VBoxWindowsAdditions.exe /S</screen> 334 332 335 333 <para>This automatically installs the right files and drivers for the … … 345 343 consult the command line help by using the command:</para> 346 344 347 <screen> 348 VBoxWindowsAdditions.exe /? 349 </screen> 345 <screen>VBoxWindowsAdditions.exe /?</screen> 350 346 </sect3> 351 347 … … 782 778 the current Guest Additions with the "uninstall" parameter from the 783 779 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> 787 781 <para>(substituting <computeroutput>VBoxLinuxAdditions-amd64</computeroutput> 788 782 on a 64-bit guest). While this will normally work … … 1397 1391 Name: /VirtualBox/GuestInfo/OS/Version, value: #59-Ubuntu SMP Thu Jan 28 01:23:03 UTC 2010, 1398 1392 timestamp: 1265813265836305000, flags: <NULL> 1399 ... 1400 </screen></para> 1393 ...</screen></para> 1401 1394 1402 1395 <para>For more complex needs, you can use the VirtualBox programming -
trunk/doc/manual/en_US/user_KnownIssues.xml
r31735 r32331 196 196 that there is a lot of output and not all errors are fatal (they 197 197 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>To199 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> 200 200 </listitem> 201 201 </itemizedlist></para> -
trunk/doc/manual/en_US/user_Storage.xml
r31735 r32331 920 920 address, the IP configuration and the Internal Networking name 921 921 ("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 923 VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/Config/MAC 08:00:27:01:02:0f 924 VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/Config/IP 10.0.9.1 925 VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/Config/Netmask 255.255.255.0 926 VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/LUN#0/Driver IntNet 927 VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/LUN#0/Config/Network MyIntNet 928 VBoxManage setextradata "VM name" VBoxInternal/Devices/IntNetIP/0/LUN#0/Config/IsService 1</screen></para> 936 929 937 930 <para>Finally the iSCSI disk must be registered with the 938 931 <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> 941 933 942 934 <para>The target address must be specified as a numeric IP address, as -
trunk/doc/manual/en_US/user_Troubleshooting.xml
r31735 r32331 578 578 command:</para> 579 579 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> 582 581 583 582 <para>This sets the delay to one millisecond. In case this doesn't help,
Note:
See TracChangeset
for help on using the changeset viewer.