Users Guide

Deploying Your Operating System Using VMCLI 215
Floppy/Disk Device or Image File
-f { <device-name> | <image-file> }
where <device-name> is a valid drive letter (for Windows systems) or a valid
device filename (for Linux systems); and <image-file> is the filename and
path of a valid image file.
NOTE: Mount points are not supported for the VMCLI utility.
This parameter specifies the device or file to supply the virtual floppy/disk
media.
For example, an image file is specified as:
-f c:\temp\myfloppy.img (Windows system)
-f /tmp/myfloppy.img (Linux system)
If the file is not write-protected, Virtual Media may write to the image file.
Configure the operating system to write-protect a floppy image file that
should not be overwritten.
For example, a device is specified as:
-f a:\ (Windows system)
-f /dev/sdb4 # 4th partition on device /dev/sdb
(Linux system)
NOTE: Red Hat
®
Enterprise Linux
®
version 4 does not and will not
provide support for multiple LUNs. However, the kernel supports this
functionality, but you must enable Red Hat Enterprise Linux version 4
to recognize a SCSI device with multiple LUNs by following these steps:
1
Edit /etc/modprobe.conf and add the following line:
options scsi_mod max_luns=8
(You can specify 8 LUNs or any number greater than 1.)
2 Get the name for the kernel image by typing the following command at
the command line:
uname -r
3 Go to the /boot directory and delete the kernel image file, whose name you
determined in Step 2:
mkinitrd /boot/initrd-’uname -r’.img ‘uname -r’