diff --git a/doc/source/admin/drivers/ilo.rst b/doc/source/admin/drivers/ilo.rst
index 13d1ffbd33..13b93e4cfa 100644
--- a/doc/source/admin/drivers/ilo.rst
+++ b/doc/source/admin/drivers/ilo.rst
@@ -222,7 +222,13 @@ Node configuration
   - ``ilo_deploy_iso``: The glance UUID of the deploy ramdisk ISO image.
   - ``instance info/ilo_boot_iso`` property to be either boot iso
     Glance UUID or a HTTP(S) URL. This is optional property and is used when
-    ``boot_option`` is set to ``netboot``.
+    ``boot_option`` is set to ``netboot`` or ``ramdisk``.
+
+    .. note::
+       When ``boot_option`` is set to ``ramdisk``, the ironic node must be
+       configured to use ``ramdisk`` deploy interface. See :ref:`ramdisk-deploy`
+       for details.
+
   - ``ilo_rescue_iso``: The glance UUID of the rescue ISO image. This is optional
     property and is used when ``rescue`` interface is set to ``agent``.
 
diff --git a/doc/source/admin/interfaces/deploy.rst b/doc/source/admin/interfaces/deploy.rst
index 59e52a7e1f..2e7e709980 100644
--- a/doc/source/admin/interfaces/deploy.rst
+++ b/doc/source/admin/interfaces/deploy.rst
@@ -124,15 +124,16 @@ it, see :doc:`Ansible deploy interface <../drivers/ansible>`.
 
    ../drivers/ansible
 
+.. _ramdisk-deploy:
+
 Ramdisk deploy
 ==============
 
 The ramdisk interface is intended to provide a mechanism to "deploy" an
 instance where the item to be deployed is in reality a ramdisk.
-Most commonly this is peformed when an instance is booted via PXE or iPXE,
-with the only local storage contents being those in memory. Initially this
-is only supported by the ``pxe`` boot interface, but other boot interfaces
-could support this funtionality in the future.
+Most commonly this is peformed when an instance is booted via PXE, iPXE or
+Virtual Media, with the only local storage contents being those in memory.
+It is suported by ``pxe`` and ``ilo-virtual-media`` boot interfaces.
 
 As with most non-default interfaces, it must be enabled and set for a node
 to be utilized:
@@ -171,7 +172,3 @@ or desired. As such, this interface does come with several caveats:
 * As with all deployment interfaces, automatic cleaning of the node will
   still occur with the contents of any local storage being wiped between
   deployments.
-
-.. warning::
-   As of the Rocky release of the BareMetal service, only the ``pxe`` boot
-   interface is supported.