Users Guide

158 Configuring and Using Virtual Media
I am viewing the contents of a
floppy drive or USB memory key.
If I try to establish a Virtual
Media connection using the
same drive, I receive a
connection failure and am asked
to retry. Why?
Simultaneous access to Virtual Floppy drives is
not allowed. Before you virtualize the drive, close
the application that you are using to view the drive
contents.
Do I need to install drivers on the
server to make the Virtual Media
feature work?
No. Drivers are not required on either the
managed system or the management station. The
operating system provides what is required for this
feature.
When I performed a firmware
update remotely using the DRAC
4 user interface, I noticed that
the Virtual Drives on the
managed system disappeared.
Firmware updates cause the DRAC 4 to reset,
which causes the Virtual Drives to be unmounted.
You can restore the Virtual Drives on systems
running Windows by either restarting the system
or by using the Windows device manager to scan
for new hardware. You can restore the Virtual
Drives on systems running Red Hat Enterprise
Linux by re-mounting the drives after the
firmware update completes.
What will my Virtual Media
feature look like before the
system is booted?
During system boot, the BIOS lists the virtual
devices that are available. You should see a
message that lists 2 devices as follows:
Drive Number : 0 VIRTUALFLOPPY
DRIVE Removable Media Drive
Drive Number : 1 VIRTUALCDROM
DRIVE
How do I set my virtual device to
be bootable?
You must go into the BIOS setup at the managed
system and then go to the boot menu. Once in the
boot menu, you find a listing for the virtual CD
drive and the virtual floppy drive. You can change
the order of the virtual devices in the boot order.
For example, to boot from a CD drive, you must
put the CD drive first in the boot order.
Table 7-2. Using Virtual Media: Frequently Asked Questions
(continued)
Question Answer