|
xen-users
Re: [Xen-users] Xen 3.3 NetBSD DOM0: xenconsole: Could not read tty from
Roger Pau Monné wrote:
[root@voodoo(NetBSD)]> brconfig bridge0 # on DOM0
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
xvif1.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:0d:b9:21:fa:54 bge0 1174 flags=0<>
I haven't noticed it, but it looks like the bridge is not correctly
caching the mac address of the added interfaces, I usually have
something like this in the "Address cache" of a bridge:
Address cache (max cache: 100, timeout: 1200):
00:16:3e:7c:11:77 xvif8i0 18446744073709551596 flags=0<>
00:16:3e:30:9e:ee vlan2304 18446744073709551471 flags=0<>
cast of characters [all netmasks are /24]:
voodoo: DOM0, 172.17.9.38
juju: DOMU, 172.17.9.33
zombie: macbook air that is my desktop box with the vnc session to DOMU and
ssh session to DOM0, 172.17.5.4
alix2-e0: default router, 172.17.9.1, wired network
alix2-w0: wifi side, 172.17.5.1, only connection is to zombie
d430: the outside box, 172.17.9.36
pinging out [d430] from DOMU [juju]:
voodoo# tcpdump -i bge0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bge0, link-type EN10MB (Ethernet), capture size 96 bytes
13:15:35.663665 arp who-has d430-e0.FuzzWad.NET tell juju-e0.FuzzWad.NET
13:15:35.663899 arp reply d430-e0.FuzzWad.NET is-at 00:21:70:b7:f0:70 (oui
Unknown)
13:15:35.804971 IP voodoo-e0.FuzzWad.NET.65031 >
alix2-e0.FuzzWad.NET.domain: 12889+ PTR? 36.9.17.172.in-addr.arpa. (42)
13:15:35.805830 IP alix2-e0.FuzzWad.NET.domain >
voodoo-e0.FuzzWad.NET.65031: 12889* 1/1/1 PTR[|domain]
13:15:35.805955 IP voodoo-e0.FuzzWad.NET.65030 >
alix2-e0.FuzzWad.NET.domain: 12890+ PTR? 33.9.17.172.in-addr.arpa. (42)
13:15:35.806657 IP alix2-e0.FuzzWad.NET.domain >
voodoo-e0.FuzzWad.NET.65030: 12890* 1/1/1 PTR[|domain]
13:15:36.673680 arp who-has d430-e0.FuzzWad.NET tell juju-e0.FuzzWad.NET
13:15:36.673914 arp reply d430-e0.FuzzWad.NET is-at 00:21:70:b7:f0:70 (oui
Unknown)
13:15:36.804797 IP voodoo-e0.FuzzWad.NET.65029 >
alix2-e0.FuzzWad.NET.domain: 12891+ PTR? 1.9.17.172.in-addr.arpa. (41)
13:15:36.805499 IP alix2-e0.FuzzWad.NET.domain >
voodoo-e0.FuzzWad.NET.65029: 12891* 1/1/1 PTR[|domain]
13:15:36.805603 IP voodoo-e0.FuzzWad.NET.65028 >
alix2-e0.FuzzWad.NET.domain: 12892+ PTR? 38.9.17.172.in-addr.arpa. (42)
13:15:36.806305 IP alix2-e0.FuzzWad.NET.domain >
voodoo-e0.FuzzWad.NET.65028: 12892* 1/1/1 PTR[|domain]
13:15:37.683694 arp who-has d430-e0.FuzzWad.NET tell juju-e0.FuzzWad.NET
13:15:37.683927 arp reply d430-e0.FuzzWad.NET is-at 00:21:70:b7:f0:70 (oui
Unknown)
13:15:37.804795 IP voodoo-e0.FuzzWad.NET.5901 > zombie.FuzzWad.NET.54422: P
3957151084:3957151104(20) ack 3615361740 win 4197 <nop,nop,timestamp 129095
905335335>
13:15:37.914544 IP zombie.FuzzWad.NET.54422 > voodoo-e0.FuzzWad.NET.5901: .
ack 20 win 65535 <nop,nop,timestamp 905335706 129095>
13:15:38.693717 arp who-has d430-e0.FuzzWad.NET tell juju-e0.FuzzWad.NET
13:15:38.693950 arp reply d430-e0.FuzzWad.NET is-at 00:21:70:b7:f0:70 (oui
Unknown)
13:15:38.804797 IP voodoo-e0.FuzzWad.NET.65027 >
alix2-e0.FuzzWad.NET.domain: 12893+ PTR? 4.5.17.172.in-addr.arpa. (41)
13:15:38.805655 IP alix2-e0.FuzzWad.NET.domain >
voodoo-e0.FuzzWad.NET.65027: 12893* 1/1/1 PTR[|domain]
13:15:38.815330 IP zombie.FuzzWad.NET.54422 > voodoo-e0.FuzzWad.NET.5901: P
1:11(10) ack 20 win 65535 <nop,nop,timestamp 905335715 129095>
13:15:39.014708 IP voodoo-e0.FuzzWad.NET.5901 > zombie.FuzzWad.NET.54422: .
ack 11 win 4197 <nop,nop,timestamp 129097 905335715>
13:15:39.703732 arp who-has d430-e0.FuzzWad.NET tell juju-e0.FuzzWad.NET
13:15:39.703966 arp reply d430-e0.FuzzWad.NET is-at 00:21:70:b7:f0:70 (oui
Unknown)
13:15:40.713755 arp who-has d430-e0.FuzzWad.NET tell juju-e0.FuzzWad.NET
13:15:40.713989 arp reply d430-e0.FuzzWad.NET is-at 00:21:70:b7:f0:70 (oui
Unknown)
13:15:41.723767 arp who-has d430-e0.FuzzWad.NET tell juju-e0.FuzzWad.NET
13:15:41.724001 arp reply d430-e0.FuzzWad.NET is-at 00:21:70:b7:f0:70 (oui
Unknown)
^C
28 packets captured
28 packets received by filter
0 packets dropped by kernel
Pinging DOMU [juju] from outside [d430]:
voodoo# voodoo# tcpdump -i bge0
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on bge0, link-type EN10MB (Ethernet), capture size 96 bytes
13:18:03.416797 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET
13:18:03.806349 IP voodoo-e0.FuzzWad.NET.65024 >
alix2-e0.FuzzWad.NET.domain: 13910+ PTR? 33.9.17.172.in-addr.arpa. (42)
13:18:03.807206 IP alix2-e0.FuzzWad.NET.domain >
voodoo-e0.FuzzWad.NET.65024: 13910* 1/1/1 PTR[|domain]
13:18:03.807317 IP voodoo-e0.FuzzWad.NET.65023 >
alix2-e0.FuzzWad.NET.domain: 13911+ PTR? 1.9.17.172.in-addr.arpa. (41)
13:18:03.808018 IP alix2-e0.FuzzWad.NET.domain >
voodoo-e0.FuzzWad.NET.65023: 13911* 1/1/1 PTR[|domain]
13:18:04.417209 arp who-has juju-e0.FuzzWad.NET tell alix2-e0.FuzzWad.NET
13:18:04.806175 IP voodoo-e0.FuzzWad.NET.65022 >
alix2-e0.FuzzWad.NET.domain: 13912+ PTR? 38.9.17.172.in-addr.arpa. (42)
13:18:04.806877 IP alix2-e0.FuzzWad.NET.domain >
voodoo-e0.FuzzWad.NET.65022: 13912* 1/1/1 PTR[|domain]
13:18:05.836126 IP voodoo-e0.FuzzWad.NET.5901 > zombie.FuzzWad.NET.54422: P
3957206628:3957206648(20) ack 3615362238 win 4197 <nop,nop,timestamp 129391
905337123>
13:18:05.885190 IP zombie.FuzzWad.NET.54422 > voodoo-e0.FuzzWad.NET.5901: .
ack 20 win 65535 <nop,nop,timestamp 905337183 129391>
13:18:06.790471 IP zombie.FuzzWad.NET.54422 > voodoo-e0.FuzzWad.NET.5901: P
1:11(10) ack 20 win 65535 <nop,nop,timestamp 905337192 129391>
13:18:06.806179 IP voodoo-e0.FuzzWad.NET.65021 >
alix2-e0.FuzzWad.NET.domain: 13913+ PTR? 4.5.17.172.in-addr.arpa. (41)
13:18:06.807037 IP alix2-e0.FuzzWad.NET.domain >
voodoo-e0.FuzzWad.NET.65021: 13913* 1/1/1 PTR[|domain]
13:18:06.986080 IP voodoo-e0.FuzzWad.NET.5901 > zombie.FuzzWad.NET.54422: .
ack 11 win 4197 <nop,nop,timestamp 129393 905337192>
^C
14 packets captured
14 packets received by filter
0 packets dropped by kernel
>From what I can see, looks like the DomU is able to send packets to
the outside, but the network card is not properly forwarding incoming
packets to the xvif interface (probably because it doesn't have the
MAC address of the xvif interface in the address cache).
I don't know what the problem might be, you should try asking the
port-xen NetBSD mailing list, maybe tell will be able to shed some
light on this issue. Also I don't have much experience with Xen 3,
I've always used Xen 4 so I don't know if there are some bugs related
to network configuration.
Sorry I cannot be of much help, regards, Roger.
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
After much experimenting I have come up with a repeatable way of making
this work or fail. It doesn't make much sense to me... but if I have
in my config file 'vcpus = 1' [or no vcpus designation] everything
works fine. If I set vcpus to 2 or 4, the bridge0 does not connect. I
tried HVM DOMUs with FreeBSD 8.2 RELEASE, both i386 and amd64, and
memory sized at 256m/512m/1024m/2048m as well as 4096m on amd64 only.
Anybody have any idea what could be going on here? Again, as
background, the hardware is a Dell T110, Quad Core Xeon, 8gb ram, 4x1tb
SATA. Dom0 is NetBSD 5.1 RELEASE, and xen 3.3 installed via pkg_add.
--
Ron McDowell
San Antonio TX
|
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
Home