On Fri, Jan 6, 2017, at 03:17 PM, Mike Latimer wrote:
> Thanks for reporting the problem, and please let us know how your 4.8 testing 
> goes.

Once everything propagated to the repos, I upgraded to

        xen             4.8.0_01-466.1
        xen-libs        4.8.0_01-466.1
        xen-tools       4.8.0_01-466.1
        kernel-default  4.9.1-2.1.g1072b39

Checking, there's no dangling link anymore

        ls -al /usr/bin/xenstore-ls
                lrwxrwxrwx 1 root root 8 Jan  6 16:37 /usr/bin/xenstore-ls -> 
xenstore*
        ls -al /usr/bin/xenstore
                -rwxr-xr-x 1 root root 19K Jan  6 13:24 /usr/bin/xenstore*

Reboot now completes

        Welcome to openSUSE Leap 42.2 - Kernel 4.9.1-2.g1072b39-default (hvc0).

        xent login: root
        Password:
        Last login: Fri Jan  6 14:56:48 from 192.168.1.19
        Have a lot of fun...

Previously working DomUs come up on boot

        xl list
                Name        ID   Mem VCPUs      State   Time(s)
                Domain-0     0  2048     1     r-----      51.1
                opensuse     1  1024     1     -b----       7.0

but are not accessible anymore either via console, or their individual, 
embedded sshd's

        xl console 1

                
������������������������������������������������������������������������������Ŀ
                �                                    ERROR                      
               �
                �                                                               
               �
                �                   Verification failed: (15) Access Denied     
               �
                �                                                               
               �
                �                                                               
               �
                �                                                               
               �
                �                                                               
               �
                �                                                               
               �
                �                                                               
               �
                �                                     ����Ŀ                     
               �
                �                                     � OK �                    
               �
                �                                     �����                     
               

                Trust openSUSE Certificate                          �
                �                                                               
               �
                �            Do you agree to use the built-in openSUSE 
certificate             �
                �                     to verify boot loaders and kernels?       
               �
                �                                                               
               �
                �                                    �����Ŀ                     
               �
                �                                    � No  �                    
               �
                �                                    � Yes �                    
               �1
                �                                    �������         

                
������������������������������������������������������������������������������Ŀ
                �                                    ERROR                      
               �
                �                                                               
               �
                �          Could not install security protocol: (2) Invalid 
Parameter          �
                �                                                               
               �
                �                                                               
               �
                �                                                               
               �
                �                                                               
               �
                �                                                               
               �
                �                                                               
               �
                �                                     ����Ŀ                     
               �
                �                                     � OK �                    
               �
                �                                     �����                     
               �

I don't know what to do with all that yet.  I've tried any/all of the DomUs I'd 
had working; everyone of them's the same so far.

1st look at

        journalctl -f

on the Dom0, from launching the DomU to the 1st error on boot,

        Jan 06 17:48:00 xent.lanint systemd-udevd[894]: seq 3317 queued, 'add' 
'xen-backend'
        Jan 06 17:48:01 xent.lanint systemd-udevd[894]: Validate module index
        Jan 06 17:48:01 xent.lanint systemd-udevd[894]: Check if link 
configuration needs reloading.
        Jan 06 17:48:01 xent.lanint systemd-udevd[894]: seq 3317 forked new 
worker [4992]
        Jan 06 17:48:01 xent.lanint systemd-udevd[4992]: seq 3317 running
        Jan 06 17:48:01 xent.lanint systemd-udevd[4992]: IMPORT builtin 'hwdb' 
/usr/lib/udev/rules.d/50-udev-default.rules:15
        Jan 06 17:48:01 xent.lanint systemd-udevd[4992]: IMPORT builtin 'hwdb' 
returned non-zero
        Jan 06 17:48:01 xent.lanint systemd-udevd[4992]: RUN 'kmod load 
$env{MODALIAS}' /usr/lib/udev/rules.d/80-drivers.rules:5
        Jan 06 17:48:01 xent.lanint systemd-udevd[4992]: Execute 'load' 
'xen-backend:vbd'
        Jan 06 17:48:01 xent.lanint systemd-udevd[4992]: Inserted 'xen_blkback'
        Jan 06 17:48:01 xent.lanint systemd-sysctl[5394]: Parsing 
/usr/lib/sysctl.d/50-coredump.conf
        Jan 06 17:48:01 xent.lanint systemd-sysctl[5394]: Parsing 
