HP Integrity Virtual Machines 4.2.5: Release Notes

7.2.2 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.3 Known Limitation on OpenVMS Guests and HP-UX Guests Sharing the same
vswitch
If you configure an HP-UX guest and an OpenVMS guest with the same vswitch, the network
communication between these guests fail. This problem will be fixed in a future version of OpenVMS.
To workaround this problem, configure the HP-UX guest and the OpenVMS guest with different
vswitches.
7.2.4 OpenVMS Guests Support vswitch-based VLAN Configuration and Not
Guest-based VLANs
AVIO LAN drivers on OpenVMS guests are VLAN tag-unaware and support vswitch-based a VLAN
configuration. Use the following command to configure VLAN for an OpenVMS guest:
# hpvmnet -S vswitch-name -u portid:portnum:vlanid:vlandid
See the HP Integrity Virtual Machines 4.2: Installation, Configuration, and Administration manual
on the BSC website, http://www.hp.com/go/virtualization-manuals.
7.2.5 Networking Interface Support for OpenVMS Guest
The OpenVMS guest supports the AVIO interface; however, Integrity VM commands allow you to
configure either AVIO or VIO devices to a guest, and these devices might not give any apparent
errors during the startup. VIO devices are not supported on OpenVMS guests.
7.2.6 AVIO Non-Physical Network vswitch (localnet) Restrictions
OpenVMS guests that are created (hpvmcreate) or modified (hpvmmodify) to add and use a
non-physical vswitch must use the same vswitch by name for each OpenVMS guest. The following
scenarios fail:
Attempting to start an OpenVMS guest that is using two different localnet vswitches on the
same guest
Using a different localnet vswitch than an already active OpenVMS guest is using
7.2.7 Location of AVIO Networking Driver for Linux and Windows Guests
AVIO networking driver for Linux and Windows are available in VMGuestSW bundle of Integrity
VM host software on the http://software.hp.com website. Go to this website, and search for the
VMGuestSW bundle.
7.2.8 Changing Network Device Type on Linux Guest
If you change the type of network device on a Linux guest, either from VIO to AVIO or AVIO to
VIO, follow these steps:
7.2 Known Issues and Information 71