When someone says that a virtual machine can “boot from one ISO file,” they usually mean that the VM can treat that ISO file like a virtual DVD or installation disc. The word “boot” means the virtual machine’s firmware starts from that media and loads the installer or operating environment. It does not mean the ISO magically becomes the installed system by itself, and it does not mean that activation, licensing, drivers, or disk setup can be ignored.
What an ISO file is
An ISO image is a disk-image file that contains the data and file system of optical media such as a CD, DVD, or installation disc. The Library of Congress describes ISO disk images as archive files containing the content from, or destined for, an optical disk, commonly using the .iso extension. Not every ISO is bootable: it may lack bootloader files, target a different CPU architecture, or expect a firmware mode such as UEFI when the VM is configured for legacy BIOS. Modern operating-system installers are often distributed as ISO files because virtualization software can mount them without a physical disc drive.
Why a virtual machine can use an ISO directly
A virtual machine already has virtual hardware: virtual firmware, virtual memory, virtual storage controllers, and a virtual hard disk. When you attach an ISO, the hypervisor presents it to the guest as a virtual optical drive. In Oracle VM VirtualBox, the create-VM wizard includes an “ISO Image” field that can attach the installer media to the new machine. The VM then starts from that virtual drive, just as a physical computer might start from a DVD or USB installer.
The ISO is often the installer, not the final installed disk. Some bootable ISOs start a live or rescue environment that can run temporarily without installing anything; others launch an installer. During a normal installation, the guest operating system writes files to the VM’s virtual hard disk, such as a VDI, VMDK, VHD/VHDX, raw image, or qcow2 image depending on the platform. QEMU’s documentation, for example, distinguishes disk-image formats such as raw and qcow2 from the removable media used to boot or install a system.
How this differs from installing with a USB drive
A USB installer has to be prepared so real firmware can find boot files on a physical USB device. On modern PCs, the boot choice may differ between UEFI mode and legacy BIOS mode. Microsoft’s Windows deployment documentation explains that the same USB device can appear as separate UEFI and BIOS boot choices, and the installed system normally continues in the mode used during setup. That is why a physical USB installer involves firmware menus, partition style, boot files, and sometimes Secure Boot settings.
In a VM, the hypervisor hides much of that physical-device work. You choose the virtual firmware mode, attach the ISO, create a virtual hard disk, and let the VM boot from the virtual optical drive. The concept is the same—firmware loads bootable media—but the hardware is simulated.
Where GHO files fit
A .gho file is generally associated with Ghost-style disk or partition imaging. It is not the same thing as a normal operating-system ISO installer. A GHO image may contain a captured system or partition, and restoring it typically requires compatible imaging software and an appropriate boot environment. It also requires the right license and permission for the operating system and applications inside the image. Treating a random GHO file as a clean, universal installer is a common source of confusion.
A modern, legitimate VM installation path
- Download the operating system installer ISO from the software publisher or another authorized source.
- Create a new VM and choose the correct OS type and version.
- Assign memory and CPU conservatively so the host computer still has enough resources.
- Create a new virtual hard disk rather than writing directly to a host drive.
- Attach a bootable ISO for the correct CPU architecture and firmware mode as virtual optical media, then boot the VM.
- Install the guest OS to the virtual hard disk, then remove or detach the ISO after installation.
Common mistakes
- Calling every image file an “ISO.” ISO, GHO, qcow2, VDI, VMDK, and VHD are different formats used for different jobs.
- Thinking the ISO is the installed system. Usually it is the installer media; the installed system lives on the virtual hard disk.
- Assuming every ISO can boot. Missing boot files, the wrong CPU architecture, or a UEFI/legacy BIOS mismatch can stop the VM before the installer appears.
- Mixing UEFI and legacy BIOS without noticing. The wrong boot mode can make an installer or restored image fail to boot.
- Using an image from an unknown source. That can create malware, licensing, and data-integrity problems.
- Restoring an old captured image onto different virtual hardware without checking drivers, boot mode, and partition style.
So the short answer is: a VM can start from one ISO because virtualization software can present that file as bootable virtual media. A USB installer performs the same basic boot-media role on physical hardware, but it must satisfy the firmware and device layout of a real computer. A GHO image is usually a restore image, not a normal installer, and should be handled with compatible tools and legitimate software rights.
References: Library of Congress description of ISO disk images, Oracle VM VirtualBox first-steps manual, QEMU disk image documentation, and Microsoft guidance on UEFI and legacy BIOS boot modes.