Add a Floppy Drive to a Virtual Machine in Oracle VirtualBox

Learn how to add a virtual floppy controller, attach a physical floppy drive or .img disk image, verify guest detection, and troubleshoot boot problems in Oracle VirtualBox.

Oracle VirtualBox can emulate legacy floppy hardware for a virtual machine (VM). This lets a guest operating system use a virtual floppy drive much like an older physical computer would. You can attach a raw floppy disk image or, where supported, a physical floppy drive connected to the host system.

This guide covers adding the controller, attaching media, starting the guest, verifying the drive, replacing media, and safely removing the configuration.

What a Virtual Floppy Drive Is Used For

A virtual floppy drive is an emulated floppy disk drive attached to a VM. The guest operating system sees a floppy controller and drive even though the device is implemented by VirtualBox rather than by physical hardware.

A guest operating system is the operating system running inside the VM. The physical computer and its operating system are the host system. VirtualBox provides the connection between the guest and the emulated floppy hardware.

Booting an older operating system installer or diagnostic disk.
Loading legacy drivers that expect floppy media.
Running older software distributed on floppy disks.
Reading a preserved floppy image for historical or compatibility testing.
Replacing removable media without changing the rest of the VM hardware.

Modern operating systems often do not need floppy support. Add it when the guest or the software running in it specifically requires this legacy device.

Floppy Media Sources

VirtualBox can obtain floppy media from either a physical host device or a floppy disk image file, depending on host and VirtualBox support.

Physical host drive: A real floppy drive connected to the host computer. The guest can access the disk inserted in that drive when VirtualBox and the host operating system permit device access.
Floppy disk image: A file containing the sector-level contents of a floppy disk. These files are commonly raw images with an .img extension. VirtualBox inserts the image into the virtual floppy drive as if it were a disk.

A raw disk image stores disk contents directly rather than using a virtual hard-disk container format. The file must be a valid floppy image; changing its filename extension does not convert an unrelated file into floppy media.

Media source: Host physical floppy drive

What it uses: A supported real floppy drive attached to the host.

Typical use case: Reading an existing physical floppy disk.

Considerations: The host must recognize the drive, VirtualBox must be able to access it, and the device must not be blocked by permissions or another application.

Media source: Raw floppy image file

What it uses: A sector-level floppy image, commonly a readable .img file.

Typical use case: Booting legacy media, loading drivers, or testing preserved floppy contents.

Considerations: The image should be complete, supported, readable by the host account, and bootable if you intend to start the VM from it.

VirtualBox Storage Components

VirtualBox storage settings describe several different layers. Keeping them distinct helps prevent confusion between a floppy device and an optical CD/DVD device.

Floppy controller: The virtual storage controller that provides a floppy-drive interface to the guest.

Virtual floppy drive: The emulated removable drive connected to the floppy controller.

Attached floppy media: The physical host device or floppy image currently inserted in the virtual drive.

Optical CD/DVD device: A separate virtual device intended for CD/DVD media, usually including ISO images. Its add-device control is not the same as the floppy-controller action.

In the storage tree, the controller normally contains the drive, and the drive shows the attached media. A floppy image should appear under the floppy controller, not under an optical controller.

Before Changing VM Hardware

Fully power off the target VM. Do not change this storage hardware while the guest is running.
If the VM is in a saved state, restore or discard the saved state as appropriate, then shut the VM down before editing hardware.
Prepare a valid floppy image, or confirm that a supported physical host floppy drive is available.
Check that your VirtualBox release and guest operating system support the legacy device you need. Labels and available controls can vary by release.
Back up important VM configuration or media before changing boot devices or removing storage components.

Add a Floppy Controller in VirtualBox Manager

Open Oracle VirtualBox Manager.
Select the VM that needs floppy support.
Confirm that the VM is powered off, then open Settings.
Select Storage in the settings sidebar.
Inspect the storage-controller controls or add-device menu. Choose the option for a floppy controller.
After the controller appears in the storage tree, select it and add a floppy drive if VirtualBox has not created one automatically.
Select the floppy drive beneath the new controller so that its media options are displayed.
Attach a physical host device or select a floppy image from the host file system.
Confirm the configuration by selecting OK or the equivalent save control for your VirtualBox release.

Attach Floppy Media

Use a Physical Host Floppy Drive

