Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have two vSwitches like this:

enter image description here

enter image description here

On vSwitch0, I have 3 VMs.

On vSwitch1, I have 1 VM.

I want to know if it is possible for the VM on vSwitch1 to communicate with a VM on vSwitch0 without going through the physical NIC (or vNIC), since it's on the same host. For instance, if I unplug the vmnic1, can LABUNIX01 still communicate with a VM on vSwitch0 since it's on the same physical host ?

share|improve this question
If both physical adapters go to the same LAN, just put both physical adapters, and all hosts on the same vSwitch. You do not need multiple vSwitches here. – SpacemanSpiff Jan 29 '13 at 22:47

No they cannot. Virtual machines on two different vSwitches can't communicate with each other, except through the physical network or through a virtual machine acting as a "bridge" between the vSwitches (one vNIC connected to each of the vSwitches).

share|improve this answer

Nope. They're separate and discrete vSwitches for a reason. Why are they separate in this case? If they need to remain separate, you could bridge them through an external switch or potentially add another vNIC from the relevant VM's and join them into a third vSwitch.

You can have all the VMs on the same vSwitch and use multiple uplinks to the physical switch for redundancy.

share|improve this answer

Assuming that there's a good reason for the current vSwitch separation, another option is to add a third vSwitch, with no uplink ports, then add virtual adapters to both VMs and assign them to the new vSwitch. You'll need to configure IP addressing, etc, but you'll have network connectivity without requiring access to to the physical network.

However, I believe this configuration (VM connected to a vSwitch with no uplink) will break vMotion, and VMs on the new vSwitch will not be eligible for vMotion.

share|improve this answer

Both joeqwerty's and ewwhite's answers are correct, for a solution you can set both nics to the same switch and add all the VMs, use different VLANs to segregate the networks.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.