VMware Cloud Community
rt7500
Contributor
Contributor

vSphere ks.cfg wrong vmnic

When building ESX 3.5 with PXE and ks.cfg I was able to specifiy any eth interface for

--device= Then ESX would use that specified eth interface as vmnic0. This was good.

Now I'm using HP RDP 3.83 with ESX Supplement to PXE boot HP BL460c G6 to install vSphere4.

ks.cfg is configured to use the following for networking.

network --bootproto=dhcp --device=vmnic0 --hostname=%#*"select replace(,' ','') from computer where computer_id="%

vmnic0 is always the device listed with the lowest PCI number in esxcfg-nics -l

I can change --device= to what ever vmnic I desire and it builds just fine.

Is it possible with PXE, ks.cfg, and vSphere4 to specify what physical nic I want vmnic0 to be during the build process?

Tags (4)
Reply
0 Kudos
1 Reply
DSTAVERT
Immortal
Immortal

http://communities.vmware.com/message/1365413#1365413

Do a search on the forums for ks.cfg There seems to be a few returns. The above post might be worth replying to to.

-- David -- VMware Communities Moderator
Reply
0 Kudos