Version 2.

0 - 07/2020
Table of Contents
INTRODUCTION 3

SUPPORT LIMITATIONS AND DISCLAIMER 3

REQUIREMENTS 3

CREATE AND EXPORT THE HC3 VM TEMPLATE 3

COPY THE FOREIGN DISK FILES OVER THE EXPORTED HC3 VM DISK FILES 4

IMPORT THE FOREIGN DISK FILE DATA THROUGH THE HC3 WEB INTERFACE 5

INJECT THE VIRTIO PERFORMANCE DRIVERS INTO WINDOWS VMS POST MIGRATION (OPTIONAL) 5

COMMON TROUBLESHOOTING FOR IMPORTS AND EXPORTS 6

PRE-PROCESS CHECKLIST 6
DURING THE EXPORT 7
DURING THE IMPORT 7

RESOURCES 7
SCALE COMPUTING 7

FEEDBACK & SUPPORT 8

©2020 Scale Computing. All rights reserved. Any and all other trademarks used are owned by their respective holders. ​2
INTRODUCTION
This guide provides the general steps for importing a foreign virtual machine (VM) or appliance into the HC3 system
to run as a HC3 VM. This includes VHD, VHDX, VMDK, QCOW2, OVA and other file types that have not been
natively exported from the existing HC3 system first.

SUPPORT LIMITATIONS AND DISCLAIMER

The features shown in this guide have been tested in a limited fashion internally and in preliminary use have been
seen to function in most environments in the field. However, the features are not officially tested as part of the
HC3 system and may cause unexpected behavior. Best Effort assistance will be provided at ScaleCare Support’s
discretion unless otherwise noted.

REQUIREMENTS
There are a few requirements before beginning the foreign import process.

● A SMB share must be made available locally to the HC3 system network with read and write credential
access.
● The appliance backing files (disk/data files) for the foreign VM or appliance should be copied into the same
SMB share as the exported HC3 template for the easiest import and conversion process.

NOTE

Imported disks ​cannot​ exceed 8TB in size. Disks exceeding 8TB will cause unexpected behavior
in VM recognition, boot sequences, and/or operation. It is required that disks larger than 8TB be
shrunk or split into multiple disks as necessary.

CREATE AND EXPORT THE HC3 VM TEMPLATE

All steps will be taken through the HC3 web interface.

1. Create a template HC3 VM that matches the configuration of the foreign VM or appliance you would like to
import. This includes matching the operating system (Windows or Other), number of disks, CPU allocation,
and RAM allocation. Disk size will not matter, only that the number of disks match.

©2020 Scale Computing. All rights reserved. Any and all other trademarks used are owned by their respective holders. ​3
 NOTE

When selecting the disk type it is important to select the compatible IDE drivers. Selecting the
Scale Tools performance drivers for a foreign VM or appliance not already utilizing VIRTIO may
cause boot issues on the imported appliance—particularly in a Windows environment. The
performance drivers can be injected after the importation process.

For Linux guests with a kernel version greater than 2.6.32 this is not an issue.

2. Select the Replication and Snapshots icon on the VM card for the template VM that was created (it appears
as a stack of papers on the left side of the VM card).
3. Click the Export VM icon (it appears as a box with an arrow pointing out on the bottom-right of the VM card
in the Replication and Snapshots screen).
4. Enter the SMB share information for the export. See the ​Common Troubleshooting for Imports and
Exports​ section if you need assistance.
5. A folder with the VM’s name will be exported to the specified path. Inside the VM folder will be a single XML
file and a QCOW2 file for each HC3 VM disk that was exported.

COPY THE FOREIGN DISK FILES OVER THE

EXPORTED HC3 VM DISK FILES
All steps will be taken through the SMB share location and on the content of the exported HC3 VM folder.
1. Browse to the SMB share holding the template HC3 VM that was exported.
2. Ensure that the foreign VM or appliance disk backing files are either already in the same SMB share or can be
copied into the SMB share for the following steps.
3. Copy each foreign VM or appliance disk backing file into the VM export folder (the folder with the VM name
containing the XML file and QCOW2 file(s) ). The VMDK file is our foreign backing file.

4. Rename the exported QCOW2 file with some sort of "old" distinction as seen in the first QCOW2 file in the
image below ("W" at the start and "_old" at the end). Rename the (previously VMDK) foreign disk backing
file to match the QCOW2 exported disk file. The VMDK data is now under the exported QCOW2 name.

©2020 Scale Computing. All rights reserved. Any and all other trademarks used are owned by their respective holders. ​4
 5. The disks are a one-to-one conversion. You'll need an exported QCOW2 file for each foreign VM disk
backing file you need to convert. You may need to re-export the HC3 VM files if additional disks are needed.

WARNING

DO NOT alter or remove the XML file exported with the QCOW2 disk file(s). The XML is
required for the import process. If a re-export is needed for additional disks, delete the original
export and DO NOT try to re-use XML files.

IMPORT THE FOREIGN DISK FILE DATA

THROUGH THE HC3 WEB INTERFACE
All steps will be taken through the HC3 web interface.
1. Click the Import VM icon (it appears as the box with an arrow pointing in next to the Create VM icon near
the left-center of the interface).
2. Enter the SMB share information for the import. Ensure the exported HC3 VM folder is included in the Path.
See the Common Troubleshooting for Imports and Exports section if you need assistance.
3. A new VM will be created in the HC3 web interface. The HC3 system will detect the foreign disk format
during the import process and automatically convert the disk(s) to the required QCOW2 file type during the
import.
4. The end result will be a HC3 VM with the QCOW2 format using the foreign VM or appliance data.

