shimmyt
Contributor
Contributor

ESX 3.5 as a Virtual Machine?

Jump to solution

Well I've started migrating our environment from ESX 3.5 to vSphre 4. Management has requested that we take a look at VMware View which is not fully compatible with vSphere yet. So In my brilliant thinking I thought it'd be pretty nifty to setup a small ESX 3.5 environment in our vSphere cluster. The vCenter server is complete and ESX 3.5 installed fine boots up and everything works great except I cannot access it via the network. I'm using the standard e1000 driver for it as well. If anyone could shine a light on this I would appreciate it.

0 Kudos
1 Solution

Accepted Solutions
admin
Immortal
Immortal

You probably need to configure your virtual switch to allow promiscuous mode. See KB 1004099.

View solution in original post

0 Kudos
4 Replies
admin
Immortal
Immortal

You probably need to configure your virtual switch to allow promiscuous mode. See KB 1004099.

0 Kudos
shimmyt
Contributor
Contributor

That is what did it! Now next question why would that make a difference? I have a theory but not 100% sure with it.

0 Kudos
AndreTheGiant
Immortal
Immortal

You probably need to configure your virtual switch to allow promiscuous mode

Right.

See also:

http://www.vcritical.com/2009/05/vmware-esx-4-can-even-virtualize-itself/

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
AndreTheGiant
Immortal
Immortal

That is what did it! Now next question why would that make a difference? I have a theory but not 100% sure with it.

Remember that vSwitch are similar as a bridge connection.

And they need to "listen" all the traffic to define the network topology.

Andre

Andre | http://about.me/amauro | http://vinfrastructure.it/ | @Andrea_Mauro
0 Kudos