Good evening,
I have a server host, a Lenovo RD450 that doesn't appear to have a network adapter.
When I go to "Networking" I see a zero
I have a vmk0 nic that has a IP of 192.168.1.6
I have a port group
I have a vSwitch
I have all of the components I would think I need, but I still can't seem to setup virtual machines on this host because there is no network adapter when I click the setup new VM wizard.
Network Adapter 1 field when setting up the virtual machine through the wizard is blank.
What can I do to get a network adapter to populate?
I think I was able to fix it this morning.
I had to go in and add a new adapter.
Under Networking / Port Groups I created a new Port Group called VM Network.
After that, I went in and setup folders on the SAN for each server VM file.
When I created the Port Group VM Network, and tried the creation process for a new server, I got an error about the root directory that it was being installed to, so I browsed the data store and was able then to setup two new folders for the VM's.
Now I have successfully created the vmdk.
I am going to attempt to install.
The install errored because this is a OEM server.
I had to go in and modify the configuration for the server. I added the SMBIOS.reflectHost = True line to the configuration file.
When I went to reinstall the VM and get it going, everything works fine now.
The issues have been resolved.
Some how the VM Network port group got deleted which caused a chain reaction,
Hi,
Have you checked : VMware Compatibility Guide - I/O Device Search ?
I see on the Lenovo forum this : Solved: Lenovo vSphere ESXi 6.5 Customised Image release date - Lenovo Community
Have you tried that custom image?
If you did so, you need to define which network adapter is installed an inject the network drivers for that specific network card in ESXi.
If you did not try this custom image, please try this first!
Might be your NIC not listed in ESXi 6.5 HCL. During instalaltion you are able to assign IP address, but it will not bound to a NIC, and hence you will not be able to assign a NIC for a VM. If possible attach a HCL listed PCI NIC on the server, and check. Verify your NIC listed on Configure Management Network ---> Network Adapter section.
Agree on this, but I would suggest to see if the NIC is listed on the HCL and if so, use the custom image to install ESXi and then test again.
Did you install the VMware Tools for this new virtual machine created on the host?
If you said that you have:
1 vmk0 nic with 192.168.1.6 IP
1 port group
1 vSwitch
That means that your server or host's NIC is compatible with VMware but the VM O/S you're installing may not.
- Try a different O/S & make sure you install the tools
- Install the VMware Tools on the VM with no network adapter and confirm that the issue is resolved
Raul.
VMware VDI Administrator.
Stay Connected: Like > Share > Comment > Reply > Helpful > Answered
The Lenovo System X series systems have a custom ISO but the Lenovo RD series do not. I will see about finding the driver and injecting it. I installed this on another identical system and that one works. So something must be different between the two. I will advise this morning what looks to be different between the two.
I think I was able to fix it this morning.
I had to go in and add a new adapter.
Under Networking / Port Groups I created a new Port Group called VM Network.
After that, I went in and setup folders on the SAN for each server VM file.
When I created the Port Group VM Network, and tried the creation process for a new server, I got an error about the root directory that it was being installed to, so I browsed the data store and was able then to setup two new folders for the VM's.
Now I have successfully created the vmdk.
I am going to attempt to install.
The install errored because this is a OEM server.
I had to go in and modify the configuration for the server. I added the SMBIOS.reflectHost = True line to the configuration file.
When I went to reinstall the VM and get it going, everything works fine now.
The issues have been resolved.
Some how the VM Network port group got deleted which caused a chain reaction,
