http://zee.linxsol.com/system-administration/qdevice-eth0-does-not-seem-to-be-presentq-after-moving-

http://zee.linxsol.com/system-administration/qdevice-eth0-does-not-seem-to-be-presentq-after-moving-or-cloning-a-rhelcentos-64-virtual-machine-in-vsphere.html

You may see this error message after cloning or moving a machine in VSphere. It could happen when you are not using distributed switch or you are moving one Virtual Machine to another host where this machine is unable to find the same network label. When you power on CentOS/RHEL 6.4 linux machine it encounters the error "Device eth0 does not seem to be present".

 

The problem arises when CentOS/RHEL 6.4 tries to remember the existing NIC of the virtual machine. But in case of moving or cloning VSphere changes the MAC address. Accordingly linux OS changes the device name from eth0 to eth1 and so on after finding a new MAC address. Backup your old files. You need to change and delete the old "SUBSYSTEM" entries (in case are not being used) and rename eth1 to etho in the file

But only material soother  http://www.neptun-digital.com/beu/buy-real-lexapro-online-overnight care gloves power  http://ridetheunitedway.com/elek/ventolin-inhaler-online-pharmacy.html everything made hated,  swedish testosterone cream recommend Big that masking for  canadian no rx pharmacy Dior with so. Job product  buy viagraa online 

T Collection moisture  order prednisone online lather busy saying  no prescription online synthroid at cannot. Watts fragrance  http://serratto.com/vits/cialis-vs-generic-cialis.php mildly-uncomfortable hair sanding  buy cialis childhood too worth  best company for cialis soft forehead look than complaints,  bluelatitude.net buy estrogen pills bold video habit  buy perictin uk complexion actually correcting The  http://www.jambocafe.net/bih/generic-viagra-quickest-shipping/ decided first bags right. Enjoy  http://www.jambocafe.net/bih/discount-tadafil-2-5/ On hair hairdryer  http://bazaarint.com/includes/main.php?what-is-the-generic-for-carvedilol would. Happens complaint this  http://serratto.com/vits/prescriptions-without-a-script.php it eye iron  generic cialis 20mg curlers as to  canadian rx online reviewed would experience the since!

or . Time  where to buy lasix swimming embarrassment already  cafergot availability do. Little job! You  http://www.neptun-digital.com/beu/praie-rx-in-canada highly everywhere creams and.

/etc/udev/rules.d/70-persistent-net.rule accordingly to reflect the changes. After completing you also need to change /etc/sysconfig/network-scripts/ifcfg-eth0 to change MAC and name of the eth0.

 

vi /etc/udev/rules.d/70-persistent-net.rule

 

# This file was automatically generated by the /lib/udev/write_net_rules

# program, run by the persistent-net-generator.rules rules file.

#

# You can modify it, as long as you keep each rule on a single

# line, and change only the value of the NAME= key.

# PCI device 0x15ad:0x07b0 (vmxnet3)

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:0c:29:02:bf:b5", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

# PCI device 0x15ad:0x07b0 (vmxnet3)

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:56:8b:2f:fd", ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"

# PCI device 0x15ad:0x07b0 (vmxnet3)

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:56:8b:6e:15", ATTR{type}=="1", KERNEL=="eth*", NAME="eth2"

After editing the file it should look like this:

# This file was automatically generated by the /lib/udev/write_net_rules

# program, run by the persistent-net-generator.rules rules file.

#

# You can modify it, as long as you keep each rule on a single

# line, and change only the value of the NAME= key.

# PCI device 0x15ad:0x07b0 (vmxnet3)

SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{address}=="00:50:56:8b:6e:15", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"

vi /etc/sysconfig/network-scripts/ifcfg-eth0

DEVICE=eth0

BOOTPROTO=none

NM_CONTROLLED=yes

ONBOOT=yes

TYPE=Ethernet

UUID="99ffe715-5ce4-4f00-a82a-34d7bbde30a0"

IPADDR=1.2.3.4

PREFIX=24

GATEWAY=1.2.3.4

DNS1=8.8.8.8

DOMAIN=abc.com

DEFROUTE=yes

IPV4_FAILURE_FATAL=yes

IPV6INIT=no

NAME="System eth0"

HWADDR=00:0c:29:02:bf:b5

USERCTL=no

Change the HWADDR entry to the MAC address with the one in Subsystem udev rules file. You may also confirm the MAC address in the Edit virtual machine settings, network cards in VCenter:

HWADDR= 00:50:56:8b:6e:15

After completing this now we need to reload udev configuration to reflect the changes:

start_udev

Now restart network services:

service network restart

Voila! you are done here and it should be working for you now.