CentOS7 Minimal Installation On Vmware Missing Network Interface

Home » CentOS » CentOS7 Minimal Installation On Vmware Missing Network Interface
CentOS 6 Comments

Hi there, I’m playing with CentOS 7 (don’t know if it’s recommended at all have this one as a development server as maybe is not stable enough yet)
and I installed it on a Vmware VM with two network interfaces: one as a bridged connected directly to the physical network and replicating the network state and the second one as a host only interface (the one I use to manage the VM) so after I got the CentOS installed I can see the first interface but not the second one and I don’t know how to enable it. If I
run the command ifconfig -a this is what I see:

eno16777728: flagsA63 mtu 1500
inet 192.168.1.112 netmask 255.255.255.0 broadcast 192.168.1.255
inet6 fe80::250:56ff:fe2e:e245 prefixlen 64 scopeid 0x20 ether 00:50:56:2e:e2:45 txqueuelen 1000 (Ethernet)
RX packets 126 bytes 17122 (16.7 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 83 bytes 12627 (12.3 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

lo: flagss mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10
loop txqueuelen 0 (Local Loopback)
RX packets 8 bytes 552 (552.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 8 bytes 552 (552.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

What I need to do in order to enable the other interface? Also how I change the name eno16777728 to eth0-internet without get down my server?

Thanks in advace

6 thoughts on - CentOS7 Minimal Installation On Vmware Missing Network Interface

  • This is something of a loaded question and also quite dependent on what you are doing. If the server is very critical, I would probably wait until 7.1 or 7.2. If the server is not very critical, then sure, use EL7
    and start learning it (and report bugs! :) ).

    If ‘ifconfig -a’ doesn’t see it, the kernel probably doesn’t, either. Do you see it in lspci or dmidecode? If not, I would look at the hypervisor for a problem.

    Yes you can do it without rebooting, but it still requires taking the network down.

    I wrote this a while ago:

    https://alteeve.ca/w/Changing_Ethernet_Device_Names_in_EL7_and_Fedora_15%2B

    It probably needs to be updated/cleaned up, but it should be good enough to help you.

    digimer

  • Which configuration you need? The one I made at Windows side? The Vmware is running on Windows 7 (I didn’t send here since I don’t know if I can attach images to this list and to not be banned so I omit then)

    What about if I didn’t see vmxnet3?

    [root@webserver ~]# lsmod | grep vm vmw_balloon 13415 0
    vmw_vmci 67106 0
    vmwgfx 135143 1
    ttm 83948 1 vmwgfx drm 297829 2 ttm,vmwgfx

  • It’s not critical, just a development server I’ll like to configure in order to start learn a bit CentOS 7 (I’m not a System Administrator expert but a developer)

    As I said above I’m not a expert but I did “man dmidecode” since lspci isn’t available and I can’t find a TYPE for see network interfaces also I
    do not know if the output is related to motherboard (the one I have) or is related to emulated board (if this has sense), so what command should I run to give you proper info?

    I’ll take a look in a few minutes after system updates complete

  • This is what I have in .vxm file:

    ethernet0.present = “TRUE”
    ethernet0.virtualDev = “e1000”
    ethernet0.wakeOnPcktRcv = “FALSE”
    ethernet0.addressType = “static”
    ethernet0.address = “00:50:56:2E:E2:45”
    ethernet0.linkStatePropagation.enable = “TRUE”
    ethernet1.present = “TRUE”
    ethernet1.vnet = “VMnet1”
    ethernet1.connectionType = “custom”
    ethernet1.wakeOnPcktRcv = “FALSE”
    ethernet1.addressType = “static”
    ethernet1.address = “00:50:56:3F:86:30”

    And this is how I configured the network interface at Vmware http://imgur.com/GSX9N6c the weird part here is the same network configuration works fine in a CentOS 6.5 VM

  • No worries about not being an admin.

    To find a package that provides a certain tool, you can do this:

    [root@rhel7-builder ~]# yum provides “*/lspci”
    Loaded plugins: product-id, subscription-manager Repodata is over 2 weeks old. Install yum-cron? Or run: yum makecache fast rhel-7-server-rpms/7Server/x86_64/filelists_db

    | 3.7 MB 00:00:01
    rhel-ha-for-rhel-7-server-rpms/7Server/x86_64/filelists_db

    | 50 kB 00:00:00
    rhel-rs-for-rhel-7-server-rpms/7Server/x86_64/filelists_db

    | 55 kB 00:00:00
    rhel-sap-for-rhel-7-server-rpms/7Server/x86_64/filelists_db

    | 3.7 kB 00:00:00
    pciutils-3.2.1-4.el7.x86_64 : PCI bus related utilities Repo : rhel-7-server-rpms Matched from:
    Filename : /usr/sbin/lspci

    This shows that you can get ‘lspci’ by installing the ‘pciutils’ program.

    As for “hardware”, from inside the VM, only the emulated hardware can be seen, not the real hardware. So lspci, dmidecode and similar tools will report on the (virtual) hardware created by VMWare.

    Sorry, but I can’t provide any advice for VMWare, I use KVM.

    Let me know if you have trouble.

    Cheers!

  • Thanks now with the solution you give me I’m able to see the network interface and yes I learn something new today so thanks

LEAVE A COMMENT