Dynamic workload movement with BladeSystem Matrix: Fluid movement between physical and virtual resources for flexibility and cost-effective recovery

8
also be configured to emulate either the LSI Logic Parallel or LSI Logic SAS storage type if using
Windows 2008 or LSI Logic Parallel if using Windows 2003.
In all versions of Windows 2008, the driver needed to properly operate the virtual version of the LSI
controller is installed, but disabled. In Windows 2003 the necessary driver is not there and needs to
be installed and enabled.
PISA is used to enable the LSI support in the Windows image. How PISA operates is different
depending on whether it is on Windows 2008 or Windows 2003.
This tool is a simple command line tool that only accepts a few command line options. It just needs to
be executed once after Windows has been installed on a physical server. The changes it makes will
be persistent and do not need to be repeated nor reversed. However, repeatedly running the tool will
have no negative impact. The tool can also be used to disable the driver used by the virtual machine.
The command line interface for this tool is described below. The options are mutually exclusive.
The tool will only run on supported versions of Windows and requires that the user be a member of
the Administrator user group.
Usage: hppisa <option>
-h, -?, -help Show this information
-e, -enable Enable the LSI driver
-d, -disable Disable the LSI driver
Once these changes are made, the OS image can be moved back and forth between physical servers
and servers running virtual machines.
PINT
PINT is used to resolve networking issues when you move an OS image from one physical server to
another or from a physical server to a VMware ESX virtual machine.
PINT gathers information regarding each of the network interfaces and their corresponding
configurations on the server and keeps the information in a configuration file.
In almost all cases, the OS will create new interfaces for the target server‟s NICs. There are a couple
of exceptions to this; one in Windows, and one in SuSE.
In Windows, if the new NIC is exactly the same as the original NIC, including being in the same slot,
same level of firmware, etc, Windows will use the existing interface and its configuration. This
behavior causes PINT to remove from consideration any interfaces that were handled this way by
Windows.
SuSE boot will always create new interfaces for all of the NICs in the server. However, it will not
create configurations for those interfaces. The exception to this is if there have never been any
configurations created for any of the interfaces; SuSE will create a DHCP enabled configuration for
one of the interfaces. This causes PINT to have to create the configuration for any interfaces that have
not been configured and there is a free unused configuration available Windows and RedHat only
require existing information to be moved around.