Mailinglist Archive: opensuse-bugs (4250 mails)

< Previous Next >
[Bug 1018741] after Xen 4.7 -> 4.8 upgrade, Xen PVHVM/UEFI guests fail to boot; hang @~ OVMF
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Thu, 12 Jan 2017 16:17:41 +0000
  • Message-id: <bug-1018741-21960-rOZIuTpvTy@http.bugzilla.opensuse.org/>
http://bugzilla.opensuse.org/show_bug.cgi?id=1018741
http://bugzilla.opensuse.org/show_bug.cgi?id=1018741#c42

--- Comment #42 from lists dev <lists@xxxxxxxxxxxx> ---
staring at the diff, added multiple obvious module/driver differences

in the Guest,

edit /etc/dracut.conf.d/99-xen-domu.conf
...
add_dracutmodules+=" lunmask resume"
add_drivers+=" xen-blkfront xen-netback xen-netfront"

then just

mkinitrd
etc etc

with those^ adds, guest boot still fails, but @ xl console, I *do* now drop to
the dracut shell

...
( lots of these timeout msgs )
[ 189.751248] dracut-initqueue[358]: Warning: dracut-initqueue timeout -
starting timeout scripts
[ 190.299790] dracut-initqueue[358]: Warning: dracut-initqueue timeout -
starting timeout scripts
[ 190.849995] dracut-initqueue[358]: Warning: dracut-initqueue timeout -
starting timeout scripts
[ 191.399126] dracut-initqueue[358]: Warning: dracut-initqueue timeout -
starting timeout scripts
[ 191.942188] dracut-initqueue[358]: Starting Setup Virtual
Console...Warning: dracut-initqueue timeout - starting timeout scripts
[ OK ] Started Setup Virtual Console.
[ 192.105782]
Starting Dracut Emergency Shell...dracut-initqueue[358]: Warning:
Could not boot.
[ 192.119941]
dracut-initqueue[358]: Warning: /dev/mapper/VG0_T_BOOT1 does not
existWarning: /dev/mapper/VG0_T_BOOT1 does not exist

[ 192.134505] dracut-initqueueWarning: /dev/mapper/VG0_T_EFI1 does not
exist
[358]: Warning: /dev/mapper/VG0_T_EFI1 does not exist

Generating "/run/initramfs/rdsosreport.txt"


Entering emergency mode. Exit the shell to continue.
Type "journalctl" to view system logs.
You might want to save "/run/initramfs/rdsosreport.txt" to a USB stick or
/boot
after mounting them and attach it to a bug report.


dracut:/#


not clear why it's not directly finding the mounts, as they're seen at the
shell

dracut:/# blkid -s TYPE
/dev/xvda1: TYPE="vfat"
/dev/xvde1: TYPE="ext4"
/dev/xvdf1: TYPE="swap"
/dev/xvdg1: TYPE="ext4"

related to that hardcoded path maybe? udev timing?

in any case, clearly some 'sensitivity' to dracut config.

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >
References