On Mon, Feb 15, 2016 at 12:45 AM, Paul Gonin
To be able to boot my newer skylake hidpi on nvme I finally opted to this kind of command line BOOT_IMAGE=/vmlinuz-4.4.0-3-default root=/dev/mapper/vg0-lvtwroot root=LABEL=TWROOT elevator=cfq crashkernel=512M-:256M rd.vconsole.keymap=ch-fr rd.vconsole.font=ter-v32b.psfu rd.locale.LANG=en_US.UTF-8 rd.luks.allow-discard showopts nosplash quiet luks=yes Anyone reported the issue already ? On my side, I can't access my luks based device and a consequence is
I don't know if this is relevant, but... I have a fresh load of TW on a Dell server, and, within that, a fresh load of TW as a Xen DomU guest. Following the most recent update, I am still able to boot my physical host, but pygrub can no longer boot my DomU. In fact, pygrub -l aborts with no output, suggesting it can't even understand the DomU. I had to extract the kernel and initrd from the DomU manually to the Dom0 host, and use that in similar fashion (specifying kernel and initrd manually) to get my DomU to boot. (And my dom0 has 34 instances of [bioset] running, but that may be orthogonal.)
sorry need coffee... I meant reported the bug in bugzilla.
I may well have the same issue... Glen -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org