Bojana Petrovic
2009-Dec-16 22:13 UTC
[Xen-users] FC5 as domU- failed to bring multiple interfaces
Hi everybody, I''m running Xen on CentOS 5.4 as dom0. I successfully managed to bring up multiple domU interfaces on different domU platforms- Fedora 8, Fedora 10, CentOS. A the moment, I really need Fedora 5 as domU, but I can not bring up multiple interfaces inside domU. I tried with standard procedure, like this: Made network-bridge-custom: #!/bin/sh dir=$(dirname "$0") "$dir/network-bridge" "$@" netdev=eth0 bridge=xenbr0 vifnum=0 "$dir/network-bridge" "$@" netdev=eth1 bridge=xenbrBC vifnum=1 "$dir/network-bridge" "$@" netdev=eth2 bridge=xenbrBD vifnum=2 "$dir/network-bridge" "$@" netdev=eth3 bridge=xenbrBE vifnum=3 "$dir/network-bridge" "$@" netdev=eth4 bridge=xenbrCD vifnum=4 Modified configuration file for domU, like this: disk = [ "file:/var/lib/xen/images/masterf5.img,hda,w", ",hdc:cdrom,r" ] vif = [ "mac=00:16:36:12:49:53,bridge=virbr0,script=vif-bridge", "mac=00:16:3e:50:82:56, bridge=xenbrBC"] Fedora 5 virtual machine didn''t recognize another interface. Please, does anybody have idea what might be wrong??? This approach worked perfectly in other cases? Is there anything special in a case of Fedora 5? Best regards, Bojana _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Dec-17 04:54 UTC
Re: [Xen-users] FC5 as domU- failed to bring multiple interfaces
On Thu, Dec 17, 2009 at 5:13 AM, Bojana Petrovic <bojanap@gmail.com> wrote:> disk = [ "file:/var/lib/xen/images/masterf5.img,hda,w", ",hdc:cdrom,r" ] > vif = [ "mac=00:16:36:12:49:53,bridge=virbr0,script=vif-bridge", > "mac=00:16:3e:50:82:56, bridge=xenbrBC"] > > Fedora 5 virtual machine didn''t recognize another interface.it should work. Try something like vif = [ "mac=00:16:36:12:49:53,bridge=virbr0,script=vif-bridge", "mac=00:16:3e:50:82:56, bridge=xenbrBC,script=vif-bridge"] just in case the default script is wrong. Also, what is the output of - "brctl show" on dom0, when domU is started - "xm network-list domU_name", when domU is started - "ip link show" on domU Also, which kernel did you use for domU? -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Bojana Petrovic
2009-Dec-17 21:01 UTC
Re: [Xen-users] FC5 as domU- failed to bring multiple interfaces
Hi Fajar and everybody,
This is output of *brctl show* on dom0:
bridge name bridge id STP enabled
interfaces
virbr0 8000.aa00271ff6ba yes tap0
vif1.0
xenbr0 8000.feffffffffff
no peth0
vif0.0
xenbrBC 8000.0687ee475769 no tap1
vif1.1
xenbrBD 8000.000000000000 no
xenbrCD 8000.000000000000 no
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
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.
[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.
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.
Thank you very much,
Bojana
On Thu, Dec 17, 2009 at 5:54 AM, Fajar A. Nugraha <fajar@fajar.net> wrote:
> On Thu, Dec 17, 2009 at 5:13 AM, Bojana Petrovic <bojanap@gmail.com>
> wrote:
> > disk = [ "file:/var/lib/xen/images/masterf5.img,hda,w",
",hdc:cdrom,r" ]
> > vif = [
"mac=00:16:36:12:49:53,bridge=virbr0,script=vif-bridge",
> > "mac=00:16:3e:50:82:56, bridge=xenbrBC"]
> >
> > Fedora 5 virtual machine didn''t recognize another interface.
>
> it should work. Try something like
> vif = [ "mac=00:16:36:12:49:53,bridge=virbr0,script=vif-bridge",
> "mac=00:16:3e:50:82:56, bridge=xenbrBC,script=vif-bridge"]
>
> just in case the default script is wrong. Also, what is the output of
> - "brctl show" on dom0, when domU is started
> - "xm network-list domU_name", when domU is started
> - "ip link show" on domU
>
> Also, which kernel did you use for domU?
>
> --
> Fajar
>
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Fajar A. Nugraha
2009-Dec-18 13:40 UTC
Re: [Xen-users] FC5 as domU- failed to bring multiple interfaces
On Fri, Dec 18, 2009 at 4:01 AM, Bojana Petrovic <bojanap@gmail.com> wrote:> bridge name bridge id STP enabled > interfaces > virbr0 8000.aa00271ff6ba yes tap0 > > vif1.0 > xenbrBC 8000.0687ee475769 no tap1 > > vif1.1I 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:ffThis 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 issues. -- Fajar _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users