This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-users] More network problems

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] More network problems
From: "James Alspach" <jalspach@xxxxxxxxxxxxx>
Date: Wed, 2 Jul 2008 17:58:30 -0700
Delivery-date: Wed, 02 Jul 2008 17:59:07 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acjcp+iQuPYhqdUbT02YmupuKSG1mQ==
Thread-topic: More network problems

I thought I had XEN networking down fairly well but I have since run into a sort of chicken and egg problem.

I set up my master server as I noted in an earlier post.  This machine has bonded NIC’s each sitting on trunked switch ports.  I have a vlan set up and am able to ping the gateway without issue.  Now, I want to add a second server to the pool.

If I understand correctly, once it is added to the pool it should inherit the bonding, vlans, etc… set up on the master.  The problem is that the second server can not see the master to join until it is on the network. 

I thought, no problem, I will bootstrap it by setting up the management vlan on this second server and then joining it to the pool.  Well I got the management vlan set up on this machine and can ping the gateway but Xen complains that I must have a physical NIC set up as the management port before I can join a pool (which I guess makes sense since the pool will take over control of the virtual interfaces).

Maybe this will all make sense tomorrow after I sleep on it but, does any one have any suggestions?

I am getting brain tied (similar to tongue tied only worse) every time I try to sort out the relationship between the PIF’s, VIF’s, Network’s, Vlans, Bridges, actual physical NIC’s, output of ifconfig, etc… and which ones I need to connect to which to make things work.  I had it figured out at one point (I think) but that was before I tossed vlans into the mix.

My cloudy general idea of how it works is that: physical interfaces are tied to virtual switches (networks) and those switches have interfaces pifs.  Vifs are attached to the pifs and can be plugged into virtual machines. 

Am I close?


Thanks for your help;







James Alspach
Systems Analyst II

Shasta County Office of Education

1644 Magnolia avenue

Redding, California

(530) 225-0293


IT Hotline: 225-0279



Xen-users mailing list
<Prev in Thread] Current Thread [Next in Thread>