Migration from VMware: Difference between revisions
From Xen
Jump to navigationJump to search
Rcpavlicek (talk | contribs) (Created page with "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 flexib…") |
Rcpavlicek (talk | contribs) No edit summary |
||
| Line 1: | Line 1: | ||
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. |
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. |
|||
Revision as of 00:40, 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.
