Clone error when re-initailizing MAC as well

[Robert O]

I don't know if something went buggy on my computer, or if anyone else has had a problem with this.

Since 4.3.12 (last version i just upgraded from.. to 4.3.20) I noticed that with CentOS 6 (.5) if i copy the VM with re-initialize MAC eth0 turns into eth1... and so on... and any #service network restart will get an error for eth0 (even though there' no eth0). I still get this in 4.3.20.

I find I have to clone with that unchecked --manually change the MACs, or create a new machine then using CloneVDI for cloning the HD of the old machine to the new.

Is this something there's a permanent solution for? I've tried the tips in the other threads on missing eth0/eth0 change to eth1... but none of it works for me. I can turn on and off various combinations of the network cards (or modes) and the clones never get eth0 back.

EDIT. Even worse I've notice that Adaptor 1 turned into eth2, and Adaptor 2 turned into eth1 on some clones, and I get random networking errors trying to set the interfaces (/etc/sysconfig/network-scripts/ifcfg-eth1 /.../ifcg-eth2 ) including the settings applying to both, or neither interface.

[mpack]

That's standard behaviour with any Linux, it has nothing to do with VirtualBox at all. Linux assumes that a new MAC address means a new network adapter, which it call eth<# of last known NIC +1>. There's some etc/xxxx file that you delete if you want it to forget about old NICs. I suggest that you make Google your friend.

[Robert O]

That's standard behaviour with any Linux, it has nothing to do with VirtualBox at all. Linux assumes that a new MAC address means a new network adapter, which it call eth<# of last known NIC +1>. There's some etc/xxxx file that you delete if you want it to forget about old NICs. I suggest that you make Google your friend.

Yes I finally found it using dmesg. "...changed eth0 to eth2..."
Made changes in /etc/network/interfaces, /etc/sysconfig/network-scripts/ifcfg-eth0 and /etc/sysconfig/network-scripts/ifcfg-eth1
I edited /etc/udev/rules.d/70-persistent-net.rules... rebooted... Success!
I've deleted it and I have also ln -l /etc/udev/rules.d/70-persistent-net.rules > /dev/null
Hopefully that will keep other problems from cropping up.