[SOLVED] Upgrade question (simple I think)

anon190 · 07-06-2016, 09:01 AM

I just did an upgrade this morning and everything worked except one thing. I have a feeling it's outside of Slackware but I thought I would ask anyway.

Scenario is like so,

I am using VMWare Workstation 12
I was upgrading from Slackware 14.1
Before starting I shutdown and took a snapshot in VMware
Then I ran all commands from UPGRADE.txt file, everything worked
After reboot, eth0 is now eth126, & it doesn't get dhcp address
But all other NICs are okay (I have 4 total)
I don't notice any other udev rules for other NICs
I checked udev rules file, mac address is wrong in file for eth0

After that I moved the udev rules out of the way and rebooted, and now I have an eth0 again. I wonder, did VMware change my mac address? If not then anyone know how did the udev rules file get the wrong mac in it? I never cloned the machine (at least that I can remember, maybe I'm going crazy).

Thanks in advance.

V/r,
Bryan

kjhambrick · 07-07-2016, 03:30 AM

bryanatm --

I ran into this some time back.

VMWare Workstation DOES assign new MAC Addrs to Clones.

I can't find the VMWare KB Article on the topic but I do recall finding one several years ago.

HTH

-- kjh

anon190 · 07-07-2016, 08:35 AM

Yes it is understood about the clones, funny thing is that I only made a snapshot as opposed to a full clone. Maybe it did it underhandedly, anyway it's all working just a funny thing that happened.

kjhambrick · 07-07-2016, 08:43 AM

Yes ...

This bit me when I tried to clone a CentOS VM remotely.

VMWare changed the MAC Addr and it took a while to figure out why eth0 didn't hook up ( CentOS hard-codes the MAC in the /etc/sysconfig/network-scripts/ifcfg-ethX files ).

Fortunately I had access to the Console so I was able to fix it remotely.

Otherwise, I would have been stuck without access.

-- kjh