HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration

example, network cards, files, logical volumes, and so forth)
are collectively referred to as backing stores.
Integrity VM recognizes the following types of guest virtual
devices:
• Virtual disks, which can be backed by files in a VM
Host file system, by logical volumes or by whole disks.
• Virtual DVDs, which can be backed by files in a VM
Host file system or by the physical DVD drive.
• Virtual network devices, which are created through
the hpvmnet command and backed by physical LAN
cards. For more information about virtual network
devices, see hpvmnet(1M).
For information about specifying storage and network
resources for guests, see the hpvmresources manpage.
Integrity VM Version 4.2 supports the usage of both legacy
and agile devices in guest configurations. Over time, you
should migrate from using legacy device names to agile
device names to simplify the management of devices. You
can use the hpvmmodify -P guest -m rsrc command
to change the existing legacy device to its agile device
equivalent. The ioscan -m dsk command displays the
mapping of the agile devices to legacy devices for the
specific device special file, dsf.
NOTE: The rmsf -L command should not be executed
on an Integrity VM server until all guest devices names
have been changed to agile device names.
The following commands are helpful for reconfiguring
guests to use agile device names:
• insf
By default, creates both persistent and legacy DSFs
for new devices.
• insf -L
Restores legacy DSFs and legacy configuration
information.
• rmsf -L
Aids in migration by removing all legacy DSFs and
legacy configuration information.
• ioscan —m dsf
Maps persistent DSFs to their equivalent legacy DSFs
and vice versa.
• ioscan -N
Prints persistent DSFs when used with the -n option
to list DSFs.
273