Scenario

This document describes how to prepare a Windows image by using the Windows Server 2012 operating system as an example.

Directions

Preparations

Before preparing and exporting a system disk image, complete the following checks.

If you need to prepare and export a data disk image, skip this operation.

Check the partitioning mode and launch mode of the operating system

1. In the operating system, click to open the “Windows PowerShell” window.
2. In the “Windows PowerShell” window, enter gpedit.msc and press Enter to go to “Disk Management”.
3. Right-click the disk to check, choose Properties, click the Volume tab, and check the disk partitioning mode.
4. Check whether the disk partitioning mode is GPT.
   • If yes, submit a ticket because service migration currently does not support the GPT partition.
   • If no, proceed with the next step.
5. Start CMD as admin, and run the following command to check whether the operating system launches in EFI mode:

   bcdedit /enum {current}

   The return result is similar to the following:

   Windows boot loader
   ID                  {current}
   device                  partition=C:
   path                    \WINDOWS\system32\winload.exe
   description             Windows 10
   locale                  zh-CN
   inherit                 {bootloadersettings}
   recoverysequence        {f9dbeba1-1935-11e8-88dd-ff37cca2625c}
   displaymessageoverride  Recovery
   recoveryenabled         Yes
   flightsigning           Yes
   allowedinmemorysettings 0x15000075
   osdevice                partition=C:
   systemroot              \WINDOWS
   resumeobject            {1bcd0c6f-1935-11e8-8d3e-3464a915af28}
   nx                      OptIn
   bootmenupolicy          Standard

   • If path contains "efi", the operating system starts in EFI mode. In this case, submit a ticket.
   • If path does not contain "efi", proceed with the next step.

Unmounting software

Unmount the drivers and software programs (including VMware tools, Xen tools, Virtualbox GuestAdditions, and other software that comes with underlying drivers) that produce conflicts.

Installing cloud-base

Install cloud-base by referring to Installing cloud-base.

Checking or installing the virtIO driver

1. Choose Control Panel > Programs and Features, and enter "Virtio" in the search box.
   • If the result shown in the following figure is returned, the virtIO driver has been installed.
     
   • If the virtIO driver is not installed, manually install the virtIO driver.
     • For Microsoft Windows Server 2008 R2 (Standard Edition, IDC Edition, and Enterprise Edition), and Microsoft Windows Server 2012 R2 (Standard Edition), download Virtio for Tencent Cloud.
     • For other operating system versions, download virtIO for Community.

Checking other hardware-related configurations

After the migration to the cloud, hardware changes include but are not limited to:

• The graphic card is changed to Cirrus VGA.
• The disk is changed to Virtio Disk.
• The ENI is changed to Virtio Nic, and Local Area Connection is used by default.

Exporting an image

You can select different tools to export an image based on your actual requirements.

• Use a platform tool to export an image
• Use disk2vhd to export an image

Using a platform tool to export an image

For more information on how to use the image export tools of virtualization platforms, such as VMWare vCenter Convert and Citrix XenConvert, see the document for the respective platform.

Tencent Cloud supports the following image formats for service migration: QCOW2, VHD, RAW, and VMDK.

Using Disk2vhd to export an image

To export the system on a physical machine or if you do not want to use a platform tool to export an image, use Disk2vhd instead.

1. Install and start the Disk2vhd tool.
   Click here to download Disk2vhd.
2. Select the storage path of the image to export, select the volumes to copy, and click Create, as shown in the following figure.

   • Disk2vhd can be started only after the Volume Shadow Copy Service (VSS) is installed in the Windows system.
   • Do not select "Use Vhdx" because the system currently does not support images in VHDX format.
   • We recommend that you select "Use volume Shadow Copy" to better ensure data integrity.

   

Checking the image

The image file system that you prepare may be corrupted because you prepared the image without stopping the service or due to other reasons. Therefore, we recommend that you check the image after preparing it.

If the image format is supported by the current platform, you can directly open the image to check the file system. For example, the Windows platform supports the VHD image, the Linux platform allows you to run qemu-nbd to open QCOW2 images, and the Xen platform allows you to directly open VHD files.
Take the Linux platform as an example:

modprobe nbd
qemu-nbd -c /dev/nbd0 xxxx.qcow2
mount /dev/nbd0p1 /mnt

If the file system is corrupted when the first partition of the QCOW2 image is exported, an error occurs when you run the mount command.
You can also launch the CVM to check whether the image file works before uploading the image.