82599 passthrough problem

82599 passthrough problem

[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? thanks.

Re: 82599 passthrough problem

[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 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

Re: 82599 passthrough problem

[Norton.Zhu]

XEN HVM, after it hung, no serial log printed.
it hang in __pirq_guest_unbind. its call stack as follows:
(XEN)    [<ffff82c4801682d6>] __pirq_guest_unbind+0x36/0x350
(XEN)    [<ffff82c4801682d6>] __pirq_guest_unbind+0x36/0x350
(XEN)    [<ffff82c480186e7b>] do_invalid_op+0x30b/0x3f0
(XEN)    [<ffff82c48017e22c>] flush_area_mask+0x7c/0x130
(XEN)    [<ffff82c480217808>] handle_exception_saved+0x30/0x6e
(XEN)    [<ffff82c4801682cc>] __pirq_guest_unbind+0x2c/0x350
(XEN)    [<ffff82c4801667a4>] domain_spin_lock_irq_desc+0x64/0xa0
(XEN)    [<ffff82c4801689ed>] pirq_guest_unbind+0x5d/0x170
(XEN)    [<ffff82c480141d9e>] pci_release_devices+0x13e/0x230
(XEN)    [<ffff82c48015df28>] domain_relinquish_resources+0xa8/0x2a0

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
> 
> 

Re: 82599 passthrough problem

[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)    [<ffff82c4801682d6>] __pirq_guest_unbind+0x36/0x350
> (XEN)    [<ffff82c4801682d6>] __pirq_guest_unbind+0x36/0x350
> (XEN)    [<ffff82c480186e7b>] do_invalid_op+0x30b/0x3f0
> (XEN)    [<ffff82c48017e22c>] flush_area_mask+0x7c/0x130
> (XEN)    [<ffff82c480217808>] handle_exception_saved+0x30/0x6e
> (XEN)    [<ffff82c4801682cc>] __pirq_guest_unbind+0x2c/0x350
> (XEN)    [<ffff82c4801667a4>] domain_spin_lock_irq_desc+0x64/0xa0
> (XEN)    [<ffff82c4801689ed>] pirq_guest_unbind+0x5d/0x170
> (XEN)    [<ffff82c480141d9e>] pci_release_devices+0x13e/0x230
> (XEN)    [<ffff82c48015df28>] 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
> > 
> > 
>