HP Integrity Virtual Machines 4.3: Installation, Configuration, Administration

8.12.2.2 Replacing Devices
If a backing storage device malfunctions, replace it by using the hpvmdevmgmt -n option. The
-n option works for only guest devices. It replaces the existing device entry with the new device
entry while keeping all the current guest dependents. Thus, each guest dependent is modified
to replace the old device with the new one. If the device being replaced is a pNIC, use the hpvmnet
command to halt and remove the current vswitches using that pNIC and recreate the same named
vswitches using the new pNIC. This method allows guests to use the new pNIC through the old
vswitch names without modifying the guests.
8.12.2.3 Deleting Devices
A device entry can be deleted only if it has no dependents. If a device has dependents, those
dependents must be removed before you delete the device. The hpvmmodify command that
removes a device removes that guest as a dependent on that device.
If the guest cannot be modified, you can use the hpvmdevmgmt -d command to delete a
dependent from a device. However, this command does not modify the guest that is dependent
on the device. Use this method only if you can use the hpvmmodify command on the guests
that are dependent on the device. The following example shows how to remove a guest as a
dependent:
# hpvmdevmgmt -d gdev:entry_name:depend:depend_name
8.12.2.4 Restricting VM Host Devices
You must set up restricted devices to ensure that no guest uses devices that are reserved for use
by the VM Host, including the storage devices that the VM Host uses to boot and run. This can
also include a network LAN device to which the host requires exclusive access.
If a volume manager is used for host-specific file systems, then the restricted devices should
include both the volume devices and the underlying special device files to protect both from
guest access. For more information, see Chapter 6 (page 83).
You can also allow guests to access certain files while restricting them from accessing the device
files that contain those files. You can add or delete restricted device entries to the Integrity VM
device database.
For example, to add /dev/rdisk/disk0 as a restricted device, enter the following command:
# hpvmdevmgmt -a rdev:/dev/rdisk/disk0
To delete the restricted device /dev/rdisk/disk0, enter the following command:
# hpvmdevmgmt -d rdev:/dev/rdisk/disk0
To add network lan0 as a restricted device, enter the following command:
# hpvmdevmgmt -a rdev:lan0
If a guest's configuration file contains restricted devices, the guest does not start.
8.12.3 Inspect and Edit the Repair Script
The hpvmdevmgmt -r report and repair-script function might identify one or more new
pathnames for disks whose old pathnames no longer exist. The repair-script performs that
reassignment using the hpvmdevmgmt -n command.
In general, you should inspect and edit the script before running it for the following reasons:
• All replace commands, hpvmdevmgmt —n, in the script are commented out. You must delete
only the comment characters before only one of the hpvmdevmgmt —n commands for a
particular device. Otherwise, subsequent hpvmdevmgmt -n commands for the same device
will fail.
• If a legacy device name is replaced with another legacy device name, both the legacy device
name and the agile device name are added. However, if the agile device name is used to
replace a legacy device name, only the agile device name is used.
172 Managing Guests