| United States-English |
|
|
|
![]() |
HP Integrity Virtual Machines Installation, Configuration, and Administration > Chapter 3 Installing Integrity VMPostinstallation Procedures |
|
Once the Integrity VM software is installed and running, the VM Host is available. Enter the following command to get information about the status of the guests:
You can create guests now by using the hpvmcreate command, as described in “Creating Guests.” First, however, the following virtual machine tasks should be performed:
The following sections describe these procedures. In order to provide network access for guests, you must create virtual network switches (vswitches) for them. This section describes how to create a vswitch and verify that it has started. (For information about how virtual switches work, see “Virtual Network Devices,” in Chapter 2.) To create virtual switches, use the hpvmnet command. The following is the basic format of a command that creates a virtual switch:
where:
Table 3–3 describes some of the functions of the hpvmnet command. Table 3-3 Options to the hpvmnet Command
For a complete list of hpvmnet command options, refer to hpvmnet(1M). To display the existing vswitches, enter the hpvmnet with no arguments and options. The following command creates a virtual switch called clan1 associated with lan1. The hpvmnet command is used to display the clan1 vswitch.
Note that localnet is automatically created for the local network. For a guest to use the localnet device, it must be added to the guest's configuration. To start a vswitch, enter the hpvmnet command with the -b option. For example, to start the vswitch named clan1, enter the following command:
Note that clan1 is associated with the network interface with the MAC address 0x00306e3977ab. To delete a vswitch, first stop the vswitch and then enter the hpvmnet command with the -d option. For example:
For information about allocating vswitches to guests, refer to “Creating Guests” in Chapter 4. For information about modifying virtual networks, refer to “Configuring Virtual Networks” in Chapter 5. As stated in “Planning Your Virtual Machines,” some devices should be restricted for use by the VM Host. The VM Host system boot device and swap disk, as well as any logical volumes used by the VM Host should be restricted from access by guests. Define restricted devices before you create guests in order to prevent accidental conflicts. You can also restrict network devices to the VM Host. This provides a dedicated network connection for the VM Host system. To restrict access to storage and network devices, use the hpvmdevmgmt command. For example, the following command restricts a logical volume: # hpvmdevmgmt -a rdev:/dev/vg00/lvol8 You also use the hpvmdevmgmt command to display a list of the restricted devices. For example:
To list the devices available on the VM Host system, use the ioscan command. The hpvmdevmgmt command is also useful for defining shared devices. Integrity VM provides secure access to guest consoles. When you create the guest, you can specify the group account or user account that will have guest administration privileges. These users are allowed to log on to the guest under their own user accounts and use the hpvmconsole command to perform system administration tasks on the guest virtual machine. There are two types of console users: admin and oper. Use the hpvmcreate, hpvmmodify, and hpvmclone commands with the -g and -u options to assign admin and oper privileges. You cannot use the su command to change from one privilege level to another. Per-user checks are based on real login account identifiers, not UUIDs. Guest operators and administrators need access to the hpvmconsole command to control the virtual machine. If you do not want the same user to have access to the VM Host, you can restrict their use of the hpvmconsole command to guest console access only by creating a restricted account for that purpose, as follows:
A guest administrator can now access the compass1 virtual console using the ssh command or telnet command on the VM Host and logging in to the compass1 account. The guest administrator cannot use the su command.
The following is an example session of remote access to the compass1 virtual console on the VM Host myhost:
The virtual console interface displays raw characters for the CL and CO command, including the guest's attempts to query the console terminal for its type and characteristics. As a result, the terminal answers those queries, which can cause the terminal setup communication to interfere with your console commands. Interactive users can clear the screen. This situation can be a problem, however, for noninteractive or scripted use of the console. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
|||||||||||||||