VMware ESXi and vSphere Cluster Management

How to Add a Floppy Drive to a Virtual Machine in Oracle VirtualBox

Learn how to add a virtual floppy drive in Oracle VirtualBox, attach a raw floppy image or host drive, verify it in the guest, and boot legacy media.

Oracle VM VirtualBox can present a floppy drive as virtual hardware inside a virtual machine (VM). This is useful when running legacy operating systems or software that expects floppy media for boot disks, driver disks, firmware utilities, installation files, or recovery tools.

The computer running VirtualBox is the host. The operating system running inside the VM is the guest. Adding a virtual floppy drive gives the guest a floppy-drive interface, but the guest must still support floppy hardware and the filesystem on the inserted media.

How VirtualBox Storage Works

A VM contains configurable virtual hardware. Its storage hardware is organized into controllers and attached devices. A controller provides an interface, while a drive or other device uses that interface to present storage to the guest.

A floppy controller provides the virtual floppy interface.
An optical controller is used for virtual CD/DVD drives and commonly attaches ISO images.
A hard-disk controller is used for virtual hard disks and their system files.

These device types are not interchangeable. Adding a floppy controller makes a floppy drive available to the VM; attaching media determines what that drive can read. The media can be a floppy disk image or, where supported, a physical floppy drive connected to the host.

When to Use a Virtual Floppy Drive

Floppy hardware is uncommon on modern computers, but it remains useful for older environments. Typical uses include:

Booting DOS-era diagnostic or firmware utilities.
Installing drivers that were distributed on floppy disks.
Providing legacy installation or recovery media.
Testing older operating systems that expect a floppy device.
Reading a preserved floppy disk image without needing original hardware.

The guest operating system must contain suitable floppy-drive support. Some modern guests may hide, ignore, or lack drivers for this legacy device. A successfully configured VirtualBox device does not guarantee that every guest will use it.

Prepare the VM Before Changing Hardware

Open VirtualBox Manager and confirm that you have selected the correct VM.
Shut down the guest operating system normally.
Confirm that the VM status is fully powered off, not running and not in a saved state.
Preserve a snapshot or backup if the VM contains important legacy software or configuration.

VirtualBox commonly restricts hardware configuration changes while a VM is running. A saved state can also prevent some storage changes. If necessary, discard the saved state only after confirming that doing so is safe; discarding it loses the suspended session and returns the VM to its last powered-off disk state.

Add a Floppy Controller in VirtualBox Manager

Select the target VM in VirtualBox Manager.
Open Settings for that VM.
Choose Storage.
In the storage tree, use the storage-device controls to add a floppy controller or floppy device. Depending on the VirtualBox release, the control may be represented by a controller button, a drive icon, or an add-device menu.
If VirtualBox asks for a controller type, choose the floppy option rather than an optical or hard-disk controller.
Confirm that the floppy controller and its virtual floppy drive appear in the storage tree.
Save the configuration with OK or the equivalent confirmation button.

The exact labels, icons, and positions of these controls vary between VirtualBox releases and host operating systems. The important result is a floppy controller with a floppy drive visible in the Storage tree.

Attach Floppy Media

Use a floppy disk image

With the VM powered off, open its Settings and return to Storage.
Select the virtual floppy drive beneath the floppy controller.
Use the media selector or attachment control.
Choose the option to select a floppy image file, then browse to the image.
Confirm the selection and save the VM settings.

A floppy disk image is a file containing a sector-level representation of a floppy disk. It is normally a raw image, meaning that it directly represents disk sectors rather than using a VirtualBox virtual-hard-disk container or an optical-disc format.

Common filename extensions include .img, .ima, and sometimes .flp. An extension alone does not prove compatibility. The file must contain a valid floppy layout, such as the expected sector count and geometry, and the guest must understand its filesystem or boot format.

Use a physical host floppy drive

If the host has a physical floppy drive and the platform and VirtualBox release support exposing it, the virtual floppy drive may be connected to that host device instead of an image file.

Confirm that the host operating system detects the physical floppy drive.
In the virtual floppy drive's media selector, check whether the host drive is available.
Select the supported physical device and save the VM configuration.
Allow the guest to access the media through VirtualBox.

Do not access the same physical floppy simultaneously from host software and the guest. Host applications can lock the device or cause inconsistent reads and writes. Modern computers often have no floppy hardware, so a raw image file is usually the more practical choice.

Connection type	What is attached	Typical use	Requirements and limitations
Raw floppy image file	A file containing floppy sectors	Boot disks, driver disks, archived legacy media, and repeatable testing	Requires a compatible raw layout and a guest that supports the image's filesystem or boot format
Physical floppy drive on the host	A real floppy device connected to the host	Reading or writing original disks	Requires host detection, platform support, suitable permissions, and exclusive access; availability varies

Eject, Replace, or Detach Media

The floppy controller can remain configured while its media changes. Removing media does not require removing the virtual controller.

