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 a physical machine with two nics.

I already have a fully working cobbler server and I am able to deploy a bare metal or dom0 server in a few minutes. My target OS is RHEL5.

My goal is to deploy a dom0 installation in which only eth0 is up and configured (I can already do it now), and a number of domUs that are only bound to the other physical nic, eth1.

I can assign a different IP for each domU if necessary, of course.

Anybody can point out a link to documentation or an idea to accomplish my task?

The reason of my intent is security, dom0 would be only reachable by a management network, while domUs will only live on public network.

Thanks in advance

share|improve this question

Create a bridge in the dom0, connect eth1 in the dom0 to that, and then configure the domUs to connect to the bridge as well.

share|improve this answer
Uhm, any pragmatic way to do it in cobbler? Moreover, why the need for a custom bridge to be shared by every domU? – drAlberT Oct 5 '09 at 8:50
I know nothing about cobbler, never touched and I hopefully never will. It's not a "custom" bridge, it's how you're supposed to do switched network in a virtualised environment. – womble Oct 5 '09 at 9:02
So it is already what cobbler does. – drAlberT Oct 5 '09 at 13:15
up vote 0 down vote accepted

I found (only now unfortunately) a cobbler doc explaining how to do the job in a cobbler/koan way:

This is a very good starting point for me, I'm going to implement it.

The solution arrived from RHEL5 docs for xen libvirt virtualization:

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.