Migration from VMware: Difference between revisions
From Xen
Jump to navigationJump to search
Rcpavlicek (talk | contribs) |
Rcpavlicek (talk | contribs) |
||
Line 14: | Line 14: | ||
</pre> |
</pre> |
||
* In the case above, the file format is <b>raw</b>, so it needs no conversion. Just rename the file to ".raw". However, most of the time, that will not be the case. You will need to use qemu-img to do the conversion. |
* In the case above, the file format is <b>raw</b>, so it needs no conversion. Just rename the file to ".raw". However, most of the time, that will not be the case. You will need to use <b>qemu-img</b> to do the conversion. |
||
<pre> |
<pre> |
||
# qemu-img convert vm1.vmdk -O raw /volumes/vm1/vm1.img |
# qemu-img convert vm1.vmdk -O raw /volumes/vm1/vm1.img |
Revision as of 01:02, 11 January 2015
As time passes, we are finding more and more people interested in migrating to Xen Project from VMware. The reasons for this migration include cost reduction and increased flexibility in cloud orchestration.
Introduced in the 4.5 release, Xen Project now includes the ability to use VMware VMDK files natively to ease migration. For maximum performance, it is advisable to actually translate the VM files into a raw format. But this step can be delayed, if needed, to facilitate migration.
Disk Conversion
- Halt the VMware VM. Examine the type of file used by the VM:
# qemu-img info vm1.vmdk image: vm1.vmdk file format: raw virtual size: 23G disk size: 23G
- In the case above, the file format is raw, so it needs no conversion. Just rename the file to ".raw". However, most of the time, that will not be the case. You will need to use qemu-img to do the conversion.
# qemu-img convert vm1.vmdk -O raw /volumes/vm1/vm1.img
- Create an appropriate Xen Project VM configuration file in /etc/xen/vm1, with a line specifying the converted file as disk:
disk = [ ‘file:/volumes/vm1/vm1.img,hda,w’ ]
- Just boot and go!