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

There is documentation available for version 5 (I am running 4.1 per the title), but following the directions raises the error:

Incompatible device backing specified for device '0'.

upon clicking 'OK' to apply the settings. I don't really know if creating a serial port connection is necessary in this case, so I'm open to other options. All I really need is to ping the other VM and get a response.

I am new to networking, so the following information may or may not be helpful:

  • I have two virtual machines I want to connect, and each are RHEL 5.9.
  • They reside on the same vNetwork, but there is no physical switch associated with the vNetwork. There are unfortunately no more physical switches I can use to my knowledge but, if this is indeed the problem, I can see what I can do to get another. Obviously, virtual solutions are 'easier', not to mention cooler.
  • I actually lied; I need to connect three machines A, B, and C (all RHEL), however A and C should not be able to contact each other. (If A<B means server B serves client A, then A<B<C.) Thus, I think any solution connecting two machines should scale to this scenario, but I am new to this game.

If you would like more information, please comment and I'll do my best to provide it. :-)

share|improve this question
The documentation you link to refers to VMWare Workstation (a very old version of workstation too). There is no way you could have followed those instructions on an ESXi host. – Rex Jun 4 '13 at 17:23
@Rex Nice catch. That definitely explains why it wouldn't stick... – Sean Allred Jun 4 '13 at 17:24
Based on your other question (…) there is a firewall between the systems, they shouldn't be on the same virtual network at that point.. unless you are referring to the same vSwitch. These are close to being duplicate questions and might need to be merged. I would probably try to provide the info in your other question and keep the question together. – Rex Jun 4 '13 at 17:25
@Rex If merging is a thing, then I will certainly make either a comprehensive question. I asked the former a few days ago, if memory serves, and it specifically is concerned with how to do it with Puppet. If there is an idiomatically Puppet way to do this, it definitely belongs there, but this I think deals more with vSphere and the VMs themselves. If vSphere isn't particularly involved (if most of it is done through the terminal), then I could just instruct Puppet to run the command(s). – Sean Allred Jun 4 '13 at 17:35

The link you gave is talking about VMWare WorkStation, which should be quite different from vSphere ESXi you use, let alone establishing a serial link need not mean you could 'ping' each other.

Back to the question, I remember if you connect no physical switch to the vSwitch, the VMs connected to that vSwitch could still connect to each other. So, what you are doing should be OK. However, in that case, there will be no DHCP server so you need to either assign static IP to each of the VM network interface, or put a DHCP server on that vSwitch.

If you don't want to allow machine A to connect to machine C, and you don't trust the iptables firewall on them, one of the solution I could think of is have two network interface on machine B, and have each of the interface connect to either A or C, i.e.:

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.