From: Ted Kaczmarek <tedkaz@optonline.net>
To: xen-devel@lists.xensource.com
Subject: networking oddities, present status ? changeset: 7145:71466686d026
Date: Fri, 30 Sep 2005 14:10:06 -0400 [thread overview]
Message-ID: <1128103806.3668.146.camel@pluto.linsolutions.com> (raw)
What is the present status of networking? Also will assigning unique mac
addresses to individual bridges on a domO be supported?
Seeing all kings of weird behavior when testing multiple nics.
changeset: 7145:71466686d026
nics=3
vif = ['mac=AA:00:00:11:11:12','bridge=xen-br1']
With the above I actually get eth0 and eth1 working on the domU, the
wild part is eth0 get the mac address AA:00:00:11:11:12 and shows up on
xen-br0.
Any other bridge setting for vif and weird stuff happens, broadcast
pings fail but unicast work, packet loss, total loss of connectivity,
packets from domU's get dropped at egress on domO, and domU kernel crash
have been observed.
vif = ['mac=AA:00:00:11:11:11' , 'bridge=xen-br0' , 'bridge=xen-br1' ,
'bridge=xen-br2']
Process swapper (pid: 1, threadinfo=c00b1000 task=c00b2a80)
Stack: 00000610 00000000 c17d1000 c0106685 00000001 00000000 c17cb240
c02294c3
c17cb240 0000000b 00000000 00000006 00000000 0000000b 00000000
00000000
00000000 00000000 c17b3740 c17cb246 c17b3752 00000000 c0229756
c04b8b60
Call Trace:
[<c0106685>] gnttab_grant_foreign_access+0x15/0x60
[<c02294c3>] setup_device+0x293/0x2c0
[<c0229756>] talk_to_backend+0x136/0x390
[<c0229a2f>] netfront_probe+0x7f/0x100
[<c02250ed>] xenbus_dev_probe+0x4d/0x60
[<c020b3ff>] driver_probe_device+0x2f/0x80
[<c020b579>] driver_attach+0x59/0x90
[<c020bacd>] bus_add_driver+0xad/0xf0
[<c022517a>] xenbus_register_driver+0x5a/0x70
[<c02251a7>] xenbus_register_device+0x17/0x20
[<c033fd9f>] init_net_xenbus+0xf/0x20
[<c033fdf0>] netif_init+0x40/0x50
[<c032da72>] do_initcalls+0x32/0xf0
[<c01040fa>] init+0x8a/0x1c0
[<c0104070>] init+0x0/0x1c0
[<c010748d>] kernel_thread_helper+0x5/0x18
Code: e9 60 55 08 00 f3 c3 8d b4 26 00 00 00 00 8d bc 27 00 00 00 00 56
53 83 ec 14 8b 74 24 20 8b 54 24 24 8b 5e 08 8b 86 f4 0c 00 00 <89> 83
90 00 00 00 0f b7 86 f8 0c 00 00 66 89 83 94 00 00 00 89
Regards,
Ted
next reply other threads:[~2005-09-30 18:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-30 18:10 Ted Kaczmarek [this message]
2005-09-30 20:02 ` networking oddities, present status ? changeset: 7145:71466686d026 Andrew Theurer
2005-09-30 20:50 ` Nivedita Singhvi
2005-09-30 21:16 ` Ted Kaczmarek
-- strict thread matches above, loose matches on Subject: below --
2005-09-30 21:19 Ian Pratt
2005-09-30 22:32 ` Andrew Theurer
2005-10-01 10:17 Ian Pratt
2005-10-11 15:02 ` Andrew Theurer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1128103806.3668.146.camel@pluto.linsolutions.com \
--to=tedkaz@optonline.net \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.