HP Integrity Virtual Machines 4.3: Release Notes (5900-2265, May 2012)

With the virtual iLO Remote Console, captive accounts are not supported. The guest
administrator should be created with the default shell:
# useradd -g users \
-c "Console access to guest 'testme'" \
testme1
The hpvmmodify -P -u testme1:admin [-u testme1:oper] is still required, as well as
the setting of a password for the user testme.
7.2.3 New Features Added to Integrity VM AVIO Networking
The following two new features have been added to Integrity VM AVIO networking:
• Multiple localnet support
By using this feature, you can create multiple instances of localnet vswitches. AVIO guests
configured on each localnet vswitches can communicate only among themselves. Additionally,
guests configured on the localnet vswitches cannot communicate with the VM Host or the
external world.
• Guest VLAN support for AVIO localnet
Integrity VM V4.3 introduces support for Guest VLAN tagging for local networks. Prior to
V4.3, this feature was supported only for guests that were configured on vswitches backed
by physical PPA. Starting with Integrity VM V4.3, the same Guest VLAN tagging support is
also supported on localnet vswitches.
For information about managing AVIO local networks, see the HP Integrity Virtual Machines 4.3:
Installation, Configuration, Administration manual.
7.2.4 IP Aliases Configured on the LAN Bound to a vswitch
If IP aliases were configured on the LAN bound to a vswitch, hpvmnet did not display the correct
primary IP address of the LAN. This problem has been corrected.
7.2.5 AVIO LAN Devices Left Unclaimed by OpenVMS Guest if vswitch is Down at
Boot
If you boot an OpenVMS guest while the vswitch is not UP, AVIO interfaces associated with the
vswitch might not be claimed in the guest. For example, this issue might occur if the guest is booted
prior to booting the vswitch, or if the corresponding network interface on the VM Host is not cabled
during the guest boot time.
If you encounter this problem, perform the following steps:
1. Fix the vswitch state; that is, ensure that the hpvmnet command displays the vswitch state as
UP.
2. Once the vswitch is started, reboot the OpenVMS guest to get the AVIO LAN devices
recognized, which ensures that all the AVIO LAN interfaces that are configured through this
vswitch are recognized by the guest.
7.2.6 Using IP Alias Addresses in the Guest Not Supported for IPv4
With the exception of Serviceguard, Integrity VM Version 4.3 does not support the use of IP alias
addressing in the guest for IPv4.
7.2.7 Suspend and Resume During Guest Boot Might Cause Guest VIO LAN Problem
The suspend and resume operations during guest boot might cause the guest VIO lan not to operate.
In this case, the lanadmin command displays the Operation Status of a guest VIO LAN as down.
Use the reset command in lanadmin to enable the guest VIO LAN to function properly.
30 Networking Information