Opened 3 years ago
Last modified 3 years ago
#20365 awaitsfeedback defect
Linux guest won't boot unless hard disk is set as the priority
Reported by: | Rusty_Almighty | Owned by: | |
---|---|---|---|
Component: | virtual disk | Version: | VirtualBox 6.1.22 |
Keywords: | Cc: | ||
Guest type: | Linux | Host type: | Linux |
Description
After installing the latest CentOS 7.8 The OS refuses to boot unless the boot order for the VM is specifically changed so that the VM boots from the disk first. If I set the boot order to something else (for example network for IPXE testing),the operating system instead shows an error "fatal: int18: BOOT FAILURE". Most of what I found online talks about installing the disk in GPT vs MBR, but that shouldn't have much bearing since I know I installed the VM as MBR. None the less, I still tried to change the VM to UEFI since that is what the online community instructs. However, no effect was detected besides the VM booting into the UEFI shell. However, if the boot order for the VM is changed, even though the other boot options are not being used and the option for disk is eventually reached, the boot option for the disk will eventually show the error.
Attachments (1)
Change History (3)
by , 3 years ago
Attachment: | VirtualBox_IPXE Test_13_05_2021_12_23_25.jpeg added |
---|
comment:1 by , 3 years ago
In addendum. If you put the boot order to boot off of the disk first, then the OS boots up as expected. I've also confirmed that this doesn't appear to be an issue in VirtualBox 6.1.20. I've also noted that if I remove the IPXE server from the equation by moving the bridged NIC onto a NIC which isn't connected to anything, the VM also boots as expected. Could this be the network boot portion not cleaning up after it's self I wonder?
comment:2 by , 3 years ago
Status: | new → awaitsfeedback |
---|
We cannot even begin to guess what might be wrong without log files from the VM, ideally for both working and non-working scenarios.
Error as shown from virtual box guest OS console