On Tue, Jun 02, 2020 at 07:31:33PM +1000, Stephen Morris wrote: > I understand this is the entry that is being booted from, but I don't > understand why it is that entry rather than boot0003, which looks to be the > vm disk partition, when I am running fedora within a vm. I don't understand > how this relates to the segmented disk image that virtualbox is using for > fedora, as it is not a physical partition as far as I am aware. Virtualbox > may make it look like a partition but I'm not up on the internal workings of > virtualbox. >From the earlier message: On Mon, Jun 01, 2020 at 05:38:00PM -0700, Samuel Sieb wrote: > On 6/1/20 4:10 PM, Stephen Morris wrote: > > Timeout: 0 seconds > > BootOrder: 0005,0000,0001,0003,0004 > > This is the order that the entries will be tried in. That's why it uses the Boot0005 before Boot0003 boot entry. The order is already defined. The UEFI VBOX HARDDISK entries are most likely the VBox UEFI implementation's entries to boot via the Compatibility Support Module (CSM), which is the legacy BIOS boot method. -- Jonathan Billings <billings@xxxxxxxxxx> _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
