Created attachment 9075 [details] prompt I got dropped to at first for Mageia sta2, I installed to a usb stick as a hard drive which worked but it would not boot after that. This is in Virtualbox 5.1.10 I ran Virtualbox 5.1.10 inside Mageia 5 up to date, with vb extentions installed. I downloaded mageia.sta2 and mounted that iso to a new VM. on the vm I checked [x] Enable EFI (in System tab). on vm in USB tab I attached my SanDisk 32gb usb stick/drive. I booted vm and successfully installed mageia sta2. I let it use whole usb drive to partition as it wanted. I removed iso from vm and rebooted. Problem. I left me at a UEFI shell prompt. Fix I figured out. Mageia sta2 did not create a startup.nsh file on the 300mb EF partition so I guess it did not know what to continue booting from. simple fix. I did fs0: to get to another prompt (that is zero) and I created the file. Now it boots find by itself. startup.nsh: 2 lines FS0: \EFI\mageia\grubx64.efi when I created the file there seemed to be \EFI\EF\mageia directories but I only pointed to one \EFI in the startup.nsh file. see attached pictures. Stan Towianski
Created attachment 9076 [details] fix picture of fix
CC: (none) => stashu.pub
Which iso did you use to install from, one of the Lives (which one?) or the classical iso? If it was one of the Lives, then please attach journal.txt that is the result of running in that installed system, as root: journalctl -ab1 > journal.txt (Compress with xz if it's too large to attach) If it was the classical install, then please attach /root/drakx/report.bug.xz from that installed system.
Keywords: (none) => NEEDINFOCC: (none) => isobuild, marja11
I think this is more a VBox issue than Mageia e.g.: https://www.virtualbox.org/ticket/14279 I did write something about this for an errata/wiki a few years ago but cannot find it now :\ @stan Yes that fix is similar to what I use in VBox with UEFI - shutting down the VM wipes VBox's virtual nvram. You can also add a conditional to try fs1: if EFI is not under fs0: as is the case if there is a CD in the drive.
CC: (none) => zen25000
Created attachment 9083 [details] /root/drakx/report.bug.xz
Barry, I assume you would need a physical file (startup.nsh) to be created on a vm or non-vm box. It did not exist after installation. Reading the ticket you point to, it does seem relevant. I do not know that process. Does linux use nvram process also and flush/writes to disk and vbox does not? I see there was not response to the problem. If vbox is doing something non-standard I would think they should fix it/change it. Probably have to talk to them. That was on older vbox 4.3.30 version though. 2.) Yes, in creating startup.nsh you might have to account for the install dvd going away after reboot, i.e. assume it will or do an IF if possible.
(In reply to Barry Jackson from comment #3) > I think this is more a VBox issue than Mageia e.g.: > https://www.virtualbox.org/ticket/14279 > > I did write something about this for an errata/wiki a few years ago but > cannot find it now :\ Thanks, Barry, I had totally forgotten about it, but found it: https://wiki.mageia.org/en/EFI:_can_no_longer_boot_into_Mageia#Boot_Drops_to_UEFI_Shell_.28in_VirtualBox.29
Keywords: NEEDINFO => UPSTREAMComponent: Installer => RPM PackagesSee Also: (none) => https://www.virtualbox.org/ticket/14279Assignee: bugsquad => knightmbSource RPM: (none) => virtualboxWhiteboard: (none) => MGA5TOO
reasigning to our real tmb ;-)
Assignee: knightmb => tmb