I've recently upgraded pkgs an Opensuse 12.3 + XEN 4.3
(xen-4.3.0_08-264.1.x86_64) server.

It's got two guests set for auto-launch @ boot.

It's been working fine for awhile.  The guest cfg's have not changed in
ages.  Just the upgrade has occured recently.

Now, reproducibly after boot, one Guest is missing,

        xl list
                Name                                        ID   Mem
                VCPUs      State   Time(s)
                (null)                                       0   985    
                4     r-----      44.2             <====== Why "(null)"
                here? systemd?
                test2                                        2  1024    
                4     -b----      13.3

but launches manually 

        xl create /etc/xen/auto/test1.cfg
        xl list
                Name                                        ID   Mem
                VCPUs      State   Time(s)
                (null)                                       0   985    
                4     r-----      48.2
                test2                                        2  1024    
                4     -b----      13.8
                test1                                        3   768    
                2     -b----       2.3

and functions normally.

checking xen boot logs, I find these, new failures

        xl dmesg
                ...
                [  OK  ] Started Haveged Entropy Gathering Daemon.
                [  OK  ] Started Restore Sound Card State.
                [  OK  ] Started LSB: irqbalance daemon providing irq
                balancing on MP-machines.
                [  OK  ] Started LSB: Framebuffer setup.
                [   35.614880] Event-channel device installed.
                [   35.677851] usbcore: registered new interface driver
                usbback
                [   35.711552] pciback: backend is vpci
                [   35.748410] blktap_device_init: blktap device major
                252

                Welcome to openSUSE 12.3 "Dartmouth" - Kernel
                3.7.10-1.16-xen (xvc0).


                testsvr login:

                (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
                [  OK  ] Started LSB: Configure network interfaces and
                set up routing.
                [  OK  ] Reached target Network.
                         Starting Command Scheduler...
                ...

Those

        "event_channel.c:233:d0 EVTCHNOP failure: domain 2, error -22"

errors are new to me.

Looks like a XEN issue.  I've seen recent work on event channel deadlock
on the dev list, but my xen's logs don't mention anything evtchn-related
since ~ Nov 2011.

Before deciding to file a bug, I need to do some local troubleshooting.

Any suggestions as to what this might be about, or specific additional
info that might be enlightening?

AR
-- 
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]

Reply via email to