Re: [Xen-devel] 82599 passthrough problem

2016-02-17 Thread Konrad Rzeszutek Wilk
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

Re: [Xen-devel] 82599 passthrough problem

2016-02-03 Thread Norton.Zhu
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_s

Re: [Xen-devel] 82599 passthrough problem

2016-02-03 Thread Konrad Rzeszutek Wilk
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 fr

[Xen-devel] 82599 passthrough problem

2016-02-01 Thread Norton.Zhu
Hi,all: I met a problem when passthrough 82599 to domU(for some reasons, I use pci passthrough not SRIOV). 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? thank