User Tools

Site Tools


virtualbox_efi_boot_failed

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

virtualbox_efi_boot_failed [2015/06/21 14:17]
pavroo created
virtualbox_efi_boot_failed [2015/06/21 17:51] (current)
pavroo
Line 4: Line 4:
  
 In most cases the VirtualBox will launch the EFI Shell. In most cases the VirtualBox will launch the EFI Shell.
 +
 +{{:​vbox-efi-shell.png?​450|VirtualBox Efi Shell}}
  
 To manually launch Sparky 64 bit version, run: To manually launch Sparky 64 bit version, run:
  
    ​fs0:​\EFI\sparky\grubx64.efi    ​fs0:​\EFI\sparky\grubx64.efi
 +
 +To manually launch Sparky 32 bit version, run:
 +
 +   ​fs0:​\EFI\sparky\grubia32.efi
  
 If you used [[http://​sparkylinux.org/​wiki/​doku.php/​partitioning#​virtual_machines|automatically partitioning]],​ the **efi** file has been installed on **/​dev/​sda1** partition. If you set other partition for **efi** file, change the partition number. If you used [[http://​sparkylinux.org/​wiki/​doku.php/​partitioning#​virtual_machines|automatically partitioning]],​ the **efi** file has been installed on **/​dev/​sda1** partition. If you set other partition for **efi** file, change the partition number.
  
-If you have launched Sparky manually, fix the startup as following:+If you have launched Sparky manually, fix the startup as follow: 
 + 
 +64 bit:
  
    sudo mount /dev/sda1 /mnt    sudo mount /dev/sda1 /mnt
    cd /mnt    cd /mnt
    sudo echo '​\EFI\sparky\grubx64.efi'​ > startup.nsh    sudo echo '​\EFI\sparky\grubx64.efi'​ > startup.nsh
 +
 +32 bit:
 +
 +   sudo mount /dev/sda1 /mnt
 +   cd /mnt
 +   sudo echo '​\EFI\sparky\grubia32.efi'​ > startup.nsh
  
 Then reboot: Then reboot:
  
    ​reboot    ​reboot
- 
  
virtualbox_efi_boot_failed.txt · Last modified: 2015/06/21 17:51 by pavroo