Transferring “physical” or MS Virtual PC to XenServer
This narrative is academic and possibly of no practical value, however “Howto ...”
The source data for converting to the XVA ( XenServer Virtual Appliance ) format will be VHD ( Virtual Hard Disk ) and VMC ( Virtual Machine Config ). Let's make a virtual machine out of a physical machine:
Consider the option when we have an abstract PC with Microsoft OS installed. To get an image in the VHD format, we use the utility Disk2Vhd ( http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx ). The result of this utility will be a disk image, which we will be able to use as a disk for MS Virtual PC (Server). To convert to the XVA format, we need a virtual machine configuration file - there are two options:
1) create your own - using MS Virtual Server 2005 R2 (you can download it for free from MS)
2) manually edit, for example, my changing the amount of RAM, the number of processors and the path to the VHD ("svn3.vhd").
Note that the generated VHD file (in my case, the size of 11GB) will carry a physical hard disk on which the system was deployed, say, 250GB. Since I was not pleased with the prospect of giving such sizes on a server for a virtual machine, the following steps were taken:
')
1) before converting HDD to VHD artificially with the help (Acronis Disk Director Suite, Partition Magic, etc., etc. of the program) of the partition manager (volume), the size of the volume on which the system was deployed was changed from 250GB to 40GB (40GB - I just planned to give virtualke).
2) using the VHD Resizer utility ( http://vmtoolkit.com/files/folders/converters/entry87.aspx ), the VHD Dynamic 250GB format was converted to VHD Fixed 40GB (you pay attention to the fact that you will be doing all these operations, there was an adequate supply of space).
Now that we have VHD (the right format) and VMC, we’ll start converting to the XVA format using the v2xva.exe utility ( http://forums.citrix.com/servlet/JiveServlet/download/511-241595-1363444-26313/v2xva-1.3. 4.zip ):
v2xva / verbose: Loud / config: "c: \ path to the configuration file of the virtual machine \ myvirtpc.vmc" / output: "path to the folder where the virus will form"
The last step, “Importing VMs” from Citrix XenCenter, is choosing the “XenServer Virtual Appliance Version 1 (ova.xml)” file type.
Ps. The resulting virtual machine has a huge disadvantage in that the size of Storage (vdi_hda) can only be changed in a big way: (
The source data for converting to the XVA ( XenServer Virtual Appliance ) format will be VHD ( Virtual Hard Disk ) and VMC ( Virtual Machine Config ). Let's make a virtual machine out of a physical machine:
Consider the option when we have an abstract PC with Microsoft OS installed. To get an image in the VHD format, we use the utility Disk2Vhd ( http://technet.microsoft.com/en-us/sysinternals/ee656415.aspx ). The result of this utility will be a disk image, which we will be able to use as a disk for MS Virtual PC (Server). To convert to the XVA format, we need a virtual machine configuration file - there are two options:
1) create your own - using MS Virtual Server 2005 R2 (you can download it for free from MS)
2) manually edit, for example, my changing the amount of RAM, the number of processors and the path to the VHD ("svn3.vhd").
Note that the generated VHD file (in my case, the size of 11GB) will carry a physical hard disk on which the system was deployed, say, 250GB. Since I was not pleased with the prospect of giving such sizes on a server for a virtual machine, the following steps were taken:
')
1) before converting HDD to VHD artificially with the help (Acronis Disk Director Suite, Partition Magic, etc., etc. of the program) of the partition manager (volume), the size of the volume on which the system was deployed was changed from 250GB to 40GB (40GB - I just planned to give virtualke).
2) using the VHD Resizer utility ( http://vmtoolkit.com/files/folders/converters/entry87.aspx ), the VHD Dynamic 250GB format was converted to VHD Fixed 40GB (you pay attention to the fact that you will be doing all these operations, there was an adequate supply of space).
Now that we have VHD (the right format) and VMC, we’ll start converting to the XVA format using the v2xva.exe utility ( http://forums.citrix.com/servlet/JiveServlet/download/511-241595-1363444-26313/v2xva-1.3. 4.zip ):
v2xva / verbose: Loud / config: "c: \ path to the configuration file of the virtual machine \ myvirtpc.vmc" / output: "path to the folder where the virus will form"
The last step, “Importing VMs” from Citrix XenCenter, is choosing the “XenServer Virtual Appliance Version 1 (ova.xml)” file type.
Ps. The resulting virtual machine has a huge disadvantage in that the size of Storage (vdi_hda) can only be changed in a big way: (
Source: https://habr.com/ru/post/91411/
All Articles