Power off the VM when the guest or VirtualBox release requires offline media changes.
Open the VM's Storage settings or use its removable-media controls.
Select the virtual floppy drive and choose the eject, remove, or detach-media action.
To replace the disk, select another compatible image and attach it to the same drive.
Start or refresh the guest. Some guests need the drive to be remounted or rescanned.

Ejecting media removes the current image or host-device connection. It does not delete the image file and does not remove the floppy controller.

Verify the Drive in the Guest

Start the VM after saving the hardware configuration.
Use the guest's file manager, device manager, or hardware listing to check for a floppy drive.
Try to open the drive or list its files using the guest's command line.
If the guest supports mounting, mount the floppy using its normal guest-specific procedure.

For a DOS-style guest, the floppy drive is commonly assigned the letter A:. A command such as DIR A: may list its files when the guest recognizes the disk. Other operating systems use different device names and mounting tools.

An inserted image is not automatically usable merely because VirtualBox accepts it. The image may need to contain a valid filesystem, be formatted by the guest, or contain a bootable disk structure. An empty or unformatted floppy can be detected correctly while still producing an “unformatted” or “invalid disk” message.

Boot from a Floppy Image

Adding a floppy drive does not automatically make the VM boot from it. Booting depends on both the VM firmware's boot order and the contents of the attached media.

Open the powered-off VM's Settings.
Choose System and open the boot-order settings.
Ensure that the floppy device is enabled and placed before the virtual hard disk when testing floppy boot media.
Attach a raw floppy image that is actually bootable.
Save the settings and start the VM.

If the floppy is checked after a bootable virtual hard disk, the hard disk may start first. Moving the hard disk lower in the order temporarily can help diagnose the problem. A non-bootable image will not start a utility or operating system even when the floppy device is first.

Example: boot a DOS-era utility disk

Power off the legacy VM.
Configure a floppy controller and attach a known-good bootable raw floppy image.
Place the floppy device before the virtual hard disk in the boot order.
Start the VM and verify that the utility environment loads from the floppy.

Practical Example: Install a Legacy Driver

Power off the legacy VM and create or confirm a backup or snapshot.
Add a floppy controller in Settings > Storage.
Attach a compatible raw image containing the driver files.
Start the guest and open its floppy drive.
Copy or run the driver files using the guest's normal installation procedure.

This example does not require the image to be bootable. It only needs a filesystem and driver files that the guest can read.

Limitations and Version Differences

Storage labels, button icons, and the placement of attachment controls differ between VirtualBox releases and host operating systems.
Physical floppy pass-through may be unavailable on a particular host, platform, or VirtualBox release.
Current computers commonly lack physical floppy hardware.
Guest operating systems differ in their floppy drivers, filesystem support, and ability to detect hardware changes.
VM chipset and firmware choices can affect legacy-device behavior.
A damaged image, unusual geometry, or unsupported filesystem can prevent successful access even when the virtual device is configured correctly.

Troubleshooting Common Problems

Symptom	Likely cause	Recommended check or fix
No floppy device visible in the guest	The controller was not added, the settings were not saved, or the guest lacks support	Confirm the controller and drive in the VirtualBox Storage tree, restart the guest, and check guest device detection and legacy drivers
Image cannot be selected or read	The file is not a compatible raw floppy image, is corrupted, or has unsupported geometry	Use a known-good image, verify its expected format and source, and test it with a guest that supports its layout
Guest reports an unformatted or invalid disk	The image is empty, uses an unsupported filesystem, or does not represent a valid floppy layout	Use a formatted compatible image or format the disk through the guest if its contents are not needed
VM does not boot from floppy	Floppy is disabled or lower in the boot order, or the image is not bootable	Enable and prioritize the floppy device, then verify that the image contains valid boot media
Physical host drive is unavailable	No compatible drive is detected, the platform does not expose it, or another process has exclusive access	Check host-level detection, close host applications using the drive, verify permissions, or use a floppy image instead

Storage hardware controls are unavailable

The VM may still be running or in a saved state. Shut down the guest completely and reopen the VM settings. If the VM is saved, discard the saved state only when it is safe to lose the suspended session.

The guest still does not detect the drive

First confirm that the floppy controller appears in VirtualBox's Storage tree and that the revised configuration was saved. Then restart the guest and inspect its device manager or hardware listing. Some older guests need a compatible driver or a full reboot before detecting the device.

The image is unreadable

Check that the file is a raw floppy image rather than an ISO optical image or a virtual hard-disk file. A valid extension is not enough: the image may be corrupted or use geometry and a filesystem unsupported by the guest. Test a known-good image to separate a media problem from a VM configuration problem.

Quick Checklist

The correct VM is selected.
The VM is fully powered off.
A backup or snapshot exists when the legacy configuration is important.
A floppy controller and virtual floppy drive appear under Storage.
A compatible raw image or supported host floppy device is attached.
The guest has floppy-drive support.
The image contains a valid filesystem if you need to read files.
The image is bootable and floppy is prioritized if you need to boot from it.

For related configuration, see the VirtualBox floppy-drive setup guide.