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-users] FC5 as domU- failed to bring multiple interfaces

On Fri, Dec 18, 2009 at 4:01 AM, Bojana Petrovic <bojanap@xxxxxxxxx> wrote:
> bridge name     bridge id                          STP enabled
> interfaces
> virbr0               8000.aa00271ff6ba          yes                   tap0
> vif1.0
> xenbrBC          8000.0687ee475769       no                      tap1
> vif1.1

I probably should ask this earlier, but are you running it as HVM
domU, by any chance? The presence of tap0 and tap1 suggests as much.
If yes, then I should warn you, performance-wise, it'd suck. Big time.
You might have better luck installing RHEL/Centos5 kernel-xen on it,
and run it as PV guest.

PV vs HVM should not have anything to do with the original issue though.

> On domU, I run following commands:
> [root@localhost ~]# ip link show
> 1: lo: <LOOPBACK,UP,10000> mtu 16436 qdisc noqueue
>     link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
> 2: eth0: <BROADCAST,MULTICAST,UP,10000> mtu 1500 qdisc pfifo_fast qlen 1000
>     link/ether 00:16:36:12:49:53 brd ff:ff:ff:ff:ff:ff
> 3: eth1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
>     link/ether 00:16:3e:50:82:56 brd ff:ff:ff:ff:ff:ff

This pretty much suggest that domU already recognize eth1. What
happens when you set it up manually, using ifconfig?

> I saw on my Fedora 8 VM that all interfaces has this parametar pfifo_fast,
> and not noop like here in the case of eth1.
> I do not know how to change it.

qdisc should be related to traffic control. try "man tc". It's
somewhat complex though.

> [root@localhost ~]# xm network list masterf5
> bash: xm: command not found
> [root@localhost ~]# xm
> bash: xm: command not found
> [root@localhost ~]# xm --help
> bash: xm: command not found
> I didn't installed xen on domU, so I suppose this is the reason for last
> output.

That's because you're supposed to run it on dom0. Plus the command is
"xm network-list", not "xm network list". Nevermind though, looks like
domU already got the interface.

> I'm running 2.6.18-164.el5xen kernel on dom0 and on for domU I use MPLS
> enabled  kernel-2.6.20-1.2320fc5.mpls.1.956.i686.rpm.

If my guess is correct, and you're running it as HVM domU (your domU
kernel suggests that as well), then you probably would never be able
to deploy this system in production environment due to performance


Xen-users mailing list

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