At certain point of time, realizing that the vboxnet0 interface is not exist. Well, it can be seen by executing the following command where the operating system used as an example in this context where it is actually the real output from a host installed with the operating system of Linux Ubuntu 16.04 is shown as follows :
root@hostname:~$ /sbin/ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:15887 errors:0 dropped:0 overruns:0 frame:0 TX packets:15887 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:15338390 (15.3 MB) TX bytes:15338390 (15.3 MB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlp1s0 Link encap:Ethernet HWaddr 5c:51:4f:70:2e:07 inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::5b52:1e14:2634:cff9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:42855 errors:0 dropped:0 overruns:0 frame:0 TX packets:27998 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:44255969 (44.2 MB) TX bytes:4510947 (4.5 MB) root@hostname:~$
This is actually happened because of the vboxnet0 which is in my opinion specifically used in the Host-Only Adapter mode currently is not used in any running Virtual Machine created in the Virtualbox. So, the actual ‘vboxnet0’ is in my case, it will appear upon the usage of the Host-Only Adapter in one running Virtual Machine at least. Below is the actual network configuration of a running operating system :
After activating it, the following is the actual vboxnet0 network interface display in the host :
user@hostname:~$ /sbin/ifconfig lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:658834 errors:0 dropped:0 overruns:0 frame:0 TX packets:658834 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:637007198 (637.0 MB) TX bytes:637007198 (637.0 MB) vboxnet0 Link encap:Ethernet HWaddr 0a:00:27:00:00:00 inet addr:192.168.56.1 Bcast:192.168.56.255 Mask:255.255.255.0 inet6 addr: fe80::800:27ff:fe00:0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:543 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:136937 (136.9 KB) virbr0 Link encap:Ethernet HWaddr 00:00:00:00:00:00 inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0 UP BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) wlp1s0 Link encap:Ethernet HWaddr 5c:51:4f:70:2e:07 inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::5b52:1e14:2634:cff9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1158399 errors:0 dropped:0 overruns:0 frame:0 TX packets:681010 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1494092803 (1.4 GB) TX bytes:87981525 (87.9 MB) user@hostname:~$
So, in my opinion, unless the vboxnet0 is used and it is active and run in at least one Virtual Machine, it will not be shown in the list of network interface available in the host.