HP Integrity Virtual Machines Version 4.2 Release Notes

4 Installing Guests
This chapter describes notes pertaining to installing guest software on the virtual machines.
4.1 Windows Guests
The following sections contain the release notes specific to installing Windows guests.
4.1.1 Changes and Issues in This Release
The following sections describe changes, issues, and new information pertaining to this release.
4.1.1.1 Windows Server 2003 Guests No Longer Supported
Starting with Integrity VM V4.2, the Windows Server 2003 guest is not supported.
4.1.2 Known Issues and Information
The following sections describe known issues and information from previous releases that still
apply to V4.2.
4.1.2.1 Disable the NetBIOS Over TCP (NBT) Protocol for Windows Server 2008 Guests
Due to instability with the NetBIOS over TCP (NBT) protocol when using network shares in
Windows Server 2008 guests, HP strongly advises that this protocol be disabled until this problem
is fixed in a future release of Windows Server 2008.
For information about this issue, including how to disable the protocol, see the article, Direct
hosting of SMB over TCP/IP, at the Microsoft support website.
4.1.2.2 Removing Media During Installation Hangs Guest
If you begin the installation of the Windows operating system and then eject the media from the
virtual console, the guest hangs. To recover from the problem, restart the guest from the virtual
console.
4.1.2.3 Network Driver for Some Windows Guests Not Behaving Correctly
The network driver for some Windows guests is not behaving correctly if the network device is
configured at PCI bus 0, device 3, function 1, because of an interaction with the console device
at PCI bus 0, device 3, function 0. To avoid this issue, do not specify PCI bus 0, device 3 as an
address when adding network devices to a Windows virtual machine.
There is no issue if hpvmcreate or hpvmmodify automatically assign PCI addresses. This
problem can be corrected by removing any network devices at PCI bus 0, device 3 and adding
them at any other free PCI address.
4.1.2.4 Setting a Static IPv4 Address at the SAC> Prompt
If you want to set a static IPv4 address at the SAC> prompt using the i command after a guest
boot, the first i command entered to set the guest IPv4 address to a static IP address can fail with
the SAC could not set the IP Address. SAC> prompt message. This can cause Remote
Desktop connection to this guest to fail. Enter the same i command to set the static IPv4 address
correctly.
4.1.2.5 Guest Kit for Windows Server 2008
The guest kit for Windows Server 2008 is different from the guest kit for Windows Server 2003.
To operate correctly, each version of Windows (2003 and 2008) must use the guest kit for that
4.1 Windows Guests 41