Index: /trunk/doc/manual/en_US/user_AdvancedTopics.xml
===================================================================
--- /trunk/doc/manual/en_US/user_AdvancedTopics.xml (revision 54985)
+++ /trunk/doc/manual/en_US/user_AdvancedTopics.xml (revision 54986)
@@ -1837,39 +1837,54 @@
By default VirtualBox provides you with one host-only network
interface. Adding more host-only network interfaces on Solaris hosts
- requires manual configuration. Here's how to add two more host-only
- network interfaces.
-
- You first need to stop all running VMs and unplumb all existing
- "vboxnet" interfaces. Execute the following commands as root:
+ requires manual configuration. Here's how to add another host-only
+ network interface.
+
+ Begin by stopping all running VMs. Then, unplumb the existing
+ "vboxnet0" interface by execute the following command as root:
ifconfig vboxnet0 unplumb
- Once you make sure all vboxnet interfaces are unplumbed, remove the
- driver using:
-
- rem_drv vboxnetthen edit the file
- /platform/i86pc/kernel/drv/vboxnet.conf
- and add a line for the new interfaces:
-
- name="vboxnet" parent="pseudo" instance=1;
-name="vboxnet" parent="pseudo" instance=2;Add as many of these lines
- as required and make sure to assign a unique instance number.
+ If you have several vboxnet interfaces, you will need to unplumb
+ all of them. Once all vboxnet interfaces are unplumbed, remove the
+ driver by executing the following command as root:
+
+ rem_drv vboxnet
- For each instance that you have added, create a corresponding
- file "/etc/hostname.vboxnetX" where "X" is the instance number. In the
- above example, we would have to create "/etc/hostname.vboxnet1".
-
- Specify the IP address you want assigned to the interface in the
- hostname.vboxnetX file. In the above example, we would use 192.168.57.1.
-
- Finally, reload the vboxnet driver using:
-
- add_drv vboxnetNow plumb all the interfaces using
- ifconfig vboxnetX plumb (where X can be
- 0, 1 or 2 in this case) and once plumbed you can then configure the
- interface like any other network interface.
-
- To make your newly added interfaces' settings persistent across
- reboots you will need to edit the files
+ Edit the file /platform/i86pc/kernel/drv/vboxnet.conf
+ and add a line for the new interface we want to add as shown below:
+
+ name="vboxnet" parent="pseudo" instance=1;
+name="vboxnet" parent="pseudo" instance=2;
+
+ Add as many of these lines as required with each line having a
+ unique instance number.
+
+ Next, reload the vboxnet driver by executing the following command
+ as root:
+
+ add_drv vboxnet
+
+ On Solaris 11.1 and newer hosts you may want to rename the default
+ vanity interface name. To check what name has been assigned, execute:
+
+ dladm show-phys
+LINK MEDIA STATE SPEED DUPLEX DEVICE
+net0 Ethernet up 100 full e1000g0
+net2 Ethernet up 1000 full vboxnet1
+net1 Ethernet up 1000 full vboxnet0
+
+ In the above example, we can rename "net2" to "vboxnet1" before
+ proceeding to plumb the interface. This can be done by executing as root:
+
+ dladm rename-link net2 vboxnet1
+
+ Now plumb all the interfaces using
+ ifconfig vboxnetX plumb (where 'X' would
+ be 1 in this case). Once the interface is plumbed, it may be configured
+ like any other network interface. Refer to the
+ ifconfig documentation for further details.
+
+ To make the newly added interfaces' settings persistent across
+ reboots, you will need to edit the files
/etc/inet/netmasks, and if you are using NWAM
/etc/nwam/llp and add the appropriate
@@ -2620,5 +2635,5 @@
-
+
@@ -2829,5 +2844,5 @@
open a bug report.
This behavior can be configured:
-
+
VBoxManage setextradata "VM name" GUI/GuruMeditationHandler MODE
@@ -2879,5 +2894,5 @@
VBoxManage setextradata "VM name" GUI/MouseCapturePolicy MODE
-
+
where MODE is one of the
following keywords: