From mboxrd@z Thu Jan 1 00:00:00 1970 From: "B.G. Bruce" Subject: Re: Driver domain - NEW issue: IRQ handling error Date: Tue, 01 Feb 2005 21:01:03 -0400 Message-ID: <1107306062.4411.105.camel@master.vms.security> References: <1107263493.4411.22.camel@master.vms.security> <200502011310.50062.maw48@cl.cam.ac.uk> <1107274402.4411.49.camel@master.vms.security> <1107277309.4411.60.camel@master.vms.security> Reply-To: bgb@nt-nv.com Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit In-Reply-To: <1107277309.4411.60.camel@master.vms.security> Sender: xen-devel-admin@lists.sourceforge.net Errors-To: xen-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: Mark Williamson Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Okay, after a little RTFM, I have the the frontend domain putting it's vif in the correct backend domain (not dom0) and the backend domain properly configured to be a backend domain (backend(netif)) in the sxp config. Don't I feel silly. However, running the ping test still kills the nic. If I run it from the front end domain, I get the disabling IRQ 18 error message in that dom. If I run it external to the physical box, the NIC still dies, however if I run the NICs from dom0, everything is fine. For testing purposes, I'm using the SAME xen0 for booting both xen0 and the backend domain. Regards, B. On Tue, 2005-02-01 at 13:01, B.G. Bruce wrote: > 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 " 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! > > > > [] > > > > [] > > > > [] > > > > [] > > > > [] > > > > [] > > > > [] > > > > [] > > > > [] > > > > handlers: > > > > [] > > > > [] > > > > 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@lists.sourceforge.net > > > > 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@lists.sourceforge.net > 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