Use the following procedure to create L-Servers:
Create an L-Server using an L-Server template
When there are no cloning images, or when not using cloning images which have been already registered
Create an L-Server, referring to "16.1 Creation Using an L-Server Template" in the "User's Guide for Infrastructure Administrators (Resource Management) CE". When creating the L-Server, select [None] for images.
In this case, the created L-Server may not be displayed in the orchestration tree.
For details, refer to "Note- When the created L-Server is not displayed in the orchestration tree".
For details on the created VM guests or cloning images, refer to "Information- Information created during L-Server creation".
Install an OS, referring to "Manual OS Installation".
When collecting cloning images after creating an L-Server, the cloning images are stored in the image pool. When collecting cloning images, refer to "C.3.8 Collecting and Deleting Cloning Images".
When using an existing cloning image
Create an L-Server, referring to "16.1 Creation Using an L-Server Template" in the "User's Guide for Infrastructure Administrators (Resource Management) CE". In this case, specify the cloning image that you want to use as an image.
Create an L-Server specifying individual specifications
Refer to "16.3 Creation of Virtual L-Servers Using Parameters" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For details on the [OS] tab settings, refer to "C.3.9 [OS] Tab Configuration".
Note
When the created L-Server is not displayed in the orchestration tree
When using the following SCVMM functions for the VM of the created L-Server, after this, the L-Server will not be recognized or displayed in the orchestration tree, and operation of the L-Server becomes unavailable.
Saving in the library, deploying from the library
New template
Transfer the template to a cluster node that is not managed by Resource Orchestrator
When "copying" is performed, the copied VM is not recognized as an L-Server.
Information
Information created during L-Server creation
VM guests created as L-Servers have the following configuration:
Connected to the primary channel (0) of IDE device
Connected to a SCSI adapter as data disk (*)
Connected to the secondary channel (0) of IDE device
* Note: Cannot be used on guest OSs without the integrated service. Only boot disks connected to the IDE adapter can be used.
When a guest OS that Hyper-V supports is specified, a converged network adapter will be used. When a different OS has been selected, an emulated network adapter will be added.
For details on the guest OSs supported by Hyper-V, refer to the following Microsoft web site.
Microsoft download web site
URL: http://technet.microsoft.com/en-US/library/cc794868(v=ws.10).aspx |
"1.00GHz Pentium III Xeon" or "3.60 GHz Xeon (2 MB L2 cache)" (the SCVMM default value) is specified. The CPU type is used for internal operations of SCVMM, and it does not indicate the CPU performance.
It is also different from the information displayed for the computer information of the guest OS.
Using cloning images, collection or deployment of data disks other than system volumes can be selected.
When registering a template created using SCVMM in the image pool of Resource Orchestrator, use a template created from a VM guest that has the system volume (a disk connected to primary channel (0) of the IDE device).
In other configurations, deploying using Resource Orchestrator will create VM guests without system volumes.
Manual OS Installation
Manually install an OS, after configuring the DVD connection settings from the SCVMM management window.
To use a guest OS supported by Microsoft on Hyper-V, it is necessary to install a virtual guest service on the guest OS.
For details on virtual guest service installation, refer to the Help of SCVMM.
