Shulou(Shulou.com)06/03 Report--

Because Hyper-V is not as convenient as VMware in some aspects of day-to-day management, there may be a need to convert virtual machines on Hyper-v into VMware virtual machines. So here is only a brief introduction to how to convert the virtual machine running on Hyper-V into VMWare through the BE system.

Described in the above figure:

To make the conversion, you must also have an ISO "windows.iso"

When you click OK-à editor, the BE system automatically detects whether the server meets the conditions required for the conversion operation, and the duration of the process depends on the server performance, usually a few minutes.

When the self-test is over, you can see a series of configuration options interface related to the conversion, where you can configure the time when the conversion is executed, the notification of completion, and the detailed settings of the conversion.

Generally, the conversion is one-time, so on this page I only configure the option "convert to virtual (V) immediately after the source task is completed", which means that the conversion job starts immediately after the backup job of this server is completed and successful.

The interface may not be configured in order to notify the manager of the job result.

This page is the core configuration page of the transformation, and its purpose is as follows:

"convert (C) for the following items": refers to what type of virtual machine you want to convert the source to. Only Hyper-V and VMware type conversion is supported here.

"Virtual environment option": this refers to where you want to store the converted virtual machine. You need to enter the name of the server where the target is stored (the hostname or IP of vCenter. It is recommended to use the IP address here to avoid a lot of unnecessary trouble) and the account and password used for login.

"Virtual machine options": the "Windows.ISO" image file mentioned earlier is used here, and the BE system will call this ISO image file during the conversion process.

Other configurations can be ignored and left by default.

In addition: when the job is completed and successful, the converted virtual machine may need 1 or 2 system restart operations to be used normally, because the system needs to install or reload the VMware Tools plug-in and hardware drivers.

Windows Server 2003, Windows Server 2008, Windows Server 2008 R2 and Windows7 based on Hyper-V were tested successfully.

After the configuration is completed, the conversion work can be completed by running it directly as needed.

Signature of the sword casting team:

[director] Twelve Spring and Autumn period, 3483099@qq.com

[Master] Godao is not green, han169@126.com

[developed by Java] Rain egret, 3436911940q.com; Siqi Junhui, qiangzhang1227@163.com; Little Prince, 545106057Jingq.com; Mountain Patrol, 840260821@qq.com

[VS development] Bean point, 2268800211@qq.com

[system test] asked the earth mirror, 847071279 dust and freedom, 695187655@qq.com

[big data] Desert Oasis, caozhipan@126.com; Zhangsan Province, 570417591@qq.com

[network] Night Lone Star, 11297761@qq.com

[system operation] Sanshi, 261453882 ordinary qq.com; ordinary freak, 591169003@qq.com

[disaster recovery backup] autumn rain, 18568921@qq.com

[security] secrecy, you know.

Original author: autumn Rain

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.