This section explains how to collect cloning images.
Use the following method to collect cloning images:
After installing an OS, stop the target L-Server.
Right-click the target L-Server in the orchestration tree, and select [Cloning]-[Collect] from the popup menu.
Click <OK>.
A cloning image is collected.
A given cloning image (identified by its name attribute) can be managed by image version.
Point
When the destination folder for image storage is omitted during the collection of cloning images, an accessible disk from a VM host in the same storage pool as the disk used by the L-Server that is the target for collecting cloning images is automatically selected.
When automatically configuring the IP address or the host name on the OS for the L-Server to create, follow the procedures below, as the preparations and conditions differ depending on the OS type of the cloning image to use.
When using a Linux cloning image
There are no preparations.
When using a Windows cloning image
OS versions supporting the OS auto-configuration functions
Microsoft(R) Windows Server(R) 2008 R2
Versions other than the above are not configured, even if the version is entered on the [OS] tab.
Preparations
Perform the following preparations:
Install the following packages on the host OS.
- guestfish.x86_64
- libguestfs-mount.x86_64
- libguestfs-tools-c.x86_64
- libguestfs-tools.x86_64
- perl-Sys-Guestfs.x86_64
- perl-Sys-Virt.x86_64
- perl-XML-Parser.x86_64
- perl-XML-Writer.noarch
- perl-XML-XPath.noarch
- perl-libintl.x86_64
- libguestfs-winsupport.x86_64
Obtain libguestfs-winsupport from the "RHEL V2VWIN (v. 6 for 64-bit x86_64)" channel for Red Hat Network.
For details, refer to "Chapter 17. Guest disk access with offline tools".
URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Administration_Guide/index.html |
For L-Servers from which cloning images will be collected, install the virtio driver (the driver to recognize virtual devices) for Windows.
There are virtio drivers related to memory, network, and disk I/O.
When drivers related to memory or disk I/O are provided by RedHat, endure that they are installed.
For details, refer to the following section in the "Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide".
Chapter 9. Installing a fully-virtualized Windows guest
Chapter 10. KVM Para-virtualized Drivers
URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Virtualization_Host_Configuration_and_Guest_Installation_Guide/index.html |
Edit the registry of the L-Server the cloning image will be collected from as follows:
Value Name | Data Type | Value |
|---|---|---|
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\DefaultPassword | REG_SZ | Administrator's password (*) |
* Note: Ensure the Administrator's password is entered.
OS auto-configuration cannot be performed, even if the password of another user ID with Administrator privileges is entered.
The tool to edit the registry above is stored in the Resource Orchestrator DVD-ROM (the first one).
Storage Location for Tool
/DISK1/Common/kvm_windows_setting
File Name for Tool
passwd_for_cloning.bat
Use the following procedure to execute the tools.
1. Store the tools in the folder for the L-Server to collect cloning images from.
2. Execute the command prompt as an administrator.
3. Execute the tools from the command prompt.
The prompt to enter the password is displayed.
4. Enter the password for the Administrator.
The password entered in the registry above is configured.
Example
C:\> passwd_for_cloning.bat
When performing OS auto-configuration, the following registries are edited by Resource Orchestrator.
Value Name
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\ RunOnce
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\AutoAdminLogon
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsNT\CurrentVersion\Winlogon\DefaultUserName
Also, the following registries are read by Resource Orchestrator.
Value Name
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProductName
- HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\SessionManager\Environment\PROCESSOR_ARCHITECTURE
Information
The response files that exist in the L-Server OS to collect a cloning image from cannot be used in the OS auto-configuration functions of Resource Orchestrator.
Note
If an L-Server is created with a specified Windows image, when deploying the image use Sysprep, provided by Microsoft, to re-configure the properties unique to the server. By executing Sysprep, the user information and OS setting information are reset.
For details on Sysprep, refer to the information provided by Microsoft.
If stopping or restarting of the manager is performed during execution of Sysprep, the operation being executed will be performed after the manager is started.
Until the process being executed is completed, do not operate the target resource.
When using MAK license authentication for activation of Windows Server 2008 image OS, Sysprep can be executed a maximum of three times. Since Sysprep is executed when creating L-Server with images specified, collection of cloning images and creation of L-Servers with images specified cannot be performed more than four times. Therefore, it is recommended not to collect cloning images from L-Servers that have had cloning images deployed, but to collect them from a dedicated master server.
If an L-Server is created with a Windows image specified, use Sysprep to set the server specific information again, when starting for the first time after creating the L-Server. After startup, and resetting of the server specific information, when the L-Server console is opened you will be logged on with Administrator status. Therefore, it is recommended that you log off.
Note the following points when collecting cloning images from an L-Server that was created using a cloning image.
As L-Servers which have not been used even once after creation do not have server specific information set, creation of L-Servers using cloning images collected from an L-Server may fail.
When collecting cloning images, set the server specific information on L-Server, after starting the target L-Server.
Information
The disk resource in which cloning images are stored will be "already allocated" in the "Allocation" in the "Configuration Information" confirmed in "Disk Details", and in the state where there is no information in "L-Server Properties".
When collecting cloning images, enter the disk resource name to use for storing cloning images in Comment. The relationship between the cloning image and the disk resource can be checked in "Comment" for each resource in the "Resource List".
