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

[Xen-devel] stub domain crash related to bind_interdomain


  • To: "xen-devel@xxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxx>
  • From: Sarah Newman <srn@xxxxxxxxx>
  • Date: Mon, 19 Jun 2017 16:39:13 -0700
  • Delivery-date: Mon, 19 Jun 2017 23:39:33 +0000
  • Dkim-filter: OpenDKIM Filter v2.11.0 mail.prgmr.com DD95528C126
  • List-id: Xen developer discussion <xen-devel.lists.xen.org>

I have gotten messages like this sporadically in the qemu-dm log for stub 
domains, both at domain start and domain reboot:

evtchn_open() -> 7
ERROR: bind_interdomain failed with rc=-22xenevtchn_bind_interdomain(121, 0) = 
-22
bind interdomain ioctl error 22
Unable to find x86 CPU definition
close(0)

It is not always remote port 0 that fails but typically is so.

We recently upgraded to xen 4.8.1. When I look at the code, what seems like the 
most likely case for failure is this check in
xen/event_channel.c:evtchn_bind_interdomain:

    if ( (rchn->state != ECS_UNBOUND) ||
         (rchn->u.unbound.remote_domid != ld->domain_id) )
        ERROR_EXIT_DOM(-EINVAL, rd);

But I don't know how this could happen.

Was there a fix for this since the 4.8.1 release that I missed? I was not 
successful in finding anything related in the xen-devel logs since April 10
or in the git repositories.

Please keep me CC'ed.

Thanks, Sarah

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
https://lists.xen.org/xen-devel

 


Rackspace

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