Most disconcerting is that if I perform the same ping flood from the
non-xen'd local box back to either dom0 or an ip assigned to the bridge
in the driver domain, eventually (about 100,000 packets) the same result
will occur. The nic dies. I can still ping between Dom0 and the driver
domain, but there is no outside traffic. When I run this against a
stock linux kernel, there is no issue (1,000,000+ packets).
B.
On Tue, 2005-02-01 at 12:13, B.G. Bruce wrote:
> Here are the dom config files:
>
> B.
>
>
> On Tue, 2005-02-01 at 09:10, Mark Williamson wrote:
> > OK, I haven't heard of this issue. Could you post your grub.conf for dom0
> > and
> > your domain config file for the backend?
> >
> > I'm not entirely clear on your configuration - how does your networking
> > setup
> > work? What *does* work?
> >
> > Cheers,
> > Mark
> >
> > On Tuesday 01 February 2005 13:11, B.G. Bruce wrote:
> > > Okay, I'm using a bk snapshot of testing as of 20:40 (-4:00) yesterday
> > > so I'm pretty sure this hasn't been addressed already.
> > >
> > > Symptom:
> > >
> > > While running a "ping -f <some local host outside the box>" from dom0
> > > where the physical nic is in a driver dom (bridged), after about 1
> > > minute the connection dies and won't restart. (even with a reboot of
> > > the driver domain).
> > >
> > > ex. Dom0 vif1.0=10.1.1.1/24
> > > outside host=10.1.1.2/24
> > >
> > > e1000 driver dom = bridge containing physical e1000(eth0) and virtual
> > > nic (eth1)
> > >
> > > dmesg on dom0 gives:
> > > irq 18: nobody cared!
> > > [<c012a4b7>]
> > > [<c012a547>]
> > > [<c0129f6c>]
> > > [<c010cd1b>]
> > > [<c0105c13>]
> > > [<c0108aa3>]
> > > [<c0106c05>]
> > > [<c0106c39>]
> > > [<c02e2621>]
> > > handlers:
> > > [<c020cdb6>]
> > > [<cc94b867>]
> > > Disabling IRQ #18
> > >
> > >
> > > and a dmesg of the driver domain shows that the nic hooked IRQ 18:
> > >
> > > Intel(R) PRO/1000 Network Driver - version 5.5.4-k2-NAPI
> > > Copyright (c) 1999-2004 Intel Corporation.
> > > PCI: Obtained IRQ 18 for device 0000:01:01.0
> > > PCI: Setting latency timer of device 0000:01:01.0 to 64
> > > e1000: eth0: e1000_probe: Intel(R) PRO/1000 Network Connection
> > >
> > > Am I correct in that the interrupt that should have been sent to the
> > > driver domain was instead sent to dom0? or what happened? If I don't
> > > have the driver dom setup correctly, would someone please explain what
> > > I'm doing wrong?
> > >
> > > Thanks,
> > > B.
> > >
> > >
> > > -------------------------------------------------------
> > > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
> > > Tool for open source databases. Create drag-&-drop reports. Save time
> > > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
> > > Download a FREE copy at http://www.intelliview.com/go/osdn_nl
> > > _______________________________________________
> > > Xen-devel mailing list
> > > Xen-devel@xxxxxxxxxxxxxxxxxxxxx
> > > https://lists.sourceforge.net/lists/listinfo/xen-devel
> >
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel
|
Home