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


Re: [Xen-devel] [Fwd: bridging problem with Xen 2.0.1]

To: Mike Wray <mike.wray@xxxxxxxxxx>
Subject: Re: [Xen-devel] [Fwd: bridging problem with Xen 2.0.1]
From: Pásztor Lénárd Zoltán <lenard.pasztor@xxxxxxxxxxxxx>
Date: Mon, 29 Nov 2004 16:02:32 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 29 Nov 2004 15:03:46 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: <41AB1F55.1020805@xxxxxxxxxx>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
References: <41AAFCBB.30605@xxxxxxxxxxxxx> <41AB1F55.1020805@xxxxxxxxxx>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
User-agent: Mozilla Thunderbird 0.9 (X11/20041124)
Mike Wray wrote:

Pásztor Lénárd Zoltán wrote:

domain0:~# brctl show
bridge name     bridge id               STP enabled     interfaces
xen-br0         8000.aa0001000011       no              vif4.0
xen-br1 8000.000000000000 no can't get port info: Function not implemented

Why vif4.1 not in xen-br1?

Something must have gone wrong. What's the ouput from 'xm list -l' show?
Also is there anything in /var/log/xend.log?

xm list -l output is:

           (idx 0)
           (vif 0)
           (mac aa:00:00:00:00:11)
           (bridge xen-br0)
           (evtchn 14 4)
           (index 0)
           (idx 1)
           (vif 1)
           (mac bb:00:00:00:00:22)
           (bridge xen-br1)
           (evtchn 15 5)
           (index 1)

Seems to bee OK.

xend.log has two lines associated by nic:

[2004-11-29 15:47:43 xend] DEBUG (XendDomainInfo:1059) Creating vif dom=2 vif=0 mac=aa:00:00:00:00:11 [2004-11-29 15:47:43 xend] DEBUG (XendDomainInfo:1059) Creating vif dom=2 vif=1 mac=bb:00:00:00:00:22

no error messages on it.

Let's add it manually...

domain0:~# brctl addif vif4.1 xen-br1
can't add xen-br1 to bridge vif4.1: Operation not supported

It gives error message :( What is the problem?

You've got the arguments round the wrong way, it should be

brctl addif xen-br1 vif4.1

sorry, I paste wrong the line o:)

domain1: brctl addif xen-br1 vif4.1
can't add vif4.1 to bridge xen-br1: Cannot assign requested address

- How can I define the nic name (vif) before I start a virtual machine?

The vif device name in domain-0 is vif<domain id>.<interface>.
This is not changeable at the moment. If you need to do something with
the device, you could use the vif-bridge script to do it, or configure
another script.

It's OK for me, thx!

Pásztor Lénárd Zoltán

Wonderline Rt.
Telefon: (+36-1) 272.0242
Fax: (+36-1) 272.0252
Honlap: www.wonderline.hu

SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>