INJECT THE VIRTIO PERFORMANCE DRIVERS

INTO WINDOWS VMS POST MIGRATION
(OPTIONAL)
Once the foreign VM or appliance has been imported there is the option to inject the Scale Tools performance
drivers. This generally improves the performance and virtual device capabilities on the VM. This is not required
(but is recommended) and should work for any Windows Operating System (OS) running 2003 R2 and up.

All steps will be taken through the HC3 web interface and in the guest OS.

©2020 Scale Computing. All rights reserved. Any and all other trademarks used are owned by their respective holders. ​5
 1. Ensure the imported foreign VM or appliance can power on and boot normally if you have not already done
so. Troubleshooting should be taken on the importation process before altering the drivers if there are any
boot issues or guest OS abnormalities.
2. Power off the VM that was imported (if necessary).
3. Make sure the newest VIRTIO drivers are mounted in the virtual CD tray. The latest drivers can be found for
download in the Resources section at the end of this guide.
4. Make sure to take a snapshot of the imported HC3 VM while it is powered down and before making any
changes.
5. Add a new disk of the VIRTIO disk type to the powered off VM. The disk size is irrelevant—unless you want
to use the disk going forward—as the disk will be deleted at the end of these steps.
6. Creating a VIRTIO disk type should auto-mount the latest Scale Tools ISO available on the HC3 system. If it
does not, manually mount the latest Scale Tools ISO into a virtual CD tray on the VM.
7. Make sure the IDE disk is still set as the primary boot device in the boot priority list for the VM.
8. Power on the VM.
9. The guest OS should detect the new hardware (the newly added VIRTIO disk). Select Install Device
Manually.
10. Access the CD tray containing the Scale Tools ISO in Windows Explorer (typically drive E). Inside the Scale
Tools package there will be a series of files, including two Windows Installer Packages. One package is for
32 bit systems (ending in x86) and the other is for 64 bit systems (ending in x64). Double click the
appropriate installer for the guest OS.
11. The Scale Computing Guest Tools Setup Wizard will appear. Click Install.
12. A Windows security confirmation window may appear; verify the installation to proceed.
13. The installer will then install and/or update all of the necessary VIRTIO performance drivers automatically.
14. Click Finish when complete to close the wizard.
15. Shut down the VM.
16. While the VM is powered down, change any IDE disk types to VIRTIO in the HC3 web interface.
17. Power on the VM. It should now boot normally with the VIRTIO performance drivers installed. The disk that
was added for the purpose of introducing the VIRTIO drivers to the VM can be used or deleted as needed.

COMMON TROUBLESHOOTING FOR IMPORTS

AND EXPORTS
Common tips and tricks for simple troubleshooting during the VM import and export process.

PRE-PROCESS CHECKLIST
● Remove any custom VM tools or drivers from your previous virtualization platform prior to importing the
foreign VM or appliance.

©2020 Scale Computing. All rights reserved. Any and all other trademarks used are owned by their respective holders. ​6
 ● Have the SMB host’s IP address available. Always use the SMB host’s IP address, not the DNS name. This
resolves many connection issues.
● Have the full domain name and SMB host name available. Both will be needed for the export and import
process.

DURING THE EXPORT

● Ensure the account you are using to import or export the VM has permission to read and write from the SMB
share and that the account is not locked in any fashion.
● The HC3 VM template you export should use the compatibility drivers (IDE). You can transition the VM to
the VIRTIO performance drivers once the foreign VM or appliance is imported and booting correctly.
● Be sure you’re including the domain and host name in your share path.

DURING THE IMPORT

● It's possible to rename the path or XML file during import. An import requires that the pathname and XML
file name match, or the import will fail.
● Ensure the account you are using to import or export the VM has permission to read and write from the SMB
share and that the account is not locked in any fashion.
● Any foreign VM you import should use a HC3 VM template with compatibility drivers (IDE) for the import
conversion process. You can transition the VM to the VIRTIO performance drivers once it’s imported and
booting correctly.
● Be sure you’re including the domain and host name in your share path.
● If you’re having trouble importing a foreign VM file type, export a basic HC3 VM template and immediately
try to import the same VM template back into HC3.
○ If you’re still having trouble with a basic VM template sourced from the HC3 system you can rule out
the foreign VM itself as an issue. Focus on the SMB share, path, or permissions.
○ If you’re able to import the basic VM template sourced from the HC3 system without an issue you
can rule out the SMB share, path, and permissions. Focus on the foreign VM itself.

RESOURCES
SCALE COMPUTING
● Video Walkthrough of the Foreign Import Process - ​https://youtu.be/IM00n89U3jw

©2020 Scale Computing. All rights reserved. Any and all other trademarks used are owned by their respective holders. ​7
FEEDBACK & SUPPORT
DOCUMENT FEEDBACK
Scale Computing welcomes your suggestions for improving our documentation. Please send your feedback to
[email protected]​.

TECHNICAL SUPPORT AND RESOURCES

There are many technical support resources available for use. Access this document, and many others, at
http://www.scalecomputing.com/support/login/​.

● Partner Portal - Partner and Distributor use only.

● User Community - Customer focused, including our online Forum.

©2020 Scale Computing. All rights reserved. Any and all other trademarks used are owned by their respective holders. ​8