Re: [Xen-devel] [POSSIBLE BUG] Failure to bind event channel

[Ian Campbell <Ian.Campbell@xxxxxxxxxx>]

On Wed, 2014-01-15 at 12:30 +0000, Wei Liu wrote:
> Xen: master branch
> Dom0 Linux: git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip.git
>                linux-next
> 
> When I tried to start a HVM domain running squeeze with 2.6.32, I got
> 
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22

Julien mentioned having seen something very similar with BSD on ARM
yesterday...

> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> (XEN) event_channel.c:271:d0 EVTCHNOP failure: domain 5, error -22
> [... more of this ...]
> [67196.736733] device vif5.0 entered promiscuous mode
> [67196.746221] IPv6: ADDRCONF(NETDEV_UP): vif5.0: link is not ready
> [67196.911973] device vif5.0-emu entered promiscuous mode
> [67196.921890] xenbr0: port 3(vif5.0-emu) entered forwarding state
> [67196.927833] xenbr0: port 3(vif5.0-emu) entered forwarding state
> (d5) HVM Loader
> (d5) Detected Xen v4.4-unstable
> (d5) Xenbus rings @0xfeffc000, event channel 3
> (d5) System requested SeaBIOS
> (d5) CPU speed is 2660 MHz
> (d5) Relocating guest memory for lowmem MMIO space disabled
> (XEN) irq.c:270: Dom5 PCI link 0 changed 0 -> 5
> (d5) PCI-ISA link 0 routed to IRQ5
> (XEN) irq.c:270: Dom5 PCI link 1 changed 0 -> 10
> (d5) PCI-ISA link 1 routed to IRQ10
> 
> The guest was eventually up and running and seemed to be working fine.
> The failure in log was not that harmful after all... But it would be
> nice to figure out what's going on here. I suspect the toolstack was
> trying to setup something, failed, then retried and eventually succeed.
> Sadly the error log wasn't elaborated enough to provide direct insight
> into the root cause and I couldn't tell which side (toolstack, kernel,
> Xen) to blame.
> 
> The failing snippet in Xen common/event_channel.c
> 
> 269     if ( (rchn->state != ECS_UNBOUND) ||                                  
>       
> 270          (rchn->u.unbound.remote_domid != ld->domain_id) )                
>       
> 271         ERROR_EXIT_DOM(-EINVAL, rd);     
> 
> Wei.
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel



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