Anders Siverby
2006-Feb-03 14:26 UTC
[Xen-users] Unable to have more than 3 interfaces in domU
I am not able to give more than 3 interfaces to domU. If I specify 4
vif=... to xm create, ifconfig -a in domU will only see eth0, eth1 and eth2.
Config file:
kernel = "/boot/vmlinuz-2.6.12.6-xenU"
memory = 20
disk = [''cow:/mnt/cdrom/crab-domU.img 30,hda1,w'']
root = "/dev/hda1 ro"
startscript for domU:
brctl addbr switch1
brctl addbr switch2
brctl addbr switch3
brctl addbr switch4
ifconfig switch1 up
ifconfig switch2 up
ifconfig switch3 up
ifconfig switch4 up
xm create -c /crab/.xen/crab-domU.cfg name=test vif=bridge=switch1
vif=bridge=switch2 vif=bridge=switch3 vif=bridge=switch4
The dom0 part of the network seem to be set up correctly:
#brctl show
bridge name bridge id STP enabled interfaces
switch1 8000.feffffffffff no vif2.0
switch2 8000.feffffffffff no vif2.1
switch3 8000.feffffffffff no vif2.2
switch4 8000.feffffffffff no vif2.3
xenbr0 8000.feffffffffff no peth0
vif0.0
Could there be some limitation in the xenU kernel or am I missing
something else?
We are developing a router simulator that runs Quagga in every domU, is
there a better way to simulate a serial link between two routers than to
use a bridge?
/Anders
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Anders Siverby
2006-Feb-06 13:14 UTC
[Xen-users] Re: Unable to have more than 3 interfaces in domU
I noticed that vif2.3 isn''t up, looks like the problem is in dom0 after
all.
vif2.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:5 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:84 (84.0 b) TX bytes:0 (0.0 b)
vif2.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF
BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Also, if I destroy domain 2 vif2.3 still shows up and is still attached
to switch4 (while vif2.0-2.2 is gone). I think I saw a post about this
earlier but I can''t find it now.
I am using Xen 3.0. What am I doing wrong?
/Anders
Anders Siverby wrote:> I am not able to give more than 3 interfaces to domU. If I specify 4
> vif=... to xm create, ifconfig -a in domU will only see eth0, eth1 and
> eth2.
>
> Config file:
>
> kernel = "/boot/vmlinuz-2.6.12.6-xenU"
> memory = 20
> disk = [''cow:/mnt/cdrom/crab-domU.img 30,hda1,w'']
> root = "/dev/hda1 ro"
>
> startscript for domU:
>
> brctl addbr switch1
> brctl addbr switch2
> brctl addbr switch3
> brctl addbr switch4
> ifconfig switch1 up
> ifconfig switch2 up
> ifconfig switch3 up
> ifconfig switch4 up
>
> xm create -c /crab/.xen/crab-domU.cfg name=test vif=bridge=switch1
> vif=bridge=switch2 vif=bridge=switch3 vif=bridge=switch4
>
> The dom0 part of the network seem to be set up correctly:
> #brctl show
> bridge name bridge id STP enabled interfaces
> switch1 8000.feffffffffff no vif2.0
> switch2 8000.feffffffffff no vif2.1
> switch3 8000.feffffffffff no vif2.2
> switch4 8000.feffffffffff no vif2.3
> xenbr0 8000.feffffffffff no peth0
> vif0.0
>
> Could there be some limitation in the xenU kernel or am I missing
> something else?
>
> We are developing a router simulator that runs Quagga in every domU, is
> there a better way to simulate a serial link between two routers than to
> use a bridge?
>
> /Anders
_______________________________________________
Xen-users mailing list
Xen-users@lists.xensource.com
http://lists.xensource.com/xen-users
Anders Siverby
2006-Feb-10 08:30 UTC
[Xen-users] Re: Unable to have more than 3 interfaces in domU
I found the post I was referring to. http://lists.xensource.com/archives/html/xen-users/2005-12/msg00817.html Seem to be the same problem but I don''t understand Ian''s answer:> As I recall, it''s a grant table size issue; the backend code should > dynamically allocate it but currently doesn''t.Eric Tessler has apparently been able to run 122 vifs per VM so it have to be possible to create at least 6 which is what I need? http://lists.xensource.com/archives/html/xen-users/2005-10/msg00278.html Please help me. /Anders Anders Siverby wrote:> I noticed that vif2.3 isn''t up, looks like the problem is in dom0 after > all. > > vif2.2 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > inet6 addr: fe80::fcff:ffff:feff:ffff/64 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:2 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:5 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:84 (84.0 b) TX bytes:0 (0.0 b) > > vif2.3 Link encap:Ethernet HWaddr FE:FF:FF:FF:FF:FF > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:3 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > Also, if I destroy domain 2 vif2.3 still shows up and is still attached > to switch4 (while vif2.0-2.2 is gone). I think I saw a post about this > earlier but I can''t find it now. > I am using Xen 3.0. What am I doing wrong? > > /Anders > > Anders Siverby wrote: >> I am not able to give more than 3 interfaces to domU. If I specify 4 >> vif=... to xm create, ifconfig -a in domU will only see eth0, eth1 and >> eth2. >> >> Config file: >> >> kernel = "/boot/vmlinuz-2.6.12.6-xenU" >> memory = 20 >> disk = [''cow:/mnt/cdrom/crab-domU.img 30,hda1,w''] >> root = "/dev/hda1 ro" >> >> startscript for domU: >> >> brctl addbr switch1 >> brctl addbr switch2 >> brctl addbr switch3 >> brctl addbr switch4 >> ifconfig switch1 up >> ifconfig switch2 up >> ifconfig switch3 up >> ifconfig switch4 up >> >> xm create -c /crab/.xen/crab-domU.cfg name=test vif=bridge=switch1 >> vif=bridge=switch2 vif=bridge=switch3 vif=bridge=switch4 >> >> The dom0 part of the network seem to be set up correctly: >> #brctl show >> bridge name bridge id STP enabled interfaces >> switch1 8000.feffffffffff no vif2.0 >> switch2 8000.feffffffffff no vif2.1 >> switch3 8000.feffffffffff no vif2.2 >> switch4 8000.feffffffffff no vif2.3 >> xenbr0 8000.feffffffffff no peth0 >> vif0.0 >> >> Could there be some limitation in the xenU kernel or am I missing >> something else? >> >> We are developing a router simulator that runs Quagga in every domU, >> is there a better way to simulate a serial link between two routers >> than to use a bridge? >> >> /Anders_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users