NetBSD-Users archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Xen 3.3/NetBSD 5.1 DOM0: bridge not working if vcpus>1
Niels Dettenbach (Syndicat IT&Internet) wrote:
> Ron McDowell <rcm%fuzzwad.org@localhost> schrieb:
>
>> And have my bridge set up...
>>
>> [root@voodoo(NetBSD)]> cat /etc/ifconfig.bridge0
>> create
>> !brconfig $int add bge0 up
>> [root@voodoo(NetBSD)]> ifconfig bridge0
>> bridge0: flags=41<UP,RUNNING> mtu 1500
>>
>
> Does your bridge interface has any IP address configured (if you want to ping
> her)?
>
> Make shure not any of the ethernet interfaces within the bridge has any IP
> adress configured instead.
>
Keep in mind the bridge works fine with vcpus=1 [or no vcpu directive].
Only if vcpus>1 is there a problem.
Here is with one vcpu...
voodoo# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 256 1 r-----
2552.2
juju 2 4096 1 -b----
3452.4
voodoo# ifconfig -a
bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
capabilities=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
address: bc:30:5b:d0:a1:46
media: Ethernet autoselect (1000baseT
full-duplex,flowcontrol,rxpause,txpause)
status: active
inet 172.17.9.38 netmask 0xffffff00 broadcast 172.17.9.255
inet6 fe80::be30:5bff:fed0:a146%bge0 prefixlen 64 scopeid 0x1
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
bridge0: flags=41<UP,RUNNING> mtu 1500
xvif2.0: flags=8923<UP,BROADCAST,NOTRAILERS,PROMISC,SIMPLEX,MULTICAST>
mtu 1500
capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
enabled=0
address: 00:16:3e:ad:99:01
inet6 fe80::216:3eff:fead:9901%xvif2.0 prefixlen 64 scopeid 0x5
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
address: f2:0b:a4:20:a2:07
media: Ethernet autoselect
inet6 fe80::f00b:a4ff:fe20:a207%tap0 prefixlen 64 scopeid 0x6
voodoo# brconfig -a
bridge0: flags=41<UP,RUNNING>
Configuration:
priority 32768 hellotime 2 fwddelay 15 maxage 20
ipfilter disabled flags 0x0
Interfaces:
tap0 flags=3<LEARNING,DISCOVER>
port 6 priority 128
xvif2.0 flags=3<LEARNING,DISCOVER>
port 5 priority 128
bge0 flags=3<LEARNING,DISCOVER>
port 1 priority 128
Address cache (max cache: 100, timeout: 1200):
00:16:3e:ac:99:01 tap0 1180 flags=0<>
00:0d:b9:21:fa:54 bge0 946 flags=0<>
...and here is with 4 vcpus...
voodoo# xm list
Name ID Mem VCPUs State
Time(s)
Domain-0 0 256 1
r----- 11.6
juju 1 4096 4
-b---- 52.0
voodoo# ifconfig
-a
bge0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
capabilities=3f80<TSO4,IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
address: bc:30:5b:d0:a1:46
media: Ethernet autoselect (1000baseT
full-duplex,flowcontrol,rxpause,txpause)
status: active
inet 172.17.9.38 netmask 0xffffff00 broadcast 172.17.9.255
inet6 fe80::be30:5bff:fed0:a146%bge0 prefixlen 64 scopeid 0x1
lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 33648
inet 127.0.0.1 netmask 0xff000000
inet6 ::1 prefixlen 128
inet6 fe80::1%lo0 prefixlen 64 scopeid 0x2
bridge0: flags=41<UP,RUNNING> mtu 1500
xvif1.0: flags=8923<UP,BROADCAST,NOTRAILERS,PROMISC,SIMPLEX,MULTICAST>
mtu 1500
capabilities=2800<TCP4CSUM_Tx,UDP4CSUM_Tx>
enabled=0
address: 00:16:3e:ad:99:01
inet6 fe80::216:3eff:fead:9901%xvif1.0 prefixlen 64 scopeid 0x4
tap0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
address: f2:0b:a4:e3:5c:08
media: Ethernet autoselect
inet6 fe80::f00b:a4ff:fee3:5c08%tap0 prefixlen 64 scopeid 0x5
voodoo# brconfig -a
bridge0: flags=41<UP,RUNNING>
Configuration:
priority 32768 hellotime 2 fwddelay 15 maxage 20
ipfilter disabled flags 0x0
Interfaces:
tap0 flags=3<LEARNING,DISCOVER>
port 5 priority 128
xvif1.0 flags=3<LEARNING,DISCOVER>
port 4 priority 128
bge0 flags=3<LEARNING,DISCOVER>
port 1 priority 128
Address cache (max cache: 100, timeout: 1200):
00:16:3e:ac:99:01 tap0 1150 flags=0<>
00:0d:b9:21:fa:54 bge0 1113 flags=0<>
>
> Does xen add the vif interface to your bridge when your DomU got created
> (show bridge config when DomU got created/runs)? Otherwise you have to
> configure xen to use the network bridge for your DomUs in xend-config...
>
Yes, it all looks good.
--
Ron McDowell
San Antonio TX
Home |
Main Index |
Thread Index |
Old Index