From: Wei Liu <wei.liu2@citrix.com>
To: xen-devel@lists.xen.org
Cc: wei.liu2@citrix.com
Subject: [POSSIBLE BUG] Failure to bind event channel
Date: Wed, 15 Jan 2014 12:30:45 +0000 [thread overview]
Message-ID: <20140115123045.GL5698@zion.uk.xensource.com> (raw)
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
(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.
next reply other threads:[~2014-01-15 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-15 12:30 Wei Liu [this message]
2014-01-15 12:37 ` [POSSIBLE BUG] Failure to bind event channel Ian Campbell
2014-01-15 14:29 ` Wei Liu
2014-01-15 14:34 ` Julien Grall
2014-01-28 16:55 ` Wei Liu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140115123045.GL5698@zion.uk.xensource.com \
--to=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.