{"id":61401,"date":"2024-06-11T09:00:57","date_gmt":"2024-06-11T07:00:57","guid":{"rendered":"https:\/\/nolabnoparty.com\/?p=61401"},"modified":"2024-06-12T08:52:13","modified_gmt":"2024-06-12T06:52:13","slug":"proxmox-import-vmware-vms","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/proxmox-import-vmware-vms\/","title":{"rendered":"Proxmox: import VMware VMs"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-62496 size-full\" title=\"proxmox-import-vmware-vms-01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/proxmox-import-vmware-vms-01.jpg\" alt=\"proxmox-import-vmware-vms-01\" width=\"602\" height=\"202\" \/><\/p>\n<p>To simplify the migration of workloads from VMware vSphere to Proxmox <strong>avoiding complicated procedures<\/strong>, <a href=\"https:\/\/www.proxmox.com\/en\/downloads\" target=\"_blank\" rel=\"noopener\">latest Proxmox<\/a> release provides an integrated tool to easily import VMware VMs.<\/p>\n<p>The tool works well and does what it is supposed to do. There are for sure margins of improvements especially to perform massive imports from complex VMware infrastructures.<!--more--><\/p>\n<p>&nbsp;<\/p>\n<h2>Import VMware VMs<\/h2>\n<p>Using a supported browser, login to a <a href=\"https:\/\/nolabnoparty.com\/en\/proxmox-configure-high-availability-ha\/\">Proxmox<\/a> node by entering the correct credentials then click <strong>Login<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62498 size-full\" title=\"proxmox-import-vmware-vms-02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/proxmox-import-vmware-vms-02.jpg\" alt=\"proxmox-import-vmware-vms-02\" width=\"402\" height=\"198\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Add a No-Subscription Repository<\/h4>\n<p>To <strong>update Proxmox<\/strong> or to <strong>add new features<\/strong> using default repositories, you need a <strong>commercial subscription<\/strong>.\u00a0If you have a regular subscription, you can skip these steps.<\/p>\n<p>From the first node of your <a href=\"https:\/\/nolabnoparty.com\/en\/install-a-nested-proxmox-in-vmware\/\">Proxmox<\/a> infrastructure, access the <strong>Repositories<\/strong> section and click <strong>Add<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62500 size-large\" title=\"proxmox-import-vmware-vms-03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/proxmox-import-vmware-vms-03-600x305.jpg\" alt=\"proxmox-import-vmware-vms-03\" width=\"600\" height=\"305\" \/><\/p>\n<p>If you don't have any subscription is available, select <strong>No-Subscription<\/strong> from the <strong>Repository<\/strong> drop-down menu and click <strong>OK<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62502 size-large\" title=\"proxmox-import-vmware-vms-04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/proxmox-import-vmware-vms-04-600x289.jpg\" alt=\"proxmox-import-vmware-vms-04\" width=\"600\" height=\"289\" \/><\/p>\n<p>The new repository has been added to the node. Now we need to <strong>disable the Enterprise components<\/strong> because without a regular subscription you will receive a warning and the upgrade <strong>procedure will fail<\/strong>. Select the <em>enterprise<\/em> <strong>Components<\/strong> and click <strong>Disable<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62504 size-large\" title=\"proxmox-import-vmware-vms-05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/proxmox-import-vmware-vms-05-600x209.jpg\" alt=\"proxmox-import-vmware-vms-05\" width=\"600\" height=\"209\" \/><\/p>\n<p>This article has been written for\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/\" target=\"_blank\" rel=\"noopener noreferrer\">StarWind blog<\/a>\u00a0and can be found in\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/proxmox-import-vmware-vms\" target=\"_blank\" rel=\"noopener\">this page<\/a>. It covers the full procedure to <strong>import VMware VMs into Proxmox<\/strong>.<\/p>\n<p>&nbsp;<\/p>\n<h2>Test the imported VM<\/h2>\n<p>Access the Proxmox node where the VM has been imported, right click the VM and select <strong>Start<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62506 size-large\" title=\"proxmox-import-vmware-vms-06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/proxmox-import-vmware-vms-06-600x408.jpg\" alt=\"proxmox-import-vmware-vms-06\" width=\"600\" height=\"408\" \/><\/p>\n<p>If everything works as expected, you should see in the Proxmox <strong>Console<\/strong> the main screen of the imported VM (Windows machine in the example). Keep in mind the source <strong>VM is not deleted<\/strong> from VMware infrastructure.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-62508 size-large\" title=\"proxmox-import-vmware-vms-07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2024\/05\/proxmox-import-vmware-vms-07-600x294.jpg\" alt=\"proxmox-import-vmware-vms-07\" width=\"600\" height=\"294\" \/><\/p>\n<p>This new feature is very useful and helps to <strong>perform a fast migration<\/strong> from a VMware vSphere environment to Proxmox. Of course the tool can be enhanced by adding for example the direct import from the vCenter Server instead of mapping single hosts. Proxmox solution is definitively interesting and worth to be tested.<\/p>\n<p>Read the\u00a0<a href=\"https:\/\/www.starwindsoftware.com\/blog\/proxmox-import-vmware-vms\" target=\"_blank\" rel=\"noopener\">full article<\/a>\u00a0on StarWind blog.<\/p>\n<p><img decoding=\"async\" title=\"signature\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"signature\" \/><\/p>\n","protected":false},"excerpt":{"rendered":"<p>To simplify the migration of workloads from VMware vSphere to Proxmox avoiding complicated procedures, latest Proxmox release provides an integrated tool to easily import VMware VMs. The tool works well and does what it is supposed to do. There are for sure margins of improvements especially to perform massive imports from complex VMware infrastructures.<\/p>\n","protected":false},"author":3,"featured_media":62496,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"linkedin_93tdZWzMZc_93tdZWzMZc":"","facebook_2879994398731222_17841400390232720":"","twitter_113568041_113568041":"","mastodon_115463926174894442_115463926174894442":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[2798],"tags":[2838,2795,1676,699],"class_list":["post-61401","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-proxmox-en","tag-import-en","tag-proxmox","tag-virtualization","tag-vmware-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/61401","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=61401"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/61401\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/62496"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=61401"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=61401"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=61401"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}