/usr/lib/sysctl.d/50-default.conf
        Jan 06 17:48:01 xent.lanint systemd-sysctl[5394]: Parsing 
/etc/sysctl.d/99-sysctl.conf
        Jan 06 17:48:01 xent.lanint systemd[2006]: 
sys-subsystem-net-devices-vif4.0\x2demu.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint systemd[2006]: 
sys-devices-virtual-net-vif4.0\x2demu.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint systemd[1]: 
sys-subsystem-net-devices-vif4.0\x2demu.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint systemd[1]: 
sys-devices-virtual-net-vif4.0\x2demu.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint systemd[1]: Sent message type=signal 
sender=n/a destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=UnitNew cookie=223 
reply_cookie=0 error=n/a
        Jan 06 17:48:01 xent.lanint systemd[1]: Sent message type=signal 
sender=n/a destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=UnitNew cookie=224 
reply_cookie=0 error=n/a
        Jan 06 17:48:01 xent.lanint systemd-sysctl[5403]: Parsing 
/usr/lib/sysctl.d/50-coredump.conf
        Jan 06 17:48:01 xent.lanint systemd-sysctl[5403]: Parsing 
/usr/lib/sysctl.d/50-default.conf
        Jan 06 17:48:01 xent.lanint systemd-sysctl[5403]: Parsing 
/etc/sysctl.d/99-sysctl.conf
        Jan 06 17:48:01 xent.lanint systemd[2006]: 
sys-subsystem-net-devices-vif4.0.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint systemd[2006]: 
sys-devices-vif\x2d4\x2d0-net-vif4.0.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint systemd[1]: 
sys-subsystem-net-devices-vif4.0.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint systemd[1]: 
sys-devices-vif\x2d4\x2d0-net-vif4.0.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint systemd[1]: Sent message type=signal 
sender=n/a destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=UnitNew cookie=225 
reply_cookie=0 error=n/a
        Jan 06 17:48:01 xent.lanint systemd[1]: Sent message type=signal 
sender=n/a destination=n/a object=/org/freedesktop/systemd1 
interface=org.freedesktop.systemd1.Manager member=UnitNew cookie=226 
reply_cookie=0 error=n/a
        Jan 06 17:48:01 xent.lanint kernel: vif vif-4-0 vifT: renamed from 
vif4.0
        Jan 06 17:48:01 xent.lanint systemd[2006]: 
sys-subsystem-net-devices-vif4.0.device: Dev 
sys-subsystem-net-devices-vif4.0.device appeared twice with different sysfs 
paths /sys/devices/vif-4-0/net/vif4.0 and /sys/devices/vif-4-0/net/vifT
        Jan 06 17:48:01 xent.lanint systemd[2006]: 
sys-subsystem-net-devices-vifT.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint systemd[2006]: 
sys-devices-vif\x2d4\x2d0-net-vifT.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint systemd[1]: 
sys-subsystem-net-devices-vif4.0.device: Dev 
sys-subsystem-net-devices-vif4.0.device appeared twice with different sysfs 
paths /sys/devices/vif-4-0/net/vif4.0 and /sys/devices/vif-4-0/net/vifT
        Jan 06 17:48:01 xent.lanint systemd[1]: 
sys-subsystem-net-devices-vifT.device: Changed dead -> plugged
        Jan 06 17:48:01 xent.lanint kernel: br0: port 2(vifT) entered blocking 
state
        Jan 06 17:48:01 xent.lanint kernel: br0: port 2(vifT) entered disabled 
state
        Jan 06 17:48:01 xent.lanint kernel: device vifT entered promiscuous mode
        Jan 06 17:48:02 xent.lanint kernel: IPv6: ADDRCONF(NETDEV_UP): vifT: 
link is not ready
        Jan 06 17:48:02 xent.lanint kernel: vifT-emu: renamed from vif4.0-emu
        Jan 06 17:48:02 xent.lanint systemd[2006]: 
sys-subsystem-net-devices-vif4.0\x2demu.device: Dev 
sys-subsystem-net-devices-vif4.0\x2demu.device appeared twice with different 
sysfs paths /sys/devices/virtual/net/vif4.0-emu and 
/sys/devices/virtual/net/vifT-emu
        Jan 06 17:48:02 xent.lanint systemd[2006]: 
sys-subsystem-net-devices-vifT\x2demu.device: Changed dead -> plugged
        Jan 06 17:48:02 xent.lanint systemd[2006]: 
