What is Virtual Server Import?

This function is used to migrate a virtual server running on your on-premises virtual environment to IaaS. This function allows you to register image files that you have captured as image files that can be used in IaaS.

The diagram below shows how this function is used.

Figure: Using Virtual Server Import



Supported Migration Source Virtual Environments

A list of supported migration source virtual environments is shown below.

Table 1. List of Migration Source Virtual Environments
Virtual Environment Product and Version
VMware
  • ESX/ESXi 6.0 5.5 5.1 5.0
  • vCenter Server 6.0 5.5 5.1 5.0
FUJITSU Software ServerView Resource Orchestrator1
  • ServerView Resource Orchestrator v3.1 v3.2
Note: BIOS startup is supported in any virtual environment. UEFI startup is not supported.

Migration Source Guest OS Types that Can Be Imported

A list of migration source guest OS types that can be imported is shown below.

Note: Appliance products are not supported.
Table 2. List of Migration Source Guest OS
OS Type Supported OS
Windows
  • Windows 2008 R2 SE 64bit (Japanese Version, English Version)
  • Windows 2008 R2 EE 64bit (Japanese Version, English Version)
  • Windows 2012 SE 64bit (Japanese Version, English Version)
  • Windows 2012 R2 SE 64bit (Japanese Version, English Version)
  • Windows 2016 SE 64bit (Japanese Version, English Version)
Linux
  • CentOS 6.5, 6.6, 6.7, 6.8 64bit
  • CentOS 7.1, 7.2 64bit
  • RHEL6 64bit
  • RHEL7 64bit
  • Ubuntu 14.04 LTS 64bit

Limitations on Migration Source Virtual Server Configurations

  • Disk Configuration

    Only system storage that is on the startup disk can be imported. Additional storage cannot be imported.

    In addition, no support is provided for any of the following:

    • Dynamic disk (if the OS type is Windows)
    • Formats other than NTFS/FAT32 (if the OS type is Windows)
    • Disks encrypted with BitLocker (if the OS type is Windows)
    • A Windows system of which the Windows folder has been renamed to anything other than the default '\Windows' (if the OS type is Windows)
    • Volumes with the "NODEFAULTDRIVELETTER" attribute enabled (if the OS type is Windows)
    • GPT format disks
    • Multi-boot environments

  • Network Interface

    One network interface must be defined.

  • Sysprep

    When duplicating virtual servers, if the OS is Windows, do so using Sysprep on the migration source virtual environment or on the virtual server after import. For how to use Sysprep and response files, refer to Microsoft technical support.

Note:

When executing Sysprep and importing an image on which Sysprep will be used when the OS starts, note the following points.

  • For Sysprep, only use OOBE (Out-of-box Experience) mode with generalized settings. At that time, prepare a response file.
  • In cases other than the above, the system wizard window is displayed the first time the server is started which means that the system wizard window cannot be operated as remote desktop connections are not possible.

  • When creating a virtual server using an imported image, the values for the following items in the response file will not be applied.

    • Administrator password: The password specified using the portal or the API will used
    • Machine name: The name configured in the system will be used

Handling of Licenses

The handling of licenses by type of imported OS is shown below.

Table 3. Handling of Licenses by Type of Imported OS
Type of Imported OS Handling of License
Windows When you import a virtual server, the license is automatically changed to an SPLA license. After importing, perform KMS activation.
Linux

  • Red Hat Enterprise Linux

    Before importing the OS image, you need to register Cloud Access. For a virtual server that is created from an image that was imported, assign the Cloud Access from Red Hat or Fujitsu for the subscription that you have purchased. For IaaS, no charges apply. Your [Corporate Name], [Mail Address], and [Number of Virtual Servers Created from an Imported RHEL Image] will be reported to Red Hat on a monthly basis. Refer to the following URL for details about Cloud Access:

    https://www.redhat.com/en/technologies/cloud-computing/cloud-access

    Note:
    • You cannot use RHUI provided by common network services. Do not install RHUI Agent.
    • You cannot receive IaaS software support service. Support service for your OS is provided from the source where you purchased your subscription.
    • To cancel your subscription to Cloud Access, contact Red Hat.

  • CentOS

    No license required.

  • Ubuntu

    No license required.
Tip:

Specify the following information when subscribing to Cloud Access.

Table 4. Settings Required to Specify for Cloud Access Subscription
Cloud Provider FUJITSU Cloud Service for OSS
Cloud Provider Account Number Contract number for FUJITSU Cloud Service for OSS
Product Name Subscription name to be used for the RHEL that you intend to migrate
Quantity Subscription types (not the number of cloud accounts assigned) to be used for the RHEL that you intend to migrate

How to Use This Service

Perform the following operations to import the image on the migration source virtual server to IaaS.

Figure: How to Use Virtual Server Import



1 Hypervisors are supported for VMware only.