Unix & Linux Stack Exchange is a question and answer site for users of Linux, FreeBSD and other Un*x-like operating systems. It only takes a minute to sign up.
Sign up to join this community
I just now installed Cent OS 7 on my VMware 8 and I am not able to connect it to a network.
I checked the VM network and its mapped to the physical NIC. The same setting work like charm on my CentOS 5 running on VM8.
Running the ip a command shows the following output:
You have to activate the interface. One way of doing that is with Network Manager's utility nmtui.
Open nmtui with:
$ sudo nmtui
And you'll get a text based interface like this:
Navigate by using TAB and ENTER.
In nmtui you can activate your interface, edit connection's and set hostname.
After you're done, restart network with:
$ sudo systemctl restart network
ifcfg-eth* in /etc/sysconfig/network-scripts/ for the line ONBOOT. That should be set to yes.
In my case, I installed two CentOS virtual machine by using VMware Player (Host OS: CentOS7). I found no IP address for both of virtual machines. The IP address set by following the below procedures.
Check the current connection on your VM:
# nmcli con show
NAME UUID TYPE DEVICE
ens33 xxxxxx ethernet ---
The network is not activated yet after virtual machine installation.
Lets, activate the network connection by using this command:
# nmcli con up ens33
Connection successfully activated xxxxxxx
Check whether the newly activated network is ready:
# nmcli con show
NAME UUID TYPE DEVICE
ens33 xxxxxx ethernet ens33
Now check your IP address on CentOS virtual machine:
# ip address show | grep inet
inet 127.0.0.1/8 scope host lo
inet6 ::1/128 scope host
inet 192.168.xxx.xxx/xx brd 192.168.xxx.xxx scope global noprefixroute dynamic ens33
inet6 xxxxxxx
Your IP address for the CentOS virtual machine is : 192.168.xxx.xxx/xx
nmcli d
Output:
DEVICE TYPE STATE CONNECTION
virbr0 bridge unmanaged --
ens33 ethernet unmanaged --
lo loopback unmanaged --
virbr0-nic tun unmanaged --
ip link set dev ens33 up
dhclient -v ens33
Output:
Internet Systems Consortium DHCP Client 4.2.5
Copyright 2004-2013 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/ens33/00:0c:29:6d:49:7e
Sending on LPF/ens33/00:0c:29:6d:49:7e
Sending on Socket/fallback
DHCPDISCOVER on ens33 to 255.255.255.255 port 67 interval 5 (xid=0x7ea0b970)
DHCPREQUEST on ens33 to 255.255.255.255 port 67 (xid=0x7ea0b970)
DHCPOFFER from 192.168.153.254
DHCPACK from 192.168.153.254 (xid=0x7ea0b970)
bound to 192.168.153.128 -- renewal in 724 seconds
Try executing ifconfig now
I user bridged network,you should attach your guest OS's network interface to host interface,you need edit vmware's network editor:
Edit -> Virtual Network Editor -> bridged to host interface
picture:
Open my.vmx which contain your VM configurations and Added the following line to my.vmx:
ethernet0.virtualDev = "e1000"
My problem was solved by this line.
In the nmtui, edit the connection and then select Automatically Connect check box. Restart the network and you should be back in business :-)
I had a similar issue with a VM running Red Hat Enterprise Linux (RHEL) V6.4 with VMWare 10. I was able to fix it using the "Restore Defaults" button in VMWare's Virtual Network Editor. In my case, somehow the bridged network had been deleted at some time in the past.
For me, the problem was "onboot" parameter in the interface network script (/etc/sysconfig/network-scripts/ifcfg-enp0s3).
To fix I, changed it from "no" to "yes"
All scenario (following @KRT)
Step 1: to check ip address statement by ip a or ifconfig
Step 2: to use "sudo nmtui"
Step 3: to use TAB and ENTER for your choice (for my example "ENTER" to my virtual network card)
Step 4: to check "Automatically connect"
Step 5: to restart network
sudo systemctl restart network
Step 6: to check the network statement by ip a or ipconfig
