That is not related to this bug report Djordje.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665329
Title:
Installer fails to create startup.nsh for EFI system on VirtualBox
To manage
I too have issue with this. HP elitebook 745 g3 installation with
customer partitioning and luks (kubuntu 16.04.2). after installation i
get dropped to initramfs and error about not able to reach root volume.
it didn't ask for luks password.
--
You received this bug notification because you are
I too have issue with this. HP elitebook 745 g3 installation with
customer partitioning and luks (kubuntu 16.04.2). after installation i
get dropped to initramfs and error about not able to reach root volume.
it didn't ask for luks password.
--
You received this bug notification because you are
** Changed in: grub2 (Ubuntu)
Importance: Undecided => High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665329
Title:
Installer fails to create startup.nsh for EFI system on VirtualBox
To
@Phillip Susi
Is this something should be filed as a bug on VirtualBox? If so, I have
nowhere near sufficient knowledge to file a bug report that makes any
sense. Would you be willing to file such a bug report?
I found these two bug reports, but I don't know if they are relevant (as
I say, I'm
AFAIK, startup.nsh is entirely up to the user and optional -- not
something that OS installers are normally supposed to mess with. The OS
is supposed to make calls to the EFI firmware to register its boot
loader in the EFI variables and that tells the firmware what to boot,
but virtual machines
For that matter, even having an EFI shell installed that would have the
ability to interpret startup.nsh is optional and not something that any
real hardware I have seen comes with.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Phillip Susi
Forgive me if I'm wrong on this — unfortunately, I'm not technically
expert. As far as I could tell, the ESP should have startup.nsh.
If it's a bug with VirtualBox, I should post a bug report there, but I'd
need to know details about how it's wrong. If you could explain, please,
or
So this is a proposed workaround for virtual machines that don't
correctly implement EFI variables?
** Package changed: ubiquity (Ubuntu) => grub2 (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Confirming this occurs on Ubuntu 16.04 and 16.10.
** Changed in: ubiquity (Ubuntu)
Status: New => Confirmed
** Tags added: yakkety
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665329
** Tags added: xenial
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665329
Title:
Installer fails to create startup.nsh for EFI system on VirtualBox
To manage notifications about this bug go to:
** Package changed: ubuntu => ubiquity (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1665329
Title:
Installer fails to create startup.nsh for EFI system on VirtualBox
To manage
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
13 matches
Mail list logo
