Upgrade question (simple I think)
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,
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 |
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 |
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.
|
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 |
All times are GMT -5. The time now is 08:09 AM. |