VMware Cloud Community
btrimble
Contributor
Contributor

Workstation6 & ESX 3.0

I'm attempting to setup an ESX Environment within Workstation 6 and am having some problems with the NIC initialization during bootup.

The specs are as follows:

The host machine is a Dell P.E 1900 with the following NICs:

1x Broadcom NetXtreme II GigE

1x Dual Port Intel PRO/1000 PT

I had the NICs teamed, but have since disabled that to see if the vNIC would be initialized during bootup of the ESX box, and unfortunately it had no effect.

The error message I get when entering the Service Console is:

Bringing up interface eth0: pcnet32 device eth0 does not seem to be present, delaying initialization.

If anyone knows any tricks or troubleshooting techniques to get more information as to what might be the problem it would be much appreciated.

Thanks.

~Brian

Reply
0 Kudos
11 Replies
admin
Immortal
Immortal

Here's an excellent whitepaper that covers everything you need to know about getting ESX3 working inside Workstation 6.

http://www.xtravirt.com/index.php?option=com_remository&Itemid=75&func=fileinfo&id=9

Reply
0 Kudos
btrimble
Contributor
Contributor

This looks excellent.

Thanks for the prompt assistance.

~Brian

Reply
0 Kudos
rtaverae
Enthusiast
Enthusiast

Hi guys,

I followed up the xtravit paper line by line and ESX 3.x installs and boots like a charm. My problem is, have no networking.....

If I check my setup, everithing seems to be ok, but no network

response, the loopback interface and the service console interface

responds to ping, but nothing else.... nor from service console, not

from any other machine trying to reach the service console....

I'm running workstation 6.0 for linux on a Dell XPS1210 VT enabled....

Any clue?

Reply
0 Kudos
Santhosh_vmware

have you tried setting network to "private network with host" in workstation 6,that way esx host will automatically get its ip address.

Reply
0 Kudos
rtaverae
Enthusiast
Enthusiast

I did it with NAT, but I'll try with Host only to see what happpen...

Stay tuned....

El Tuesday 16 October 2007 00:29:48 escribió:

Rene Tavera,

A new message was posted in the thread "Workstation6 & ESX 3.0":

http://communities.vmware.com/message/771023

Author : Santhosh_vmware

Profile : http://communities.vmware.com/people/Santhosh_vmware

Message:

Reply
0 Kudos
Dave_Mishchenko
Immortal
Immortal

You'll want to set the virtual NIC(s) to be bridged. That way the ESX VM will appear to be on the LAN just like any other server or PC.

Reply
0 Kudos
rtaverae
Enthusiast
Enthusiast

That was my first choice, but no networking....

If I ping to the local IP (ServiceConsolo, not loopback) can reach two ort

three ICMP responds and then stops.

If I ping to any other host in the net I've got nothing....

the same to the bridged and the NAT vm adapters...

El Tuesday 16 October 2007 13:52:32 escribió:

Rene Tavera,

A new message was posted in the thread "Workstation6 & ESX 3.0":

http://communities.vmware.com/message/771605

Author : Dave.Mishchenko

Profile : http://communities.vmware.com/people/Dave.Mishchenko

Message:

Reply
0 Kudos
virtualdud3
Expert
Expert

I'm running WS6 on top of Linux (CentOS 5), when I login as "non-root" (which I always do), I can start WS6, and boot the ESX guest, but I am unable to ping any IP other than the vswif and vmkernel IP addresses UNLESS I launch WS6 via the command line $sudo /usr/bin/vmware.

Interestingly, if I recall correctly, if I boot the ESX VM into "Service Console only", I am able to ping outside of the VM (even when I launch WS6 as non-root).

So, try either logging-in as root or launching WS6 via the sudo command and let us know if doing so allows the networking to function properly

I am curious to know the results...

############### Under no circumstances are you to award me any points. Thanks!!!
Reply
0 Kudos
Dave_Mishchenko
Immortal
Immortal

Just looking at your original post you have this:

Bringing up interface eth0: pcnet32 device eth0 does not seem to be present, delaying initialization.

Edit the VMX for the VM and add this line: ethernet0.virtualDev = "e1000" . If you have more than one NIC then you'll want to add the line for each vNIC. Then ESX will see the vNIC as an Intel Pro1000 rather than a pcnet32 (Advanced Micro Devices (AMD) 79c970.

When you reboot ESX you should then see vmnic as an Intel Corp card with the e1000 driver loaded if you run esxcfg-nics -l . It may screw up the sernice console when you do this, so you may want to reinstall ESX.

Reply
0 Kudos
HenrikElm
Contributor
Contributor

I had it all running fine for a few weeks. After upgrading to WS 6.0.1, my virtual ESX servers does not boot anymore. I guess it was too good to be true in the long run. As 3.5 supports SATA, i HOPE that it will run nicely in WS 6.X.

/Henrik

Reply
0 Kudos
rtaverae
Enthusiast
Enthusiast

It works!, running Workstation as root brings the net alive!

Thanks guys.

Gracias a todos.

Reply
0 Kudos