November 28, 2010 at 00:45migration of physical Linux servers to the virtual environment of the Microsoft Hyper-V hypervisor
Everything is ambiguous in the scheme of migration of physical Linux servers to the virtual environment of the Microsoft Hyper-V hypervisor, however, without trying to speak clearly about this, it is difficult.
In the continuation of “Sluggish Attempts at Linux P2V Conversion for Hyper-V” (Andrei Ivashentseva, http://bit.ly/hzaV6L ). There is no single solution on the Internet for such a migration; the main options have been known for a long time:
Hyper V and System Center Virtual Machine Manager are not able to migrate Linux P2V, which does not prevent them from successfully virtualizing it; there are hyper-v integration tools for Linux - LinuxIC.
The problem that I was trying to solve was to free the legacy equipment on which Oracle databases are spinning, all this is spinning under Fedora, and transfer the virtual machines to the Hyper-V hypervisor that we use.
I followed the famous path number one on my list. Migration consists of the following steps, it is assumed that you already have Windows Server 2008 installed with Hyper-V and System Center Virtual Machine Manager:
Vmware Converter is needed only during the migration to Vmware, it’s good if there is a high-speed Ethernet adapter. You can immediately try the possibility of migrating your Linux server by starting the migration and specifying data with root access and clicking View source details.
From this moment you will understand that for migration you need Vmware ESXi, it is free to download and use. There is also a 60-day period for managing it through vSphere Client. I put on the first PC with a processor that supports virtualization hardware. There is no point in describing the installation of Vmware ESXi, there is nothing there that would cause difficulties (next - next –next). Just in case, here is a link to the installation guide (http://bit.ly/frcqdD). The only thing to consider is: there should be enough space on the hard disk for the data of your migrated servers. You will also need to configure remote SSH access, as indicated in the screenshot. Wizard Vmware Converter starts p2v migration, it took me about an hour with 140 Gb of data from one of the servers.
The next step is to download, for example, Winscp, in order to download the necessary files via SSH after the migration is completed. In the System Center Virtual Machine Manager, add the folder with the image from Vmware, all the files that I pulled from Vmware ESXi via SSH. After adding everything, we create the task of migrating V2V to SCVMM. Again, we expect, since I was deploying the machine on a server that is only a Hyper-V host, and SCVMM was on a separate machine - the process took about an hour and a half. As a result, I got a working machine under Linux Fedora under Hyper-V. I did not need to integrate Hyper-V tools, the machines will sleep and wait for an hour when they are needed. In addition, I can say that you can do without SCVMM, a free tool: VMDK2VHD ( http://bit.ly/i2IuaT )
In the continuation of “Sluggish Attempts at Linux P2V Conversion for Hyper-V” (Andrei Ivashentseva, http://bit.ly/hzaV6L ). There is no single solution on the Internet for such a migration; the main options have been known for a long time:
- Linux -> Vmware Converter 4 -> Vmware ESX -> VMDK2VHD -> Hyper-V -> Install LinuxIC
- Alternative solutions:
- PlateSpin® Migrate (owned by Novell, formerly Invirtus Enterprise VM Converter),
- Quest® vConverter (formerly Vizioncore),
- Citrix XenConvert (but you can’t do without intermediate migration to Vmware here).
- Installing Linux directly into Hyper-V and migrating data and configuration with Linux is also very interesting.
- Perhaps there is something else, I will be glad if someone share this knowledge.
Hyper V and System Center Virtual Machine Manager are not able to migrate Linux P2V, which does not prevent them from successfully virtualizing it; there are hyper-v integration tools for Linux - LinuxIC.
The problem that I was trying to solve was to free the legacy equipment on which Oracle databases are spinning, all this is spinning under Fedora, and transfer the virtual machines to the Hyper-V hypervisor that we use.
I followed the famous path number one on my list. Migration consists of the following steps, it is assumed that you already have Windows Server 2008 installed with Hyper-V and System Center Virtual Machine Manager:
- Install Vmware Converter on a Windows machine.
- Install Vmware ESXi. Configure SSH access.
- The migration process in ESXi.
- Copy VMDK from ESXi to Hyper-V Server via SSH with Winscp.
- Adding a folder with vmware files to the SCVMM library, and converting V2V (VMDK to VHD using the SCVMM Wizard).
- Checking and running your Linux server on Hyper-V.
- LinuxIC component integration.
Vmware Converter is needed only during the migration to Vmware, it’s good if there is a high-speed Ethernet adapter. You can immediately try the possibility of migrating your Linux server by starting the migration and specifying data with root access and clicking View source details.
From this moment you will understand that for migration you need Vmware ESXi, it is free to download and use. There is also a 60-day period for managing it through vSphere Client. I put on the first PC with a processor that supports virtualization hardware. There is no point in describing the installation of Vmware ESXi, there is nothing there that would cause difficulties (next - next –next). Just in case, here is a link to the installation guide (http://bit.ly/frcqdD). The only thing to consider is: there should be enough space on the hard disk for the data of your migrated servers. You will also need to configure remote SSH access, as indicated in the screenshot. Wizard Vmware Converter starts p2v migration, it took me about an hour with 140 Gb of data from one of the servers.
The next step is to download, for example, Winscp, in order to download the necessary files via SSH after the migration is completed. In the System Center Virtual Machine Manager, add the folder with the image from Vmware, all the files that I pulled from Vmware ESXi via SSH. After adding everything, we create the task of migrating V2V to SCVMM. Again, we expect, since I was deploying the machine on a server that is only a Hyper-V host, and SCVMM was on a separate machine - the process took about an hour and a half. As a result, I got a working machine under Linux Fedora under Hyper-V. I did not need to integrate Hyper-V tools, the machines will sleep and wait for an hour when they are needed. In addition, I can say that you can do without SCVMM, a free tool: VMDK2VHD ( http://bit.ly/i2IuaT )
