From: "Pásztor Lénárd Zoltán" <lenard.pasztor@wonderline.hu>
To: Mike Wray <mike.wray@hpl.hp.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: [Fwd: bridging problem with Xen 2.0.1]
Date: Mon, 29 Nov 2004 16:02:32 +0100 [thread overview]
Message-ID: <41AB3A08.6000807@wonderline.hu> (raw)
In-Reply-To: <41AB1F55.1020805@hpl.hp.com>
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:
(devices
(vif
(idx 0)
(vif 0)
(mac aa:00:00:00:00:11)
(bridge xen-br0)
(evtchn 14 4)
(index 0)
)
(vif
(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
rendszergazda
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/
prev parent reply other threads:[~2004-11-29 15:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-29 10:40 [Fwd: bridging problem with Xen 2.0.1] Pásztor Lénárd Zoltán
2004-11-29 11:58 ` kaz
2004-11-29 14:12 ` Nuutti Kotivuori
2004-11-29 15:41 ` kaz
2004-11-29 15:47 ` Brian Wolfe
2004-11-29 15:56 ` kaz
2004-11-29 16:20 ` Brian Wolfe
2004-11-29 16:55 ` Nuutti Kotivuori
2004-11-29 17:29 ` Brian Wolfe
2004-11-29 14:47 ` Xen 2.0 Debian packages Jérôme Petazzoni
2004-11-30 1:12 ` Brian Wolfe
2004-11-29 12:18 ` [Fwd: bridging problem with Xen 2.0.1] Keir Fraser
2004-11-29 14:55 ` Pásztor Lénárd Zoltán
2004-11-29 16:01 ` Pásztor Lénárd Zoltán
2004-11-29 13:08 ` Mike Wray
2004-11-29 15:02 ` Pásztor Lénárd Zoltán [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=41AB3A08.6000807@wonderline.hu \
--to=lenard.pasztor@wonderline.hu \
--cc=mike.wray@hpl.hp.com \
--cc=xen-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.