From mboxrd@z Thu Jan 1 00:00:00 1970 From: Konrad Rzeszutek Wilk Subject: Re: 82599 passthrough problem Date: Wed, 17 Feb 2016 13:41:13 -0500 Message-ID: <20160217184113.GD24109@char.us.oracle.com> References: <56B02AD4.5090100@huawei.com> <20160203175405.GC1069@char.us.oracle.com> <56B2F2D8.40301@huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Content-Disposition: inline In-Reply-To: <56B2F2D8.40301@huawei.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: "Norton.Zhu" Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On Thu, Feb 04, 2016 at 02:42:32PM +0800, Norton.Zhu wrote: > XEN HVM, after it hung, no serial log printed. > it hang in __pirq_guest_unbind. its call stack as follows: > (XEN) [] __pirq_guest_unbind+0x36/0x350 > (XEN) [] __pirq_guest_unbind+0x36/0x350 > (XEN) [] do_invalid_op+0x30b/0x3f0 > (XEN) [] flush_area_mask+0x7c/0x130 > (XEN) [] handle_exception_saved+0x30/0x6e > (XEN) [] __pirq_guest_unbind+0x2c/0x350 > (XEN) [] domain_spin_lock_irq_desc+0x64/0xa0 > (XEN) [] pirq_guest_unbind+0x5d/0x170 > (XEN) [] pci_release_devices+0x13e/0x230 > (XEN) [] domain_relinquish_resources+0xa8/0x2a0 Any chance you can provide the xen-syms? Also what version of Xen is this? Is the passthrough done via pci-attach or via 'pci=' guest config? Does this happen all the time? What happens if you have 'sync_console' on the Xen command line? What happens if you detach (pci-detach) the PCI device from the guest before shutdown? Does it work? What version of QEMU are you using ? qemu-xen or qemu-traditional? Thanks. > > On 2016/2/4 1:54, Konrad Rzeszutek Wilk wrote: > > On Tue, Feb 02, 2016 at 12:04:36PM +0800, Norton.Zhu wrote: > >> Hi,all: > >> > >> I met a problem when passthrough 82599 to domU(for some reasons, I use pci passthrough not SRIOV). > > > > Is this PV or HVM? > > > >> It works well after passthrough, but the host hung after destroy domU. > >> Btw, no log prints even from serial port, but I found it hung afer unbind irq. > >> anyone knows what's wrong with it? thanks. > > > > Serial logs? > >> > >> > >> _______________________________________________ > >> Xen-devel mailing list > >> Xen-devel@lists.xen.org > >> http://lists.xen.org/xen-devel > > > > >