VirtualBox

Changeset 54986 in vbox


Ignore:
Timestamp:
Mar 27, 2015 11:03:02 AM (10 years ago)
Author:
vboxsync
Message:

doc/manual: Clarify instructions on adding new host-only interface on Solaris 11.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/doc/manual/en_US/user_AdvancedTopics.xml

    r54876 r54986  
    18371837    <para>By default VirtualBox provides you with one host-only network
    18381838    interface. Adding more host-only network interfaces on Solaris hosts
    1839     requires manual configuration. Here's how to add two more host-only
    1840     network interfaces.</para>
    1841 
    1842     <para>You first need to stop all running VMs and unplumb all existing
    1843     "vboxnet" interfaces. Execute the following commands as root:</para>
     1839    requires manual configuration. Here's how to add another host-only
     1840    network interface.</para>
     1841
     1842    <para>Begin by stopping all running VMs. Then, unplumb the existing
     1843    "vboxnet0" interface by execute the following command as root:</para>
    18441844
    18451845    <screen>ifconfig vboxnet0 unplumb</screen>
    18461846
    1847     <para>Once you make sure all vboxnet interfaces are unplumbed, remove the
    1848     driver using:</para>
    1849 
    1850     <para><screen>rem_drv vboxnet</screen>then edit the file
    1851     <computeroutput>/platform/i86pc/kernel/drv/vboxnet.conf</computeroutput>
    1852     and add a line for the new interfaces:</para>
    1853 
    1854     <para><screen>name="vboxnet" parent="pseudo" instance=1;
    1855 name="vboxnet" parent="pseudo" instance=2;</screen>Add as many of these lines
    1856     as required and make sure to assign a unique instance number.</para>
     1847    <para>If you have several vboxnet interfaces, you will need to unplumb
     1848    all of them. Once all vboxnet interfaces are unplumbed, remove the
     1849    driver by executing the following command as root:</para>
     1850
     1851    <screen>rem_drv vboxnet</screen>
    18571852   
    1858     <para>For each instance that you have added, create a corresponding
    1859     file "/etc/hostname.vboxnetX" where "X" is the instance number. In the
    1860     above example, we would have to create "/etc/hostname.vboxnet1".</para>
    1861 
    1862     <para>Specify the IP address you want assigned to the interface in the
    1863     hostname.vboxnetX file. In the above example, we would use 192.168.57.1.</para>
    1864 
    1865     <para>Finally, reload the vboxnet driver using:</para>
    1866 
    1867     <para><screen>add_drv vboxnet</screen>Now plumb all the interfaces using
    1868     <computeroutput>ifconfig vboxnetX plumb</computeroutput> (where X can be
    1869     0, 1 or 2 in this case) and once plumbed you can then configure the
    1870     interface like any other network interface.</para>
    1871 
    1872     <para>To make your newly added interfaces' settings persistent across
    1873     reboots you will need to edit the files
     1853    <para>Edit the file <computeroutput>/platform/i86pc/kernel/drv/vboxnet.conf</computeroutput>
     1854    and add a line for the new interface we want to add as shown below:</para>
     1855
     1856    <screen>name="vboxnet" parent="pseudo" instance=1;
     1857name="vboxnet" parent="pseudo" instance=2;</screen>
     1858
     1859    <para>Add as many of these lines as required with each line having a
     1860    unique instance number.</para>
     1861
     1862    <para>Next, reload the vboxnet driver by executing the following command
     1863    as root:</para>
     1864
     1865    <screen>add_drv vboxnet</screen>
     1866
     1867    <para>On Solaris 11.1 and newer hosts you may want to rename the default
     1868    vanity interface name. To check what name has been assigned, execute:</para>
     1869
     1870    <screen>dladm show-phys
     1871LINK              MEDIA                STATE      SPEED  DUPLEX    DEVICE
     1872net0              Ethernet             up         100    full      e1000g0
     1873net2              Ethernet             up         1000   full      vboxnet1
     1874net1              Ethernet             up         1000   full      vboxnet0</screen>
     1875
     1876    <para>In the above example, we can rename "net2" to "vboxnet1" before
     1877    proceeding to plumb the interface. This can be done by executing as root:</para>
     1878
     1879    <screen>dladm rename-link net2 vboxnet1</screen>
     1880
     1881    <para>Now plumb all the interfaces using
     1882    <computeroutput>ifconfig vboxnetX plumb</computeroutput> (where 'X' would
     1883    be 1 in this case). Once the interface is plumbed, it may be configured
     1884    like any other network interface. Refer to the
     1885    <computeroutput>ifconfig</computeroutput> documentation for further details.</para>
     1886
     1887    <para>To make the newly added interfaces' settings persistent across
     1888    reboots, you will need to edit the files
    18741889    <computeroutput>/etc/inet/netmasks</computeroutput>, and if you are using NWAM
    18751890    <computeroutput>/etc/nwam/llp</computeroutput> and add the appropriate
     
    26202635          </glossdef>
    26212636        </glossentry>
    2622      
     2637
    26232638      </glosslist>
    26242639
     
    28292844        open a bug report.</para>
    28302845      <para>This behavior can be configured:</para>
    2831        
     2846
    28322847      <para><screen>VBoxManage setextradata "VM name" GUI/GuruMeditationHandler MODE</screen></para>
    28332848
     
    28792894      </para>
    28802895      <para><screen>VBoxManage setextradata "VM name" GUI/MouseCapturePolicy MODE</screen></para>
    2881      
     2896
    28822897      <para>where <computeroutput>MODE</computeroutput> is one of the
    28832898        following keywords:</para><glosslist>
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