ESX server as a VM: adding a second vnic, how to?

[humanxbox]

Hi,

I have virtualized ESX server 3.0.1 with Vmware Workstation 6.0.0 build 45731. I am trying to add a second nic in the vmx file to that esx server can use extra nic for vmotion.. See the actual contents of the vmx file below. I tried with ethernet1 etc.. but no luck. Any idea ? Also where can i find the thread about virtualizing ESX server in this communitie ??? I have tried to search for this thread but no luck. To virtualize my esx server (for testing) i have the white paper of Xtravirt (Paul Davey) Please help---

config.version = "8"

virtualHW.version = "4"

numvcpus = "2"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "1132"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Red Hat Linux.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "auto detect"

ide1:0.deviceType = "cdrom-raw"

floppy0.autodetect = "TRUE"

ethernet0.present = "TRUE"

ethernet0.wakeOnPcktRcv = "FALSE"

svga.autodetect = "TRUE"

mks.keyboardFilter = "allow"

displayName = "ESXSERVER1"

guestOS = "redhat"

nvram = "Red Hat Linux.nvram"

deploymentPlatform = "windows"

virtualHW.productCompatibility = "esx"

tools.upgrade.policy = "useGlobal"

ethernet0.virtualDev = "e1000"

ethernet0.connectionType= "bridged"

ethernet0.addressType= "generated"

monitor_control.restrict_backdoor= "TRUE"

monitor_control.vt32= "TRUE"

ide1:0.autodetect = "TRUE"

floppy0.fileName = "A:"

isolation.tools.hgfs.disable = "TRUE"

ethernet0.generatedAddress = "00:0c:29:49:19:a0"

uuid.location = "56 4d 89 ec 0f bd 83 04-6c cf 03 b5 a7 49 19 a0"

uuid.bios = "56 4d 89 ec 0f bd 83 04-6c cf 03 b5 a7 49 19 a0"

scsi0:0.redo = ""

ethernet0.generatedAddressOffset = "0"

floppy0.startConnected = "FALSE"

tools.remindInstall = "TRUE"

scsi0:1.present = "TRUE"

scsi0:1.fileName = "C:\dump\Red Hat Linux-2.vmdk"

scsi0:1.redo = ""

ethernet1.present = "FALSE"

ethernet1.wakeOnPcktRcv = "FALSE"

ethernet1.addressType = "generated"

ethernet1.generatedAddress = "00:0c:29:49:19:aa"

ethernet1.generatedAddressOffset = "10"

config.version = "8"

virtualHW.version = "4"

numvcpus = "2"

scsi0.present = "TRUE"

scsi0.virtualDev = "lsilogic"

memsize = "1132"

scsi0:0.present = "TRUE"

scsi0:0.fileName = "Red Hat Linux.vmdk"

ide1:0.present = "TRUE"

ide1:0.fileName = "auto detect"

ide1:0.deviceType = "cdrom-raw"

floppy0.autodetect = "TRUE"

ethernet0.present = "TRUE"

ethernet0.wakeOnPcktRcv = "FALSE"

svga.autodetect = "TRUE"

mks.keyboardFilter = "allow"

displayName = "ESXSERVER1"

guestOS = "redhat"

nvram = "Red Hat Linux.nvram"

deploymentPlatform = "windows"

virtualHW.productCompatibility = "esx"

tools.upgrade.policy = "useGlobal"

ethernet0.virtualDev = "e1000"

ethernet0.connectionType= "bridged"

ethernet0.addressType= "generated"

monitor_control.restrict_backdoor= "TRUE"

monitor_control.vt32= "TRUE"

ide1:0.autodetect = "TRUE"

floppy0.fileName = "A:"

isolation.tools.hgfs.disable = "TRUE"

ethernet0.generatedAddress = "00:0c:29:49:19:a0"

uuid.location = "56 4d 89 ec 0f bd 83 04-6c cf 03 b5 a7 49 19 a0"

uuid.bios = "56 4d 89 ec 0f bd 83 04-6c cf 03 b5 a7 49 19 a0"

scsi0:0.redo = ""

ethernet0.generatedAddressOffset = "0"

floppy0.startConnected = "FALSE"

tools.remindInstall = "TRUE"

scsi0:1.present = "TRUE"

scsi0:1.fileName = "C:\dump\Red Hat Linux-2.vmdk"

scsi0:1.redo = ""

ethernet1.present = "FALSE"

ethernet1.wakeOnPcktRcv = "FALSE"

ethernet1.addressType = "generated"

ethernet1.generatedAddress = "00:0c:29:49:19:aa"

ethernet1.generatedAddressOffset = "10"

[Dave_Mishchenko]

I usually just add a NIC via the Workstation GUI and then edit it to be an Intel NIC with this line - ethernet1.virtualDev = "e1000"

You'll also want to change this line to TRUE - ethernet1.present = "FALSE". Once you've made those changes, boot up ESX and it will detect the card automatically (it'll likely reboot once).

[humanxbox]

Thanks for the fast reply. one more question: where can i find the best thread for virtualizing ESX server?

regards

[oreeh]

Here's the requested thread

Adding a NIC depends on the availability of NICs in the host.

If your host only has one NIC your only option is to add a second NIC using NAT or host-only.

[Dave_Mishchenko]

With just one NIC in the host you can still have more than one NIC in the VM that is set to bridged.

[oreeh]

Yes, but IMHO this doesn't make much sense.

[BUGCHK]

It makes sense to me if one wants to try out NIC teaming. Sure, you don't have a redundant physical connection, but maybe you want to play with the GUI or the scripting interface.