[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] Xen-unstable: irq.c:xxxx: dom1: forcing unbind of pirq 40

>>> On 09.12.14 at 17:24, <linux@xxxxxxxxxxxxxx> wrote:
> Currently i'm running Xen-unstable with Stefano's libxl fixup patches (not 
> doing 
> reset due to qmp race, switching order of xc_domain_irq_permission and 
> xc_physdev_unmap_pirq)
> and with a kernel with Konrad's 3.19 patch series. 
> Although i have seen these messages before, so i don't know if it is a 
> recent 
> regression (don't think so). 
> I still see these in xl dmesg when shutting down guests with pci 
> passthrough:
> "irq.c:xxxx: dom1: forcing unbind of pirq 40"
> It seems to cleanup ok afterwards, but from the sound warning it shouldn't 
> get
> to that point. I get these for both PV and HVM guests.

These messages simply indicate that the guest didn't do some
expected cleanup itself. I see these too when Dom0 shuts down,
at least for certain drivers. For HVM arguably qemu might know
better and tear things down properly, but in no event are these
messages - when occurring in connection with a guest going
down - indications of a problem. We could even see to lower their
severity or suppress them altogether when the domain is known
to be dying (you may want to check whether ->is_dying is already
set at that point).


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.