[Xen-bugs] [Bug 338] New: Using more that 1 nic results in erratic behavior, broken broadcast domains etc..

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=338

           Summary: Using more that 1 nic results in erratic behavior,
                    broken broadcast domains etc..
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Hardware Support
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: tedkaz@xxxxxxxxxxxxx


I was really trying to focus in on something but don't have the resources as
this issues seems to be totally random. I have seen everything from the peth0
griping about seeing packets from its own address, vif's created and mapped to
the wrong interfaces, vif's created and not mapped anyhwere, most of these will
have a failure in registering net-dev on boot as well, all of these will result
in some networking issue. Tried every combination of things I could think of
without having issues. 

I stopped looking into distro init scripts as the distro does not matter and you
can see the netdev issue long before the init scripts start.
 
Have seen the same problems with Centos 4.1, Debian 3.1, FC4, Gentoo 2005 and
Slacwware 10.2 and 10.3 guests using either an FC4 or Centos 4.1 dom0.

SMP -  problems are definetly more frequent

Let me know if their is something specific you want me to try, in all the
multiple nic setups the domU's between dom0's share a broadcast domain.

I know my bridge configs are valid as every failure I have tested the bridge
configs without xen and no issues.

-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs