Hard disk boot order
When you have several hard drives set in your VM and the actual boot disk is SATA or on any other controller than IDE, while you have an IDE hard drive attached, it will fail to boot. There is no way to set the controller priority in the VM settings for booting the VM. The first detected hard drive is tried, but never another if that one fails.
Here is one of the examples, though the issue describes something else too: http://forums.virtualbox.org/viewtopic.php?f=6&t=31956 The first reply (second post) is the vital one.
It is reported for version 3.2.4, but I think this problem exists in all versions where more controllers are available. It doesn’t matter which host or Guest you have. It also appears that the OS you want to boot using the boot menu (F12) may fail.
I have attached two log files, it’s the same VM, one where I let it boot without intervention and it just stays on a black screen with a blinking _ and 100% CPU on one core. It tries to boot from a data VDI, it doesn’t contain an OS. The second log is where I selected the proper device (AHCI SATA drive) and got the error «A Boot Error Occurred».
Вложения (2)
VBox_failed_boot_non-boot_IDE.log ( 66.9 KB ) — added by Sasquatch 13 лет ago. Let it continue without intervention. VBox_failed_boot_device_chosen.log ( 71.8 KB ) — added by Sasquatch 13 лет ago. Selected boot device, failed to boot error appears.
Download all attachments as: .zip
Booting from local disk virtualbox что делать
Oracle® VM VirtualBox
User Manual for Release 6.0
- Preface
- First Steps
- Why is Virtualization Useful?
- Some Terminology
- Features Overview
- Supported Host Operating Systems
- Host CPU Requirements
- Starting a New VM for the First Time
- Capturing and Releasing Keyboard and Mouse
- Typing Special Characters
- Changing Removable Media
- Resizing the Machine’s Window
- Saving the State of the Machine
- Taking, Restoring, and Deleting Snapshots
- Snapshot Contents
- About the OVF Format
- Importing an Appliance in OVF Format
- Exporting an Appliance in OVF Format
- Exporting an Appliance to Oracle Cloud Infrastructure
- Importing an Instance from Oracle Cloud Infrastructure
- The Cloud Profile Manager
- Using the Soft Keyboard
- Creating a Custom Keyboard Layout
- Installing on Windows Hosts
- Prerequisites
- Performing the Installation
- Uninstallation
- Unattended Installation
- Public Properties
- Performing the Installation
- Uninstallation
- Unattended Installation
- Prerequisites
- The Oracle VM VirtualBox Kernel Modules
- Kernel Modules and UEFI Secure Boot
- Installing Oracle VM VirtualBox from a Debian or Ubuntu Package
- Using the Alternative Generic Installer (VirtualBox.run)
- Performing a Manual Installation
- Updating and Uninstalling Oracle VM VirtualBox
- Automatic Installation of Debian Packages
- Automatic Installation of RPM Packages
- Automatic Installation Options
- Performing the Installation
- The vboxuser Group
- Starting Oracle VM VirtualBox on Oracle Solaris
- Uninstallation
- Unattended Installation
- Configuring a Zone for Running Oracle VM VirtualBox
- Supported Guest Operating Systems
- Mac OS X Guests
- 64-bit Guests
- An Example of Unattended Guest Installation
- Basic Tab
- Advanced Tab
- Description Tab
- Disk Encryption Tab
- Motherboard Tab
- Processor Tab
- Acceleration Tab
- Screen Tab
- Remote Display Tab
- Recording Tab
- USB Settings
- Implementation Notes for Windows and Linux Hosts
- Video Modes in EFI
- Specifying Boot Arguments
- Introduction to Guest Additions
- Installing and Maintaining Guest Additions
- Guest Additions for Windows
- Installing the Windows Guest Additions
- Updating the Windows Guest Additions
- Unattended Installation
- Manual File Extraction
- Installing the Linux Guest Additions
- Graphics and Mouse Integration
- Updating the Linux Guest Additions
- Uninstalling the Linux Guest Additions
- Installing the Oracle Solaris Guest Additions
- Uninstalling the Oracle Solaris Guest Additions
- Updating the Oracle Solaris Guest Additions
- Manual Mounting
- Automatic Mounting
- Supported Formats
- Known Limitations
- Hardware 3D Acceleration (OpenGL and Direct3D 8/9)
- Hardware 2D Video Acceleration for Windows Guests
- Using Guest Properties to Wait on VM Events
- Using the Guest Control File Manager
- Memory Ballooning
- Page Fusion
- Hard Disk Controllers
- Disk Image Files (VDI, VMDK, VHD, HDD)
- The Virtual Media Manager
- Special Image Write Modes
- Differencing Images
- Cloning Disk Images
- Host Input/Output Caching
- Limiting Bandwidth for Disk Images
- CD/DVD Support
- iSCSI Servers
- vboximg-mount: A Utility for FUSE Mounting a Virtual Disk Image
- Viewing Detailed Information About a Virtual Disk Image
- Mounting a Virtual Disk Image
- Virtual Networking Hardware
- Introduction to Networking Modes
- Network Address Translation (NAT)
- Configuring Port Forwarding with NAT
- PXE Booting with NAT
- NAT Limitations
- Introduction
- Commands Overview
- General Options
- VBoxManage list
- VBoxManage showvminfo
- VBoxManage registervm/unregistervm
- VBoxManage createvm
- VBoxManage modifyvm
- General Settings
- Networking Settings
- NAT Networking Settings
- Import from OVF
- Import from Oracle Cloud Infrastructure
- Export to OVF
- Export to Oracle Cloud Infrastructure
- Synopsis
- Description
- unattended detect
- unattended install
- Synopsis
- Description
- General Command Operand
- Take a Snapshot of a Virtual Machine
- Delete a Snapshot
- Restore a Snapshot
- Restore the Current Snapshot
- Change the Name or Description of an Existing Snapshot
- List the Snapshots
- Show Information About a Snapshot’s Settings
- Synopsis
- Description
- Command Operand and Options
- Examples
- See Also
- Synopsis
- Description
- extpack install
- extpack uninstall
- extpack cleanup
- Synopsis
- Description
- Common options
- dhcpserver add
- dhcpserver modify
- dhcpserver remove
- dhcpserver restart
- dhcpserver findlease
- Common DHCP Options:
- Synopsis
- Description
- Common options
- debugvm dumpvmcore
- debugvm info
- debugvm injectnmi
- debugvm log
- debugvm logdest
- debugvm logflags
- debugvm osdetect
- debugvm osinfo
- debugvm osdmesg
- debugvm getregisters
- debugvm setregisters
- debugvm show
- debugvm stack
- debugvm statistics
- Synopsis
- Description
- Common options
- cloudprofile add
- cloudprofile show
- cloudprofile update
- cloudprofile delete
- Synopsis
- Description
- Common options
- cloud list instances
- cloud list images
- Synopsis
- Description
- Common options
- cloud instance create
- cloud instance info
- cloud instance termination
- cloud instance start
- cloud instance pause
- Synopsis
- Description
- Common options
- cloud image create
- cloud image info
- cloud image delete
- cloud image import
- cloud image export
3.2. Unattended Guest Installation
Oracle VM VirtualBox can install a guest OS automatically. You only need to provide the installation medium and a few other parameters, such as the name of the default user.
Performing an unattended guest installation involves the following steps:
- Create a new VM. Use one of the following methods:
- The VirtualBox Manager, see Section 1.7, “Creating Your First Virtual Machine”.
- The VBoxManage createvm command, see Section 7.7, “VBoxManage createvm”.
For the new VM, choose the guest OS type and accept the default settings for that OS. The following sections in this chapter describe how to change the settings for a VM.
Section 3.2.1, “An Example of Unattended Guest Installation” describes how to perform an unattended guest installation for an Oracle Linux guest.
3.2.1. An Example of Unattended Guest Installation
The following example shows how to perform an unattended guest installation for an Oracle Linux VM. The example uses various VBoxManage commands to prepare the guest VM. The VBoxManage unattended install command is then used to install and configure the guest OS.
- Create the virtual machine.
# VM="ol7-autoinstall" # VBoxManage list ostypes # VBoxManage createvm --name $VM --ostype "Oracle_64" --register
Note the following:
- The $VM variable represents the name of the VM.
- The VBoxManage list ostypes command lists the guest OSes supported by Oracle VM VirtualBox, including the name used for each OS in the VBoxManage commands.
- A 64-bit Oracle Linux 7 VM is created and registered with Oracle VM VirtualBox.
- The VM has a unique UUID.
- An XML settings file is generated.
# VBoxManage createhd --filename /VirtualBox/$VM/$VM.vdi --size 32768 # VBoxManage storagectl $VM --name "SATA Controller" --add sata --controller IntelAHCI # VBoxManage storageattach $VM --storagectl "SATA Controller" --port 0 --device 0 \ --type hdd --medium /VirtualBox/$VM/$VM.vdi # VBoxManage storagectl $VM --name "IDE Controller" --add ide # VBoxManage storageattach $VM --storagectl "IDE Controller" --port 0 --device 0 \ --type dvddrive --medium /u01/Software/OL/OracleLinux-R7-U6-Server-x86_64-dvd.iso
The previous commands do the following:
- Create a 32768 MB virtual hard disk.
- Create a SATA storage controller and attach the virtual hard disk.
- Create an IDE storage controller for a virtual DVD drive and attach an Oracle Linux installation ISO.
# VBoxManage modifyvm $VM --ioapic on # VBoxManage modifyvm $VM --boot1 dvd --boot2 disk --boot3 none --boot4 none # VBoxManage modifyvm $VM --memory 8192 --vram 128
The previous commands do the following:
- Enable I/O APIC for the motherboard of the VM.
- Configure the boot device order for the VM.
- Allocate 8192 MB of RAM and 128 MB of video RAM to the VM.
# VBoxManage unattended install $VM \ --iso=/u01/Software/OL/OracleLinux-R7-U6-Server-x86_64-dvd.iso \ --user=
login--full-user-name=name--passwordpassword\ --install-additions --time-zone=CETThe previous command does the following:
- Specifies an Oracle Linux ISO as the installation ISO.
- Specifies a login name, full name, and login password for a default user on the guest OS. Note that the specified password is also used for the root user account on the guest.
- Installs the Guest Additions on the VM.
- Sets the time zone for the guest OS to Central European Time (CET).
# VBoxManage startvm $VM --type headless
# yum update
Copyright © 2004, 2020 Oracle and/or its affiliates. All rights reserved. Legal Notices
FIX: VirtualBox FATAL: INT18: BOOT FAILURE. (Solved)

If you receive the VirtualBox error «FATAL: INT18: BOOT FAILURE» when starting a guest machine with Windows 10/11 OS, continue reading below to fix the problem.
Problem in details. After converting the physical disk of a Windows 10//11 UEFI computer to a Virtual Hard disk (VHD or VHDX) and attaching the VHD/VHDX file to a new VirtualBox machine, the VM couldn’t start with fatal error: INT18: BOOT FAILURE or the guest Windows 10 OS couldn’t start with error code: 0x0000225.

This tutorial contains detailed instructions to troubleshoot the «INT18: BOOT FAILURE” error in VirtualBox.
How to FIX: INT18 BOOT FAILURE & Windows 10 Error Code 0x0000225 in VirtualBox.
Method 1. Enable I/O APIC & UEFI in VirtualBox.
The fatal error «INT18 BOOT FAILURE» in VirtualBox, commonly appears when you attaching a VHD/VHDX/VMDK file which contains an UEFI operating system. To fix this problem just proceed and enable UEFI on the VirtualBox machine’s settings. To do that:
1. Press the X button to close the VM machine window and Power Off the machine.

2. Open the VM Settings and go to System > Motherboard.
3. Here ensure that the Hard Disk is checked and is the first boot device, and at Extended features check the following two (2) options and click OK:
Enable I/O APIC
Enable EFI (special OSes only)
4. Try to start the Virtual Machine now. Hopefully it will start without error now.
Method 2. Disable Hyper-V on Host machine.
1. Navigate to Control Panel > Programs and Features > Turn Windows features on or off

