On 15.08.13 at 04:17, ar16 <ar16@imapmail.org> wrote: (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22 (XEN) [2013-08-15 01:42:22] event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22
These being failures of Dom0 trying to bind inter-domain event channels between itself and Dom2, these would quite likely be accompanied by some log entries from the xen tools or the Dom0 kernel. In any case - the failure message here indicates that the event channel either wasn't in "unbound" state, or wasn't intended to be bound to by Dom0. For what it's worth, both seem pretty unlikely... Furthermore, you certainly realize that with the update to Xen 4.3, which isn't part of 12.3, you also got switched from xend/xm to the libxl based tools, which may be part of your problem. Thus it would also be important to know what's so specific about this one failing VM (there ought to be something, or else it wouldn't be always the same VM that fails to come up). Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org