Bug 15293

Summary:	5b3 Kde-Live-Iso wont boot in qemu in efi-mode because of wrong cmdline
Product:	Mageia	Reporter:	Lutz Lacher <l.lacher>
Component:	Release (media or process)	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	ennael1, l.lacher, sysadmin-bugs, tmb
Version:	Cauldron
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	rdsosreport with UEFI in cmdline

Description Lutz Lacher 2015-02-14 13:32:40 CET

Description of problem:

I just tried to boot Mageia-5-beta3-Live4-x86_64-DVD.iso in qemu in EFI-mode, and there are two Problems i think:

The cmdline from grub menu is 

BOOT_IMAGE=/boot/vmlinuz root=mgalive:LABEL=MGALIVE UEFI quiet rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0

but the filesystem's label is (from blkid)

/dev/sr0: UUID="2015-02-11-21-53-27-00" LABEL="Mageia-5-KDE4-LiveDVD" TYPE="iso9660" PTUUID="119a5c31" PTTYPE="dos"

Correcting the label in grub to Mageia-5-KDE4-LiveDVD leads to (from rdsosreport)

[    1.488665] cdrom: Uniform CD-ROM driver Revision: 3.20
[    1.489359] sr 1:0:0:0: Attached scsi CD-ROM sr0
[    1.577958] FAT-fs (sr0): invalid media value (0x90)
[    1.579164] FAT-fs (sr0): Can't find a valid FAT filesystem

The rdsosreport from that boot is attached. I was able to boot with the corrected label and removing UEFI from cmdline, so it now reads:

BOOT_IMAGE=/boot/vmlinuz root=mgalive:LABEL=Mageia-5-KDE4-LiveDVD rd.luks=0 rd.lvm=0 rd.md=0 rd.dm=0



Reproducible: 

Steps to Reproduce:

Comment 1 Lutz Lacher 2015-02-14 13:34:03 CET

Created attachment 5917 [details]
rdsosreport with UEFI in cmdline

Lutz Lacher 2015-02-14 13:34:17 CET

CC: (none) => l.lacher

Thierry Vignaud 2015-02-14 14:52:42 CET

CC: (none) => ennael1, sysadmin-bugs, tmb
Component: Installer => Release (media or process)

Comment 2 Thomas Backlund 2015-02-14 18:13:55 CET

Crap, so it boots according to the grub.cfg meant for USB installs, instead of reading the correct uefi boot info from efiboot.img that is tagged as efi boot data on the iso :/


I guess I need to re-add the separate "from USB" enties to work around this.

Comment 3 Samuel Verschelde 2015-06-01 00:08:28 CEST

A lot has changed and I think it's fixed.

Status: NEW => RESOLVED
Resolution: (none) => FIXED