2. Uncheck the following features and click OK to apply the change:
- Containers *
- Hyper-V *
- Virtual Machine Platform
- Windows Hypervisor Platform
- Windows Sandbox
* Note: The ‘Containers’ and the ‘Hyper-V’ features exists only in Windows 10 PRO.

3. Restart the computer after uninstall.
4. Open Command Prompt as Administrator.
5. Type the following command and press Enter:- bcdedit /set hypervisorlaunchtype off

6. Reboot your PC again.
7. After reboot, start the VirtualBox VM machine and see if the problem is fixed.Method 3. Fix Boot Problems.
The final method to solve VirtualBox error «FATAL: INT18: BOOT FAILURE» is to fix the boot problems on the Guest machine, by starting the guest machine from a bootable Windows 10 ISO file.*
* Note: If you don’t own a Windows 10 ISO file, you can download one directly from Microsoft, by using the Media Creation Tool.
1. Open the Settings of the VirtualBox machine and go to Storage.
2. Click the 1st plus (+) button next to Controller to add optical drive.

3. Click Add and find and open the Windows.iso file.

4. Then select the Windows.iso file and click Choose.
![image_thumb[5]](https://www.wintips.org/wp-content/uploads/2022/06/image_thumb5_thumb.png)
5. After attaching the Windows.iso file in Storage devices…
![image_thumb[6]](https://www.wintips.org/wp-content/uploads/2022/06/image_thumb6_thumb.png)
6. … go to System and drag Optical to the top in order to boot the VM from the attached Windows.iso.
Also, make sure that the «Enable EFI» option is unchecked, otherwise you will not be able to boot from the ISO file. When done, click OK.

7. Start the Virtual Machine and click Next > Repair Your computer.
8. Then select Troubleshoot > Startup Repair.

9. Allow the Startup Repair to run and depending on the result do the following actions:
a. If the Startup Repair can fix the problem, shutdown the virtual machine, set the hard disk as first boot device and try to start again the virtual machine.
b. If the Startup Repair cannot fix the problem, continue to next step.
10. Click Advanced Options and go to Troubleshoot > Command Prompt.

11. In Command prompt give the following commands in order (press enter after each command)
13. Now notice the size of the System partition (e.g. 100MB in this example).
12. Then type the following command and find out the volume number of the System partition by using its size as a reference. *
* e.g. As you can see in the screenshot below, in this example, the System partition (100MB) is the volume 2.

13. Now give the following commands to select the system partition (using its volume number), and to assign the drive letter Z: to it. Then exit DISKPART:
* Note: Change the Volume number «2» according your case.

14. Finally, in command prompt give this command to repair the boot files:
![image_thumb[9]](https://www.wintips.org/wp-content/uploads/2022/06/image_thumb9_thumb.png)
15. Close all windows, shutdown the virtual machine, set the hard disk as first boot device and start the virtual machine.
That’s it! Which method worked for you?
Let me know if this guide has helped you by leaving your comment about your experience. Please like and share this guide to help others.virtualbox.org
FreeDos hangs on «Booting from local disk» after install
Discussions related to using VirtualBox on Windows hosts.
3 posts • Page 1 of 1
pepesz Posts: 2 Joined: 19. Nov 2020, 22:39FreeDos hangs on «Booting from local disk» after install
Post by pepesz » 19. Nov 2020, 23:02
Host OS: Windows 8.1 Enterprise 6.3.9600
Guest OS: Freedos 1.2 (FD12CD.iso)Problem: FreeDOS installed from iso. When trying to boot for the first time it freezes on «Booting from local disk. «
Processor usage is 100% but after 1h nothing changes.
Any suggestions?Hyper-V in windows is off.
Attached is log file
Attachments Freedos-2020-11-19-21-28-08.log (80.32 KiB) Downloaded 21 times
pepesz Posts: 2 Joined: 19. Nov 2020, 22:39Re: FreeDos hangs on «Booting from local disk» after install
Post by pepesz » 20. Nov 2020, 10:32
Issue solved,
Apparently RAM was the problem. It needed at least 512MB to properly install FreeDOS,scottgus1 Site Moderator Posts: 20009 Joined: 30. Dec 2009, 20:14 Primary OS: MS Windows 10 VBox Version: PUEL Guest OSses: Windows, Linux
Re: FreeDos hangs on «Booting from local disk» after install
Post by scottgus1 » 20. Nov 2020, 20:54
- Guest Additions for Windows