In the VM's Settings > Storage area, select the floppy drive below the floppy controller.
Open the media selection control.
Choose the available physical host floppy device.
Insert the floppy disk into the host drive and save the VM settings.

This option depends on the host computer exposing a compatible physical drive to VirtualBox. A USB floppy device may not be presented to VirtualBox as a directly usable floppy drive on every host configuration.

Use a Floppy Disk Image

Select the virtual floppy drive under the floppy controller.
Open the media selection control and choose the option to select an existing disk image.
Browse to the raw floppy image on the host system. Images commonly use the .img extension.
Select the image and save the VM configuration.

The image is now inserted into the virtual floppy drive. It represents the floppy's contents; it is not a second virtual hard disk.

Start the Guest and Verify Detection

Start the VM after the controller and media have been configured.
Watch the guest's startup messages for floppy-drive detection if the operating system displays hardware information.
Inside the guest, look for the drive using the operating system's normal device list or file manager.
Try reading a known file from the floppy media.

The guest may expose the device under a legacy drive letter, such as a floppy-style drive letter, or under an operating-system-specific device name. The exact name depends on the guest operating system and its hardware support.

For a bootable floppy image, review the VM's boot order if the guest starts from another device first. The image must also contain boot code compatible with the guest firmware and operating system.

Practical Examples

Boot a Legacy Operating System Installer

Power off the VM, add a floppy controller, attach a bootable raw floppy image, and start the VM. If the guest does not boot from it, place the floppy device ahead of other devices in the VM's boot order and verify that the image is actually bootable.

Load Drivers for Older Software

Attach a floppy image containing the required driver files. Start the guest and use its driver installation process to read the virtual floppy drive. This is useful when the installer only searches legacy floppy devices.

Read Existing Physical Media

Insert the disk into a compatible host floppy drive, select that device as the floppy media source, and start the VM. The guest can then access the inserted disk if host permissions and device support are correct.

Replace Removable Media

After the guest finishes reading one image, eject or detach it in the storage settings, then attach another image. Keep the floppy controller and virtual drive in place unless the guest no longer needs them.

Change or Remove Floppy Media Safely

Eject or detach the floppy image from the virtual drive before deleting or moving the image file on the host.
If the guest is running, use its normal eject or unmount procedure before changing removable media when possible.
Remove the floppy controller only after confirming that the guest and its software no longer require the device.
Be careful when changing boot media or device order. Legacy guests may stop starting if their expected boot device is moved or removed.

Troubleshooting

No Floppy-Controller Option Is Visible

Fully power off the VM; a running or saved-state VM may restrict hardware changes.
Return to Settings > Storage and inspect the add-controller or add-device menus.
Look specifically for floppy-controller and floppy-drive entries rather than optical CD/DVD controls.
Remember that the control's label and placement can differ between VirtualBox releases.

The Floppy Image Cannot Be Selected or Does Not Work

Use a known-good raw floppy image, commonly an .img file.
Verify that the image is complete and not damaged.
Confirm that the host user account can read the file.
Try another known-good image to separate an image problem from a VM configuration problem.

The Guest Does Not Detect the Floppy Drive

Confirm that the floppy controller and drive still appear in the VM's storage tree.
Confirm that media is attached.
Save the settings and restart the guest if it was already running.
Check the guest operating system's documentation because some newer systems provide limited or no legacy floppy support.

The VM Does Not Boot from the Floppy Image

Confirm that the image is intended to be bootable.
Review the VM's boot-order settings and place the floppy device appropriately.
Check whether the guest firmware and operating system support the image's boot format.
Test with known-compatible legacy boot media.

A Host Floppy Drive Is Unavailable

Verify that the host actually has a supported physical floppy drive.
Check whether the host operating system recognizes the device and whether another program is using it.
Review host permissions required to access the device.
Use a raw floppy image instead when physical-device access is unavailable or unreliable.

Key Points to Remember

Power off the VM before editing its storage hardware.
Add a floppy controller before attaching a floppy drive or its media.
A physical host drive and a raw .img file are different media sources.
Floppy controls are separate from optical CD/DVD controls.
Verify both the VirtualBox storage tree and the guest operating system after saving.
Detach media before deleting its host image, and remove the controller only when it is no longer needed.

For related storage tasks, see disk image files, adding a virtual CD/DVD drive, and virtual hard-disk controllers.