sys-devices-virtual-net-vifT\x2demu.device: Changed dead -> plugged
        Jan 06 17:48:02 xent.lanint kernel: br0: port 3(vifT-emu) entered 
blocking state
        Jan 06 17:48:02 xent.lanint kernel: br0: port 3(vifT-emu) entered 
disabled state
        Jan 06 17:48:02 xent.lanint kernel: device vifT-emu entered promiscuous 
mode
        Jan 06 17:48:02 xent.lanint kernel: br0: port 3(vifT-emu) entered 
blocking state
        Jan 06 17:48:02 xent.lanint kernel: br0: port 3(vifT-emu) entered 
listening state
        Jan 06 17:48:00 xent.lanint root[5036]: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/4/51712
        Jan 06 17:48:00 xent.lanint root[5037]: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/4/51776
        Jan 06 17:48:00 xent.lanint root[5041]: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/4/51808
        Jan 06 17:48:00 xent.lanint root[5038]: /etc/xen/scripts/block: add 
XENBUS_PATH=backend/vbd/4/51792
        Jan 06 17:48:00 xent.lanint root[5177]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51712/physical-device fe:d to xenstore.
        Jan 06 17:48:00 xent.lanint root[5179]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51712/physical-device-path /dev/dm-13 to xenstore.
        Jan 06 17:48:00 xent.lanint root[5181]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51712/hotplug-status connected to xenstore.
        Jan 06 17:48:00 xent.lanint root[5247]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51776/physical-device fe:e to xenstore.
        Jan 06 17:48:00 xent.lanint root[5249]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51776/physical-device-path /dev/dm-14 to xenstore.
        Jan 06 17:48:00 xent.lanint root[5251]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51776/hotplug-status connected to xenstore.
        Jan 06 17:48:00 xent.lanint root[5315]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51808/physical-device fe:10 to xenstore.
        Jan 06 17:48:00 xent.lanint root[5317]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51808/physical-device-path /dev/dm-16 to xenstore.
        Jan 06 17:48:00 xent.lanint root[5319]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51808/hotplug-status connected to xenstore.
        Jan 06 17:48:01 xent.lanint root[5381]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51792/physical-device fe:f to xenstore.
        Jan 06 17:48:01 xent.lanint root[5383]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51792/physical-device-path /dev/dm-15 to xenstore.
        Jan 06 17:48:01 xent.lanint root[5385]: /etc/xen/scripts/block: Writing 
backend/vbd/4/51792/hotplug-status connected to xenstore.
        Jan 06 17:48:01 xent.lanint root[5414]: /etc/xen/scripts/vif-bridge: 
online type_if=vif XENBUS_PATH=backend/vif/4/0
        Jan 06 17:48:01 xent.lanint root[5442]: /etc/xen/scripts/vif-bridge: 
Successful vif-bridge online for vifT, bridge br0.
        Jan 06 17:48:01 xent.lanint root[5443]: /etc/xen/scripts/vif-bridge: 
Writing backend/vif/4/0/hotplug-status connected to xenstore.
        Jan 06 17:48:01 xent.lanint root[5455]: /etc/xen/scripts/vif-bridge: 
add type_if=tap XENBUS_PATH=backend/vif/4/0
        Jan 06 17:48:01 xent.lanint root[5483]: /etc/xen/scripts/vif-bridge: 
Successful vif-bridge add for vifT-emu, bridge br0.
        Jan 06 17:48:03 xent.lanint kernel: xen-blkback: backend/vbd/4/51712: 
using 1 queues, protocol 1 (x86_64-abi)
        Jan 06 17:48:03 xent.lanint kernel: xen-blkback: backend/vbd/4/51776: 
using 1 queues, protocol 1 (x86_64-abi)
        Jan 06 17:48:03 xent.lanint kernel: xen-blkback: backend/vbd/4/51792: 
using 1 queues, protocol 1 (x86_64-abi)
        Jan 06 17:48:03 xent.lanint kernel: xen-blkback: backend/vbd/4/51808: 
using 1 queues, protocol 1 (x86_64-abi)
        Jan 06 17:48:05 xent.lanint kernel: br0: port 3(vifT-emu) entered 
learning state
        Jan 06 17:48:09 xent.lanint kernel: br0: port 3(vifT-emu) entered 
forwarding state
        Jan 06 17:48:09 xent.lanint kernel: br0: topology change detected, 
propagating

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

Reply via email to