I am attempting to install the minimal installation of CentOS7 32 bit in order to build the rpms for the 32 bit version of wine. Early on in the install I can make my network & hostname choices. When I have built 64 bit VMs of CentOS7 this part of the install defaults to Ethernet. With the 32 bit version I have a choice of:

Bond
Bridge
Team
VLAN

I have tried each and cannot configure anything which will connect to my network. Can someone offer some advice?

TIA,

Ken

Could you please give more information about your overall computer setup, as for example: host OS, 32 bit or 64 bit; version of VMWare Workstation you are using; actual network cards installed on your computer; type of computer you are using, as in laptop, desktop, etc; etc.

Thanks xode,

This issue has dropped down in priority as I resolved my 32 bit wine issue - actually I disposed of the offending VM and created a new one. My RPM set also installed fine on my new physical machine. Still, it would be interesting to sort this out. I might mention that the CentOS-7-i386-Minimal-1511.iso will NOT identify the network card in an old Pentium 4 machine. CentOS-7-i386-LiveGNOME-1511.iso installed fine on that physical machine, networking and all.

Neither of those iso files will find the network "device" in VMWare nor will CentOS-7-i386-Everything-1511.iso. I have not tried the everything image on the ancient physical machine.

My host PC is:

Dell Studio XPS 8000; i7-860; 8 GB RAM; 250 GB SSD; Nvidia Quadro K420; onboard NIC; running CentOS 6.8 64 bit

VMWare Player 12.5.2

I do not think the hardware NIC is the issue. I have installed CentOS 7 64 bit on this computer and it detected it just fine. Also, VMWare builds its own networking for the guests to talk to and then VMWare talks to the host NIC (as I understand it).

I have built a VM with Ubuntu 16.04 32 bit on this host and it communicated just fine. It sort of looks like something strange in the CentOS 7 32 bit build.

Ken

Unless you did some kind of pci passthrough on the client then the host hardware has minimal effect. The setting of virtual nic may be an issue. Using bridged or nat is common.

Look at lspci on client. Use other network tools like ip command.

Thanks jefro,

Sorry for not getting back to you sooner. This issue has fallen off the radar as I was able to install my home made 32 bit wine after reinstalling the OS on my new machine and a new CentOS 7 VM. I did manage to install CentOS 7 32 bit on my ancient PC and it did have networking as I recall. I think it is a VMWare issue. I have an outstanding bug from RedHat 8 where Anaconda would detect and install my external modem but after the first boot the modem was gone. And when installing CentOS 6 on my current (ca. 2009) PC it would not detect the on-board NIC. I had to install an old NIC, install the OS, update and then the on-board NIC worked fine. I then removed the old NIC. Perhaps I need to see if I still have it and install it before building the 23 bit VM. Or perhaps not

Thanks again,

Ken

But it gets even better. I just (accidentally) built a VM from the CentOS 7 32 bit minimal install image - complete with networking - updated it, installed a couple of packages and spent 45 minutes trying to figure out why I could not add the epel repo. When I deleted it and started over I found that I had booted from the 32 bit image instead of the 64 bit as I had intended.

Ken