Wolfgang Solfrank <Wolfgang <at> Solfrank.net> wrote: > Why don't you use gdbsx instead? It is in Xen 4.1 (is it supported with netbsd-5 dom0 and domU?). Is there anything available for Xen 3.1? -- -- Emmanuel Dreyfus http://hcpnet.free.fr/pubz manu <at> netbsd.org
Hello,
I'm trying to set up a DomU that is connected to a vlan trunk in a
transparent way. I've read other mails in the list regarding this
configuration, but I cannot get it working. My current configuration:
bnx1 is connected to a trunk of several tagged vlans (with ids: 2301, 2302...)
vlan230x is the vlan interface that corresponds to each vlan id.
bridge230x is a bridge of vlan230x.
The vlans are created using this scripts:
create
vlan 230x vlanif bnx1
(where x is the id of the vlan)
And the bridges:
create
!brconfig $int add vlan230x up
Le'ts take vlan 2301 as an example, here is the relevant configuration
after the scripts are executed:
bnx1: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST>
mtu 1500
capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx>
enabled=0
address: 18:03:73:0a:89:33
(Continue reading)
On Tue, Sep 06, 2011 at 02:42:06PM +0200, Roger Pau Monn? wrote: > > Now from the DomU I can ping the Dom0, but not the outside, and from > the Dom0 I can ping both the DomU and the outside. brconfig shows the > following after the DomU start: I have seen this too. I think if you wait a while after bringing the configuration up, it will eventually fix itself. It has something to do with the bridge learning or STP code but I have never managed to figure out what. "A while" could mean a minute or more. :-/ Thor
> I have seen this too. I think if you wait a while after bringing the > configuration up, it will eventually fix itself. It has something to do > with the bridge learning or STP code but I have never managed to figure > out what. > > "A while" could mean a minute or more. :-/ Thanks for the fast reply, DomU has been running for more than one hour and still not reachable from outside. If I perform a tcpdump of interface bnx1 I also see: 16:31:12.017369 STP 802.1w, Rapid STP, Flags [Forward], bridge-id 8000.20:fd:f1:77:b2:77.8012, length 47 16:31:14.017483 STP 802.1w, Rapid STP, Flags [Forward], bridge-id 8000.20:fd:f1:77:b2:77.8012, length 47 16:31:16.017663 STP 802.1w, Rapid STP, Flags [Forward], bridge-id 8000.20:fd:f1:77:b2:77.8012, length 47 16:31:18.017706 STP 802.1w, Rapid STP, Flags [Forward], bridge-id 8000.20:fd:f1:77:b2:77.8012, length 4 All the time, but it seems to have no effect.
On Tue, Sep 06, 2011 at 02:42:06PM +0200, Roger Pau Monné wrote: > Hello, > > I'm trying to set up a DomU that is connected to a vlan trunk in a > transparent way. I've read other mails in the list regarding this > configuration, but I cannot get it working. My current configuration: > > bnx1 is connected to a trunk of several tagged vlans (with ids: 2301, 2302...) > vlan230x is the vlan interface that corresponds to each vlan id. > bridge230x is a bridge of vlan230x. > > The vlans are created using this scripts: > > create > vlan 230x vlanif bnx1 > > (where x is the id of the vlan) > > And the bridges: > > create > !brconfig $int add vlan230x up > > Le'ts take vlan 2301 as an example, here is the relevant configuration > after the scripts are executed: > > bnx1: flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST> > mtu 1500 > capabilities=3f00<IP4CSUM_Rx,IP4CSUM_Tx,TCP4CSUM_Rx,TCP4CSUM_Tx,UDP4CSUM_Rx,UDP4CSUM_Tx> > enabled=0(Continue reading)
I've just realized what the problem was, I had bnx1 bridged, and all
packets (tagged or not) where sent to bridge1 instead of the
corresponding bridge for every vlan (what's strange is that vlan
intefaces worked correctly, the problem was with DomU packets only).
The result for the tcpdump -e -v was:
09:09:23.383347 20:fd:f1:77:b2:8a (oui Unknown) > 01:80:c2:00:00:00
(oui Unknown), 802.3, length 64: LLC, dsap STP (0x42) Individual, ssap
STP (0x42) Command, ctrl 0x03: STP 802.1w, Rapid STP, Flags [Forward],
bridge-id 8000.20:fd:f1:77:b2:77.8012, length 47
message-age 0.00s, max-age 20.00s, hello-time 2.00s,
forwarding-delay 15.00s
root-id 8000.20:fd:f1:77:b2:77, root-pathcost 0, port-role Designated
Once I removed the bnx1 interface from the bridge everything started
working correctly. Since I only have tagged traffic on this interface
I don't need the bnx1 bridge anymore, but this could be a problem in
some other situation.
Thanks, Roger.
On Wed, Sep 07, 2011 at 09:20:35AM +0200, Roger Pau Monné wrote: > I've just realized what the problem was, I had bnx1 bridged, and all > packets (tagged or not) where sent to bridge1 instead of the > corresponding bridge for every vlan Yes, that's a known issue > (what's strange is that vlan > intefaces worked correctly, the problem was with DomU packets only). Sure, I wouldn't expect vlans to work at all in this condition ... -- -- Manuel Bouyer <bouyer <at> antioche.eu.org> NetBSD: 26 ans d'experience feront toujours la difference --
On 23/08/2011, Hugo Silva <hugo <at> barafranca.com> wrote: > On 08/23/11 19:08, Cherry G. Mathew wrote: >> On 23 August 2011 20:04, Cherry G. Mathew <cherry.g.mathew <at> gmail.com> >> wrote: >>> Hi folks, >>> >>> Quick one to say that I've been able to boot MP successfully from the >>> [cherry-xenmp] branch. >>> >>> I'd love for it to be tried out and hammered a bit. >>> >>> First checkout a buildable version of -current >>> then: >>> $ cd sys >>> $ cvs update -C -rcherry-xenmp src/sys >> >> Sorry, that should be: >> >> $ cvs update -C -rcherry-xenmp >> >> >> > > Hello Cherry, > > This is for i386 domU correct? > > Purely from a curiosity standpoint, what's the status on dom0 MP and > amd64? Any ETAs? Is the work done on i386 most of the work needed for > amd64 MP ?(Continue reading)
On 9/9/11 4:57 AM, Cherry G. Mathew wrote: > Just to say I've checked in amd64 support. Do give it a spin, and let > us know (on list) how it goes. > > I haven't tested this on dom0. I haven't tried dom0 yet (hopefully in a couple hours, though). But, I just built an MP amd64 XEN3_DOMU kernel, and got through building libc on a release build of src before panic: xpq_flush_queue: 3 entries (0 successful) 0x00000001c2cba000: 0x00000001a9731007 0x00000001c625d000: 0x00000001a9731007 0x00000001a712c000: 0x00000001a9731007 panic: HYPERVISOR_mmu_update failed, ret: -22 fatal breakpoint trap in supervisor mode trap type 1 code 0 rip ffffffff801322cd cs e030 rflags 246 cr2 40357f cpl 6 rsp ffffa0002a2a7620 Stopped in pid 14556.1 (groff) at netbsd:breakpoint+0x5: leave breakpoint() at netbsd:breakpoint+0x5 panic() at netbsd:panic+0x2b7 xpq_update_foreign() at netbsd:xpq_update_foreign pmap_enter_ma() at netbsd:pmap_enter_ma+0x8e3 pmap_enter() at netbsd:pmap_enter+0x5a uvm_fault_lower() at netbsd:uvm_fault_lower+0x81d uvm_fault_internal() at netbsd:uvm_fault_internal+0xf12 trap() at netbsd:trap+0x85d --- trap (number 0) ---(Continue reading)
Hi, (sorry for the delay, was AFK for a few days.) Emmanuel Dreyfus schrieb: > Wolfgang Solfrank<Wolfgang <at> Solfrank.net> wrote: > >> Why don't you use gdbsx instead? > > It is in Xen 4.1 (is it supported with netbsd-5 dom0 and domU?). Is > there anything available for Xen 3.1? Sorry, I only use it with Xen 4. However, looking into the xentools3 tar file, there seems to be something similar (albeit not installed by the pkgsrc package) in .../tools/debugger/gdb. Ciao, Wolfgang -- -- Wolfgang <at> Solfrank.net Wolfgang Solfrank
RSS Feed17 | |
|---|---|
5 | |
26 | |
2 | |
66 | |
65 | |
74 | |
1 | |
95 | |
25 | |
57 | |
154 | |
26 | |
4 | |
11 | |
76 | |
43 | |
17 | |
7 | |
29 | |
83 | |
66 | |
23 | |
71 | |
77 | |
114 | |
90 | |
26 | |
38 | |
27 | |
44 | |
35 | |
64 | |
18 | |
48 | |
86 | |
53 | |
34 | |
132 | |
56 | |
65 | |
44 | |
43 | |
108 | |
67 | |
124 | |
73 | |
115 | |
100 | |
52 | |
72 | |
70 | |
110 | |
26 | |
86 | |
119 | |
120 | |
222 | |
71 | |
131 | |
200 | |
114 | |
120 | |
174 | |
191 | |
38 | |
84 | |
48 | |
98 | |
65 | |
47 | |
145 | |
55 | |
100 | |
78 | |
62 | |
100 | |
72 | |
139 | |
114 | |
96 | |
34 | |
127 | |
41 | |
88 | |
96 | |
205 | |
17 | |
107 | |
47 | |
65 | |
47 | |
36 | |
46 | |
23 | |
75 | |
88 | |
169 | |
164 | |
25 | |
6 | |
104 | |
1 | |
5 | |
1 | |
1 | |
1 | |
38 | |
34 |
