I wonder if this is the point where things went wrong. Googling pointed me to
http://comments.gmane.org/gmane.linux.redhat.fedora.general/453737
and
https://bugzilla.redhat.com/show_bug.cgi?id=1187007
I wonder if the following might help:
echo 'hostonly_cmdline="no"' >/etc/dracut.conf.d/no_hostonly_cmdline.conf
I first checked for defaults in place @ the Xen guest; they DO exist grep hostonly /etc/dracut.conf.d/* /etc/dracut.conf.d/* /etc/dracut.conf.d/01-dist.conf:hostonly="yes" /etc/dracut.conf.d/01-dist.conf:hostonly_cmdline="yes" namely cat /etc/dracut.conf.d/01-dist.conf # SUSE specifc dracut settings # # SUSE by default always builds a as small as possible initrd for performance # and resource reasons. # If you like to build a generic initrd which works on other platforms than # on the one dracut/mkinitrd got called comment out below setting(s). hostonly="yes" hostonly_cmdline="yes" ... Changing, there hostonly="yes" - hostonly_cmdline="yes" + hostonly_cmdline="no" then for uname -a Linux guest03 3.18.6-1.gec2a744-xen #1 SMP Fri Feb 6 21:35:46 UTC 2015 (ec2a744) x86_64 x86_64 x86_64 GNU/Linux after an upgrade to latest rpm -qa | grep -i ^xen xen-libs-4.5.0_03-350.1.x86_64 xen-tools-domU-4.5.0_03-350.1.x86_64 linking (manually, because grubonce doesn't seem to 'take' @ the guest ...) cd /boot ln -sf initrd-3.19.0-1.g8a7d5f9-xen initrd-xen ln -sf vmlinuz-3.19.0-1.g8a7d5f9-xen vmlinuz-xen mkinitrd after shutdown -r now the guest is, again, no longer accessible via ssh. checking via remote console, the guest IS up uname -a Linux guest03 3.19.0-1.g8a7d5f9-xen #1 SMP Wed Feb 11 08:59:56 UTC 2015 (8a7d5f9) x86_64 x86_64 x86_64 GNU/Linux but there's no apparent net access ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. From xx.xx.xx.xx icmp_seq=1 Destination Host Unreachable From xx.xx.xx.xx icmp_seq=2 Destination Host Unreachable ... although 'network' service claims to be up systemctl status network wicked.service - wicked managed network interfaces Loaded: loaded (/etc/systemd/system/wicked.service; enabled) Active: active (exited) since Wed 2015-02-18 06:48:25 PST; 5min ago Process: 646 ExecStart=/usr/sbin/wicked --systemd ifup all (code=exited, status=0/SUCCESS) Main PID: 646 (code=exited, status=0/SUCCESS) CGroup: /system.slice/wicked.service Feb 18 06:48:25 edge wicked[646]: lo up Feb 18 06:48:25 edge wicked[646]: eth0 up rebooting successfully to 3.18.x, ln -sf vmlinuz-3.18.6-1.gec2a744-xen vmlinuz-xen ln -sf initrd-3.18.6-1.gec2a744-xen initrd-xen mkinitrd shutdown -r now ssh, and obviously network, are again up uname -a Linux guest03 3.18.6-1.gec2a744-xen #1 SMP Fri Feb 6 21:35:46 UTC 2015 (ec2a744) x86_64 x86_64 x86_64 GNU/Linux wicked? then again, with the state it's in, I *always* suspect wicked ... -- To unsubscribe, e-mail: opensuse-kernel+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kernel+owner@opensuse.org