Unsupported content

 

This version of the product has reached end of support. The documentation is available for your convenience. However, you must be logged in to access it. You will not be able to leave comments.

Creating the VGP in BMC Server Automation for Hyper-V

You can build a repeatable process for deploying new virtual systems by using a virtual guest package (VGP). The VGP describes the new virtual system you want to add.

Before you begin

Review the following sections for requirements and recommendations for creating VGPs.

Requirements

  • Create VGPs in the CSM_Virtual_Guest_Packages folder (under Depot) in the BMC Server Automation Console.
  • Ensure that Windows templates and Linux templates are created as described in the BMC Server Automation documentation.
  • Ensure that the VGP for bare-metal VMs is assigned a larger disk space than the space that is assigned to the system package. Otherwise, the provisioning fails with the somewhat misleading error message OS Not Found.
  • Ensure that the guest VM has the latest version of the VMM agent installed and running as a service. For successful Linux provisioning, the guest VM must have the latest version of the VMM agent installed and running as a service. The VMM 2012 SP1 Beta does not ship the VMM agent, so you must use the GA version of Microsoft VMM 2012 SP1. Click here to review the Microsoft online technical documentation for installing the VMM agent.

Recommendations

  • Do not include any static IP addresses in the configuration of the VGP.
  • Do not include any information that is instance-specific, such as a hard-coded host name.

To create a VGP for BMC Cloud Lifecycle Management

This section describes how to create a VGP manually. Beginning with BMC Server Automation 8.2, you can also create VGPs automatically by using the Virtual Guest Template Enrollment Job. For more information, see the related topic in the BMC Server Automation documentation.

  1. From the Depot folder, right-click the depot folder where you want to add the VGP.
  2. From the pop-up menu, select New > Virtual Guest Package and then Hyper-V.

    Note

    You should create VGPs in the Depot in the CSM_Virtual_Guest_Packages folder.

  3. On the Virtual Guest Package dialog, enter the following:

    The VM name and the server name are required. However, BMC Cloud Lifecycle Management overrides these values.

    Field

    Description

    Name

    Enter a name for the package.

    Description

    Enter a brief description of the package.

    Member of

    Browse to the CSM_Virtual_Guest_Packages folder in the Depot.

    VM Guest Package type

    Choose HyperV Bare Metal to configure the VGP and create a new VM, or select HyperV Template Based to base the VGP on an existing template. If you selected the template-based option, perform the following steps:

    • Click Browse to choose a template on which to base the new VM.
    • Select the server that contains the template.
    • Select the template from the displayed list, and click OK.
  4. Click Next.
  5. On the Permissions panel, verify that VirtualGuestPackageHyperV.* permissions is enabled for the VGP.
  6. Click Finish.
    A dialog displays, indicating that the package is being saved to the Depot.

To modify the VGP

BMC Server Automation does not support the Add disk option for a powered on VM. Any subsequent transactional requestable offerings that use that option will fail.

After the VGP is saved, the VGP editor is displayed, enabling you to modify the VGP.

  1. On each tab in the editor, enter the desired configuration settings for your VGP. The following panels apply to Hyper-V environments:
    • Microsoft Hyper-V - Basic panel

      Only a static memory configuration is supported; dynamic memory configuration is not supported.

      Note

      If the VGP is based on a template,  you must select the Customize OS checkbox.

    • Microsoft Hyper-V - Storage panel

      The first disk in the VGP should always be type IDE.

    • Microsoft Hyper-V - Network panel

      For Microsoft Windows 2003 64 bit systems, the NIC type must be synthetic.

    • Microsoft Hyper-V - Advanced panel

    • VM Basic Config - Microsoft Windows panel

    • VM Basic Config - Linux panel

    • VM Computer Settings panel

  2. Save the package.

Where to go next

Publishing the Product Catalog

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Comments