http://bugzilla.opensuse.org/show_bug.cgi?id=1018741 http://bugzilla.opensuse.org/show_bug.cgi?id=1018741#c47 --- Comment #47 from lists dev <lists@ssl-mail.com> --- fyi, chroot into an opensuse pvhvm guest mkinitrd exit chroot launch guest -> FAILs destroy guest re-enter chroot mkinitrd -A launch guest -> BOOTS OK `xl console` into running guest mkinitrd -A reboot guest -> BOOTS OK `xl console` into running guest mkinitrd reboot guest -> BOOTS OK destroy guest re-enter chroot mkinitrd launch guest -> FAILs destroy guest re-enter chroot mkinitrd -A launch guest -> BOOTS OK rinse/repeat, ad infinitum ... There's something obviously unhealthy about in-chroot, 'just' `mkinitrd`. I'm not sure how any of that explains why the chroot + mkinitrd -A was needed on the unhacked-guests, after the 4.7 -> 4.8 upgrade -- apparently, just the once to get it to boot, post-upgrade the 1st time. -- You are receiving this mail because: You are on the CC list for the bug.