From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <liuw@liuw.name>
Cc: xen-devel@lists.xensource.com,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: Interrupt issue for nic cards
Date: Fri, 13 May 2011 09:39:31 -0400 [thread overview]
Message-ID: <20110513133931.GA6042@dumpdata.com> (raw)
In-Reply-To: <BANLkTi=e6bWKWMBD9WkM8QLfzgW3uKtRVA@mail.gmail.com>
On Fri, May 13, 2011 at 11:14:47AM +0800, Wei Liu wrote:
> Hi, all.
>
> I'm running the latest Xen unstable with Debian Squeeze as DomU in HVM mode.
>
> I configured two nics:
>
> vif = ['bridge=br0,model=virtio', 'type=ioemu,bridge=br0,model=rtl8139']
>
> These two cards can be successfully configured in DomU. But they fail
> to communicate with host bridge.
>
> I can see packets coming out their taps, but no packets are going back
> into DomU.
>
> Stefano suggest I look into /proc/interrupts. It shows:
>
> 11 0 IO-APIC-fasteoi eth0
> 48 0 PCI-MSI-edge virtio0-config
> 49 0 PCI-MSI-edge virtio0-input
> 50 0 PCI-MSI-edge virtio0-output
>
> It seems that there are no interrupts for those nic devices. I'm
> pretty sure that QEMU has pushed the data back and set interrupts
> (through msix_notify / qemu_set_irq).
>
> Has anyone encountered this problem before?
I haven't. But it looks like the NIC isn't beeing interrupted - which
implies that QEMU hasn't sent the IRQ to the DomU to tell it: 'hey
you got data'. It might be worth looking in QEMU and see under which
circumstances it sends interrupts. And whether the mechanism for sending
interrupts is KVM specific instead of being more generic (or able to
use the Xen mechanism).
>
> --
> Best regards
> Wei Liu
> Twitter: @iliuw
> Site: http://liuw.name
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-13 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 3:14 Interrupt issue for nic cards Wei Liu
2011-05-13 13:39 ` Konrad Rzeszutek Wilk [this message]
2011-05-13 13:49 ` Stefano Stabellini
2011-05-13 14:06 ` Wei Liu
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=20110513133931.GA6042@dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=liuw@liuw.name \
--cc=stefano.stabellini@eu.citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).