Installing a new operating system on a server without having to use a USB drive or DVD. That's exactly what Virtual Media makes possible. For servers in a remote data center, this feature often determines whether a new installation can be completed the same day or only after someone arrives with a USB drive.
The BMC mounts a remote ISO file as a virtual USB or CD drive, and the server boots from it just as it would from a physical medium. HTTP, HTTPS, NFS, or SMB can be used as the source. Two Use Cases dominate: bare-metal provisioning of new hardware and the repair of a damaged system via a rescue medium.
How Virtual Media Works Technically
The ISO file does not have to be stored locally on the server or in its immediate vicinity. Most systems support HTTP, HTTPS, NFS, or SMB as sources; access is available either through the BMC's browser console or via the command line (netrouting, 2025). This makes no difference to the server itself. From the server's perspective, a bootable storage device is detected on the virtual USB port.
The principle sounds simple, but it has one important prerequisite. The server must be able to access the virtual media early enough in the boot process to allow a regular operating system installation to take place at all. The DMTF Redfish standard now meets this requirement. The Redfish Host Interface allows for the control of virtual media as early as the pre-boot phase, before the actual operating system has started (DMTF, 2018).
Two use cases: new servers and damaged systems
| Use Case | Background | What Virtual Media replaces |
|---|---|---|
| Bare-Metal Provisioning | New hardware without an operating system in the rack | travelling to the site with installation media |
| OS Repair | Bootloader or system damaged | Insert the rescue medium on site |
| Firmware or diagnostic images | The manufacturer's tool must boot | A separate storage device per server |
Bare-metal provisioning involves completely new hardware on which no operating system has yet been installed (netrouting, 2025). A technician configures the server as soon as it is installed in the rack and connected to power and the network, without anyone having to physically insert an installation medium on-site.
The second scenario involves repairing a server whose operating system is corrupted, whose bootloader no longer starts, or that requires a rescue system for troubleshooting. Especially when a server at a remote location has failed, this approach often makes the difference between a repair that takes just minutes and a trip that takes several hours.
Which hardware supports Virtual Media
This feature is no longer limited to specific manufacturers. Compatible systems include Dell’s iDRAC generations 6 through 9, Supermicro systems, HPE’s iLO, and Raritan’s Dominion KX III (netrouting, 2025). Those operating a mixed server fleet with servers from multiple manufacturers can use Virtual Media as a unified tool instead of maintaining a separate installation routine for each manufacturer.
There is a second point to consider. Virtual Media does not replace a backup or an automated provisioning pipeline. It provides a way to deploy an installation medium without physical access. The actual configuration of the system is then still handled by the usual tools.
Bare-Metal Installation Without On-Site VisitUsing your own hardware, we'll demonstrate which servers support Virtual Media and how images can be deployed across multiple locations.
Virtual Media as Part of Fleet Management
For teams that manage multiple locations simultaneously, what matters most—besides the functionality itself—is having a clear overview of which server currently needs an installation, where the appropriate image is located, and who last accessed it. KVM Fleet consolidates virtual media access across multiple servers and vendors into a single interface, eliminating the need to initiate an installation through each BMC’s individual web interface. For a team that needs to set up multiple servers at different locations in a single morning, this is the difference between a smooth workflow and constantly switching between a dozen login screens.
How the underlying remote access via the BMC fits into the wider picture is described in the article on Out-of-Band Management. The architecture for many locations is covered in the article on KVM-over-IP at a fleet-wide scale.
Frequently Asked Questions
How fast is a Virtual Media remote installation?
That depends heavily on the size of the ISO file and the available bandwidth to the destination server. With a good network connection, a remote installation is virtually indistinguishable from a local installation using physical media. With a slow WAN connection, simply transferring the installation file can take up the majority of the time.
Is access to Virtual Media encrypted?
As sources for the ISO file, common systems support HTTPS in addition to unencrypted HTTP, as well as NFS and SMB (netrouting, 2025). For transmission over a public or shared network, it is recommended to use HTTPS or an additional secure connection, such as a VPN, to the management network where the BMC is located.
What requirements must the target server meet for Virtual Media?
The server requires a BMC that supports Virtual Media, as is the case with current generations of Dell iDRAC, Supermicro, HPE iLO, and comparable systems (netrouting, 2025). In addition, the BMC itself must be accessible over the network, either directly or via a properly configured management network. For very old server generations that lack this support, the only option is the traditional method using a physical storage device on-site.
The Next Step
At torck, KVM Fleet also consolidates virtual media access for the company’s own server fleet, developed by the team in Maxhütte-Haidhof, Vienna, and Rabat. Because the software runs in-house, the team has firsthand experience with bandwidth and compatibility issues. Details are provided by the Product Page for KVM Fleet.
German 
English 
French