Deploying guests

You can use Microsoft Hyper-V Manager or Microsoft System Center Virtual Machine Manager (SCVMMY) to deploy guests.

Deploying with Hyper-V Manager

  1. Open Microsoft Hyper-V Manager.
  2. Click New > Virtual Machine in the Actions panel.
  3. When you are prompted for a location for the VM, choose the volume that is on the LUN that you created in Configuring storage.
After memory and networking configurations, specify the name and location of the hard disk where you want to install the guest OS.
If you are using a VHD
Locate the hard disk on a volume that is on the LUN through the virtual port.
If you are using a pass-through disk
It is better that the disk be from a virtual port, be offline, and be configured as MBR disk type.
A pass-through disk does not support GPT and dynamic disk types. If the disk is previously configured as GPT or dynamic, you must bring the disk online and convert it, in which case you need to shut down the guest.

Deploying with SCVMM

If the host is managed by the SCVMM, complete the following steps to create a VM:
  1. Select the host that has the virtual port active when you are prompted for the host on which to place the guest.
  2. Click Browse and select the LUN that you created when you are prompted for a location for the files.
To configure the disk to install the guest OS, complete the following tasks:
Configuring the Host (Microsoft Hyper-V) Server
  1. Install one of the following operating systems:
    • Microsoft Windows Server 2008 x64
    • Windows Server 2008 R2
    • Microsoft Windows Server 2012
    • Microsoft Windows Server 2012 R2
  2. Install the Microsoft Hyper-V role on the Windows server using the Server Manager, and then restart the server.
  3. Disable automount for the disks on the host. Issue the following commands:
    C:\>diskpart
    DISKPART>automount disable
  4. To allow for remote administration on the physical host, enable the Windows firewall.
  5. Install the MPIO driver that ships with Windows Server 2008.
  6. Install the MPIO driver that your storage vendor supplied.
  7. Install and configure the Microsoft Hyper-V guest OS using the Microsoft Hyper-V Manager. The guest OS can be Windows Server 2003 R2 or later.
  8. Download and install Microsoft Visual C++ 2008 SP1 Redistributable Package on physical host. The package can be downloaded from the Microsoft website:
Configuring IBM® Storage Support for Microsoft VSS and VDS using Hyper-V
  1. Log on to the Microsoft Hyper-V guest OS.
  2. Install the IBM Storage Support for Microsoft VSS and VDS.
  3. Add the host IP address to the VM host file.
  4. Set the parameters to access the host server. For this step, you need the host server domain, user name, and password. The following list provides information about the settings and the relevant commands.
    • To set the user name, issue the ibmvcfg set vmusername command (hyper-V host user name, which can manage hyper-V)
    • To set the password, issue the ibmvcfg set vmpassword command (hyper-V host user password)
    • To set the domain, issue the ibmvcfg set vmdomain command (hyper-V host user domain)
    • To view the configuration settings, issue the ibmvcfg showcfg command
  5. Provide the following privileges for the user:
    • Access WMI on the host Server
    • Query WMI objects in the following name spaces: root/cimv2, root/wmi, root/default, and root/virtualization.
    • Create a process with class Win32_Process in root/cimv2.
    • Manage the resources in the root/virtualization name space.
Set the domain as the host name if the user does not belong to a Windows domain.
Configuring source volumes using Microsoft Hyper-V
  1. Shut down the guest OS and add the iSCSI Controller to the guest OS.
  2. Add the pass-through disk drive to the guest OS.
  3. Log on to the guest OS.
  4. Create a volume on the newly added hard disk and assign a drive letter or mount point to the volume.
Taking snapshots using Microsoft Hyper-V
Before you take a snapshot of the volume on the guest OS, issue the following command to check to see whether the configuration is correct:
ibmvcfg testsnapshot X:

The procedures to take, delete, mask, resynchronize, and import snapshots are the same as the procedures for the physical host. The provider attaches the target LUNs to the physical host and then assigns it to the guest OS as a pass-through disk when taking or importing a snapshot. When deleting or masking a snapshot, the IBM VSS Hardware Provider removes the target LUN from the guest OS before detaching it from the physical host.