Very useful tutorial. I agree with you that this is most welcome from Proxmox. In our work environment we have the added issue of "fixed IPs" allocated by the DHCP server, so we have to first change the VMWare MAC address of the migrated machine that it got from the VMWare host to the new Proxmox host's MAC address. Very quick but the migrated machine will not get an IP unless this is done first.
Shortest downtime that I discovered so far, no matter what disk size the vm has: - make nfs storage available in VMware and proxmox - migrate VMware vm to that storage - change network interfaces of given vm (Linux) - shutdown vm - create vm in proxmox and move vmdks to to that vm - qm rescan on host - start vm - downtime: 2 minutes ;)
I know how to do this using qm disk import but have not seen the qm rescan method before. Can you elaborate on the move vmdks to the vm and qm rescan steps?
Great info! The import tool seems to work great as long as you don't have any spaces in the VM name coming from ESXi. If you do, it's still possible but you need to manually edit the filenames to not have spaces.
Did this last night with a 20GB VM and it took a very long time even with a strong computer and network connection, but it worked flawless. To my surprise it worked on the Free ESXi version, I really assumed that it would only work with the paid version as you need that for features like snapshots/backups. Soon as I get my Proxmox node sorted with network and storage configuration I am looking forward to migrating all my VM's over and shutting down my old ESXi server.
Great video. I've been using the free ESXI in my home lab for many years, and before that, VMWare1 and 2... now I am building a new home lab virtualization server and am on the fence. I have ESXI 8 and a key so can still use that, but it is now a dead end and I have installed PROXMOX on an old desktop just to see what it is like. This video really came in handy, showing me the basic 'get it started and get VMs migrated'. Testing with a test Server 2022 machine right now. There is a lot to learn, PROXMOX appears much more complicated than ESXI and while I won't need to mess with much of it, I don't know yet what I will need to mess with or not... At least now I have an up to date test installation and can play with the migration tool. THANKS!
thankfully, there are thousands of great tutorials on YT about Proxmox, and Proxmox itself is very capable. I’ll add I like Craft Computing and Learn Linux TV.
Although I have no esxi hosts or vm's to migrate, I do appreciate the review; Having migrated and downsized farms before, migration tools are always interesting to a degree; and such tools always seem to improve given time..
Does this migration tool also solve the pain of renamed network interface devices? Under esxi the vmxnet3 adapter would typically be ens192, while within proxmox it would be ens18. Manually migrated VMs always needed a network config file edit to reflect the renamed interface device.
Thanks for the video. What happens to your network interfaces that were configured in VMware? Are those copied and functional on Proxmox (same MACs?) or will you have to reconfigure new interfaces?
My tip: Before migrating the VM, remove VMWARE TOOLS (if installed) on the source VM, shut down the source VM. After that, migrate to PROXMOX and check NIC interfaces, IP addresses, etc.
What about NFS central storage of your VMs, does convert to a new disk file system and required double the storage? Can you just disconnect it from esxi and import without changing locations?
Question for those who already used it. What happens if I have a USB pass through on my esxi image? I have a windows print server that is using a printer connected to USB. Is it going to work on proxmox out of the box as well?
Question: Once you import the VM over, I assume is still available over at the ESXi host? What about networking? What does the import wizard do with networking especially any static IP addresses?
There is one thing that's not mentioned is the Import Wizard can not see the cluster's vSAN. It will only see the local storage that's on the host server. So if you run a vSAN you'll have to move them to host's local storage and then it'll show up for you to import. I think eventually they will add this feature in the future. Right now they have given us a great tool and starting point to get those VMs moved over.
@@julionb87 I've done it via CLI which isn't hard to do. Just tedious and have to keep track of the vms I export out. It's not big of a deal but will be for those with large clusters with thousands of VMs.
@Darkk6969, yes that is a good call out that vSAN is not supported. However, it really just means that you need a traditional VMFS datastore, not necessarily local disks in a physical server. So if the datastore is presented to the ESXi host, this is supported I believe.
Wish this was a thing 2 years ago, had to manually migrate 80+ VM's from esxi to PM for my development labs, not hard to do on the CLI using a 'for' loop, but it was a bit frustrating to get the commands just right to manage the conversion.
congratulations for the great work done, I followed your guide but unfortunately it doesn't work but the system gives me this error create storage failed: failed to spawn fuse mount, process exited with status 65280 (500) what can I check to make the import work? Thanks
I was really hoping the "live migration" option really does live migration :( But well, shouldn't be too much of an issue for small machines with 10Gbps/25Gbps interfaces. Love the video, keep up the good work.
@accrevoke thank you for the comment! I am hopeful there will be more orchestration in the next iterations of the tool. It would be great if it would utilize a snapshot approach and shutdown the VM automatically. Hoping for the next versions :)
Im geting an error and cannot add the esxi storage. Is there some fw rules on esxi thats prvwbting this connection? Theres many rules but i didnt build it.
i am wanting to replace my esxi installation on my server with Proxmox but i have the issue of not having a second machine to move the VMs to first.. can i also just put the files for the VMs on another share and import them from that once proxmox is installed? or should i install esxi on a secondary system like an old pc, move them there, just to move them back to the proxmox then when i installed it?
Minor tweak to ESXi was required, I had to remove the limitation on the number of HTTP threads at ESXi (500 limit) or the initial import/retrieval failed. Simple setting in ESXi -- Config.HostAgent.vmacore.soap.maxSessionCount - changable simply in the WebGUI. (edited to remove question as it was a misconfiguration in my Proxmox due to exploring networking)
Hello Brandon: I have appreciated your content to add a exsi host, can datastores be on the local host IP or does it need to be network based storage, getting the error - create storage failed: failed to spawn fuse mount, process exited with status 65280 (500). Would appreciate any input. Thank You Mark.
Great video! I work for a large Global company, and we are currently looking to move off of vmware. They have just gotten crazy since the Broadcom acquisition, pricing etc. notice that you are applying this to a host. Is there no vcenter like component to Proxmox for centrally managing the environment? Would this need to be an update done to every host in a cluster? Thanks!
Really wish you would have went into reasoning for why you need to also select Quincy or Reef repo. I've looked high and low and cannot figure out what these are for nor the difference. Many other videos don't mention adding them either but rather just "No-Subscription" option only.
This was cool and a great feature given the massive changes over at VMW recently. Hopefully as a next step they will be able to take a snapshot of the ESXi VM then just copy that snap over to ProxMox as an option so it will not be required to shutoff the source VM. QUESTION: are these any optimization that should be performed on the newly imported VM?
odd, everything works up to completing the import operation then it errors out: list vms - select and import...importing...upto the last byte of import then it errors out "TASK ERROR: unable to create VM 102 - cannot import from.... - copy failed"
I had to do a minor tweak to ESXi -- remove the limitation on the number of HTTP threads at ESXi (500 limit) or the initial import/retrieval failed. Simple setting in ESXi -- Config.HostAgent.vmacore.soap.maxSessionCount - changable simply in the WebGUI, no reboot needed of the ESXi host.
10 หลายเดือนก่อน +3
@@kyle15511 I was having problems migrating very heavy VMs, and this helped me solve it. Thank you so much!
Solved by changing MaxSeassion and timeout in ESXI UI to 0. go to: Host - Manage - advanced settings, and set: Config.HostAgent.vmacore.soap.maxSessionCount = 0 Config.HostAgent.vmacore.soap.sessionTimeout = 0
@ tried a few other options and then just set both timeout and session count to 0, and that worked: Config.HostAgent.vmacore.soap.maxSessionCount = 0 Config.HostAgent.vmacore.soap.sessionTimeout = 0
HHi Can I import vmd used on vmware host on ptocmox but not connecto vmware host but mount nfs volume storaged on synology nas and import that data to proxmox host? For me more importrny is the vms data on there hdds images not cofig of vm itself
Great guide, thank you. However, I'm guessing a number of home lab people don't have 2 physical servers to do the migration. Could you run proxmox on VM, do the conversion, install proxmox on the bare metal then import the VMs?
I ran into one unusual bug, after copying the VM’s from ESXI to PVE, as a test, I tried to power back up the ESXI VM’s and they would fail to post, only able to resolve by rebooting the ESXI host
Wow that is strange. Definitely one to report in the Proxmox forums. They would probably like to see some logs from your environment. Definitely curious the underlying issue there.
Same, I am updated to PVE 8.1.10 and made sure to add the Ceph Reef repo and rebooted after all updates but, no ESXi option in storage. /edit: after checking the documentation, I believe you need IOMMU working to use this. My system is older, and I am not using passthrough so I don't care to get IOMMU working to verify but, this might be a reason why you cannot get option to add ESXi as a storage
Thanks for this informative review. I do have one question though: will this also work in a VCenter configuration, for instance in a 2-node cluster? Or do you need to take one of the nodes out of the cluster, migrate a set of VMs there and then do the import to Proxmox? I reacted to the earlier video about virtualization platforms where I mentioned that I was going for XCP-ng with XOA. I have now discovered that this is basically a dead end, because after importing a single host, I couldn't find any way to get the VM to see the virtual disks, even with the OS recovery disk. Also, I have a strong suspicion it imported the wrong guest. The guest hardware checks out, but it looks like the virtual disk XOA chose is for another VM. Finally, I added my NFS ISO store to the XCP-ng host and at first it didn't show any ISOs. Turns out that in and of itself the ISOSR driver does not dive into subdirectories, which IMHO is BS. A working patch for this is available, but so far it has not been merged, apparently for bureacratic reasons. Manually applying the patch works though. XOA is gorgeous, though somewhat unintuitive, but if you're looking for a solution that just works, I'm afraid it needs a bit more work. So I'm going to bite the bullet and install Proxmox again and simply OK the misleading pop-up about not having a valid subscription license.
Turn off the display of your AC while recording. It will remove the annoying flickering behind you. And will improve the video quality. If you also want to improve the audio quality, then just switch it off. On external speakers or a good quality headphone you can hear it in the background.
Can you migrate ESXi VM's like this but using other types of storage as the source, in stead of the ESXi datastore directly? For instance NFS, SMB, iSCSI,...? Say I copy my ESXi VM files onto my NAS, can I then import from the NAS to the Proxmox server? Reason I ask is that I'm looking at migrating at some point but I don't have a spare server on which I can bare-metal install Proxmox. Ideally I would prefer reusing my current server for Proxmox, if need be with some intermediate steps and without a direct migration as is shown in this video (Thank you for the video by the way, very interesting and of course the timing is no coincidence. I have high hopes for the growth of Proxmox now that vSphere is off the table for a lot of people)
@BinaryBlueBull I haven't tested all types of datastores myself. However, I don't think that is possible at this point with the migration wizard. You can manually convert the VMDKs to Proxmox disks though using the more traditional command line approach.
The Hyper-V migration strategy is to nuke it from orbit. Preferably twice, just to make sure it's well and truly migrated (J/k of course, though I've seen a lot of misery in companies that use Hyper-V for anything but a small environment)
One important thing is -no snapshot on ESXI host before clone error:(000001.vmdk': Unsupported reserved bits: 0x0000000000000200 0x0000000000000000 0x00000000000000000x0000000000000000)
@fbifido2 thanks for the comment! Check out my blog post. I didn't cover in the video, but did in the written post here: www.virtualizationhowto.com/2024/03/proxmox-new-import-wizard-for-migrating-vmware-esxi-vms/
@@VirtualizationHowto Hi, thanks. For Windows's one have you tried reverting the disk back to SCSI afterward? SATA tends to offer lower performance compared to SCSI.
@@anthonyholmes113 You'd be amazed! IT WORKED without ANY hiccups or drama. Granted, I had the VM shut down, but it really did work great. This definitely goes into the toolbox for many of the things I'm working on.
Tried this last night works great, I was able to migrate a 150 GB vm with no issues
Very useful tutorial. I agree with you that this is most welcome from Proxmox. In our work environment we have the added issue of "fixed IPs" allocated by the DHCP server, so we have to first change the VMWare MAC address of the migrated machine that it got from the VMWare host to the new Proxmox host's MAC address. Very quick but the migrated machine will not get an IP unless this is done first.
Shortest downtime that I discovered so far, no matter what disk size the vm has:
- make nfs storage available in VMware and proxmox
- migrate VMware vm to that storage
- change network interfaces of given vm (Linux)
- shutdown vm
- create vm in proxmox and move vmdks to to that vm
- qm rescan on host
- start vm
- downtime: 2 minutes ;)
Nfs is your best friend in this scenario.
I know how to do this using qm disk import but have not seen the qm rescan method before. Can you elaborate on the move vmdks to the vm and qm rescan steps?
Great info! The import tool seems to work great as long as you don't have any spaces in the VM name coming from ESXi. If you do, it's still possible but you need to manually edit the filenames to not have spaces.
Did this last night with a 20GB VM and it took a very long time even with a strong computer and network connection, but it worked flawless.
To my surprise it worked on the Free ESXi version, I really assumed that it would only work with the paid version as you need that for features like snapshots/backups.
Soon as I get my Proxmox node sorted with network and storage configuration I am looking forward to migrating all my VM's over and shutting down my old ESXi server.
Great video. I've been using the free ESXI in my home lab for many years, and before that, VMWare1 and 2... now I am building a new home lab virtualization server and am on the fence. I have ESXI 8 and a key so can still use that, but it is now a dead end and I have installed PROXMOX on an old desktop just to see what it is like. This video really came in handy, showing me the basic 'get it started and get VMs migrated'. Testing with a test Server 2022 machine right now. There is a lot to learn, PROXMOX appears much more complicated than ESXI and while I won't need to mess with much of it, I don't know yet what I will need to mess with or not... At least now I have an up to date test installation and can play with the migration tool. THANKS!
Awesome keep us updated on the project 👍
thankfully, there are thousands of great tutorials on YT about Proxmox, and Proxmox itself is very capable.
I’ll add I like Craft Computing and Learn Linux TV.
Although I have no esxi hosts or vm's to migrate, I do appreciate the review; Having migrated and downsized farms before, migration tools are always interesting to a degree; and such tools always seem to improve given time..
Thank you for the detailed guide. With the raising cost of vSphere, I hope Proxmox gets more and more corporate footprint.
Does this migration tool also solve the pain of renamed network interface devices? Under esxi the vmxnet3 adapter would typically be ens192, while within proxmox it would be ens18. Manually migrated VMs always needed a network config file edit to reflect the renamed interface device.
Awsome!! Really great Video!!
Thanks for the video. What happens to your network interfaces that were configured in VMware? Are those copied and functional on Proxmox (same MACs?) or will you have to reconfigure new interfaces?
Are the steps the same if the VM is a Windows server or is there any further steps?
My tip: Before migrating the VM, remove VMWARE TOOLS (if installed) on the source VM, shut down the source VM. After that, migrate to PROXMOX and check NIC interfaces, IP addresses, etc.
You don’t have to just import over and Start up good to go.
You might need the windows drivers installing too. Sep .ISO file for those
Thanks for that, the migration works like a charm 🙂
in the process of moving to low power servers and this will help as i just got proxmox running with one vm i copied over so far
Brandon, can you automate this with something like Terraform or Ansible? Or is it a one by one sort of proposition?
thank you for comprehensive explanation
Good video Brandon !
Once Veeam adds full support for Proxmox they I will be jumping board!
PBS is superior to veeam in every way, for proxmox.
What about NFS central storage of your VMs, does convert to a new disk file system and required double the storage? Can you just disconnect it from esxi and import without changing locations?
Question for those who already used it. What happens if I have a USB pass through on my esxi image? I have a windows print server that is using a printer connected to USB. Is it going to work on proxmox out of the box as well?
Question: Once you import the VM over, I assume is still available over at the ESXi host? What about networking? What does the import wizard do with networking especially any static IP addresses?
There is one thing that's not mentioned is the Import Wizard can not see the cluster's vSAN. It will only see the local storage that's on the host server. So if you run a vSAN you'll have to move them to host's local storage and then it'll show up for you to import. I think eventually they will add this feature in the future. Right now they have given us a great tool and starting point to get those VMs moved over.
Good call out. That makes it a no for me, until they support it.
@@julionb87 I've done it via CLI which isn't hard to do. Just tedious and have to keep track of the vms I export out. It's not big of a deal but will be for those with large clusters with thousands of VMs.
@Darkk6969, yes that is a good call out that vSAN is not supported. However, it really just means that you need a traditional VMFS datastore, not necessarily local disks in a physical server. So if the datastore is presented to the ESXi host, this is supported I believe.
@@VirtualizationHowto Yes you're correct about the traditional VMFS datastore which will work fine with the import tool. Good clarification on that.
Def need the vSAN option for me. No local disk to cater for the larger vms
Thank you, exactly what i needed.
Wish this was a thing 2 years ago, had to manually migrate 80+ VM's from esxi to PM for my development labs, not hard to do on the CLI using a 'for' loop, but it was a bit frustrating to get the commands just right to manage the conversion.
congratulations for the great work done, I followed your guide but unfortunately it doesn't work but the system gives me this error
create storage failed: failed to spawn fuse mount, process exited with status 65280 (500) what can I check to make the import work? Thanks
I was really hoping the "live migration" option really does live migration :(
But well, shouldn't be too much of an issue for small machines with 10Gbps/25Gbps interfaces.
Love the video, keep up the good work.
@accrevoke thank you for the comment! I am hopeful there will be more orchestration in the next iterations of the tool. It would be great if it would utilize a snapshot approach and shutdown the VM automatically. Hoping for the next versions :)
Im geting an error and cannot add the esxi storage. Is there some fw rules on esxi thats prvwbting this connection? Theres many rules but i didnt build it.
Eureca, cool 💪🏾
If only they had done this earlier. It was a pain to move 30 VMs.
30 xD imagin migrating 200vm's
i am wanting to replace my esxi installation on my server with Proxmox but i have the issue of not having a second machine to move the VMs to first.. can i also just put the files for the VMs on another share and import them from that once proxmox is installed? or should i install esxi on a secondary system like an old pc, move them there, just to move them back to the proxmox then when i installed it?
Am patiently waiting for veeam to release a patch to support proxmox.
Cant connect to esxi across the continent since no public ip, but is there an export option? noticed .vmx is what the import side needs if I am right.
Minor tweak to ESXi was required, I had to remove the limitation on the number of HTTP threads at ESXi (500 limit) or the initial import/retrieval failed. Simple setting in ESXi -- Config.HostAgent.vmacore.soap.maxSessionCount - changable simply in the WebGUI.
(edited to remove question as it was a misconfiguration in my Proxmox due to exploring networking)
Would you recommend proxmox a full alternative for vmware vsphere? Taking in consideration HCI features / limitations ?
Hello Brandon: I have appreciated your content to add a exsi host, can datastores be on the local host IP or does it need to be network based storage, getting the error -
create storage failed: failed to spawn fuse mount, process exited with status 65280 (500). Would appreciate any input. Thank You Mark.
Great video! I work for a large Global company, and we are currently looking to move off of vmware. They have just gotten crazy since the Broadcom acquisition, pricing etc. notice that you are applying this to a host. Is there no vcenter like component to Proxmox for centrally managing the environment? Would this need to be an update done to every host in a cluster? Thanks!
Thank you for your video. I tried Proxmox today with version 8.2.2 and I can see it has already ESXi option in the Storage/Add ?
Really wish you would have went into reasoning for why you need to also select Quincy or Reef repo. I've looked high and low and cannot figure out what these are for nor the difference. Many other videos don't mention adding them either but rather just "No-Subscription" option only.
dzięki za film naprawdę przydatna opcja
This was cool and a great feature given the massive changes over at VMW recently. Hopefully as a next step they will be able to take a snapshot of the ESXi VM then just copy that snap over to ProxMox as an option so it will not be required to shutoff the source VM. QUESTION: are these any optimization that should be performed on the newly imported VM?
can be more detailed with thin or thik format, and how to select the second network card 10gbs to make the import process faster
odd, everything works up to completing the import operation then it errors out: list vms - select and import...importing...upto the last byte of import then it errors out "TASK ERROR: unable to create VM 102 - cannot import from.... - copy failed"
I had to do a minor tweak to ESXi -- remove the limitation on the number of HTTP threads at ESXi (500 limit) or the initial import/retrieval failed. Simple setting in ESXi -- Config.HostAgent.vmacore.soap.maxSessionCount - changable simply in the WebGUI, no reboot needed of the ESXi host.
@@kyle15511 I was having problems migrating very heavy VMs, and this helped me solve it. Thank you so much!
@@kyle15511 mine was already set to 500..increased to 1000, but still always get same error :(
Solved by changing MaxSeassion and timeout in ESXI UI to 0. go to: Host - Manage - advanced settings, and set:
Config.HostAgent.vmacore.soap.maxSessionCount = 0
Config.HostAgent.vmacore.soap.sessionTimeout = 0
@ tried a few other options and then just set both timeout and session count to 0, and that worked:
Config.HostAgent.vmacore.soap.maxSessionCount = 0
Config.HostAgent.vmacore.soap.sessionTimeout = 0
HHi Can I import vmd used on vmware host on ptocmox but not connecto vmware host but mount nfs volume storaged on synology nas and import that data to proxmox host?
For me more importrny is the vms data on there hdds images not cofig of vm itself
Great guide, thank you. However, I'm guessing a number of home lab people don't have 2 physical servers to do the migration.
Could you run proxmox on VM, do the conversion, install proxmox on the bare metal then import the VMs?
Dude, what an awesome feature! Do you think this is similar to Vmotion?
Which esxi versions does it work with... 5, 6, 7 and 8? Or just 8?
I ran into one unusual bug, after copying the VM’s from ESXI to PVE, as a test, I tried to power back up the ESXI VM’s and they would fail to post, only able to resolve by rebooting the ESXI host
Wow that is strange. Definitely one to report in the Proxmox forums. They would probably like to see some logs from your environment. Definitely curious the underlying issue there.
@@VirtualizationHowto it felt a bit like a locked file issue or similar
So Good !
done updating, and wizard already installed. but esxi option not showing on Storage. anyone else experience same as me? how to fix this? thanks
A reboot did the trick for me 👍
Same, I am updated to PVE 8.1.10 and made sure to add the Ceph Reef repo and rebooted after all updates but, no ESXi option in storage. /edit: after checking the documentation, I believe you need IOMMU working to use this. My system is older, and I am not using passthrough so I don't care to get IOMMU working to verify but, this might be a reason why you cannot get option to add ESXi as a storage
ist the VM on VM ware still existing after migration to proxmox ? its a copy or a move ?
Please Can I do a copy of Vm from Esxi to Proxmox without deleating it from the source ?
Thanks for this informative review. I do have one question though: will this also work in a VCenter configuration, for instance in a 2-node cluster? Or do you need to take one of the nodes out of the cluster, migrate a set of VMs there and then do the import to Proxmox?
I reacted to the earlier video about virtualization platforms where I mentioned that I was going for XCP-ng with XOA. I have now discovered that this is basically a dead end, because after importing a single host, I couldn't find any way to get the VM to see the virtual disks, even with the OS recovery disk. Also, I have a strong suspicion it imported the wrong guest. The guest hardware checks out, but it looks like the virtual disk XOA chose is for another VM. Finally, I added my NFS ISO store to the XCP-ng host and at first it didn't show any ISOs. Turns out that in and of itself the ISOSR driver does not dive into subdirectories, which IMHO is BS. A working patch for this is available, but so far it has not been merged, apparently for bureacratic reasons. Manually applying the patch works though.
XOA is gorgeous, though somewhat unintuitive, but if you're looking for a solution that just works, I'm afraid it needs a bit more work.
So I'm going to bite the bullet and install Proxmox again and simply OK the misleading pop-up about not having a valid subscription license.
I can answer this question myself. In the meantime I've been able to successfully import VMs from vcenter using the esxi import tool in Proxmox.
Turn off the display of your AC while recording. It will remove the annoying flickering behind you. And will improve the video quality. If you also want to improve the audio quality, then just switch it off. On external speakers or a good quality headphone you can hear it in the background.
Can you migrate ESXi VM's like this but using other types of storage as the source, in stead of the ESXi datastore directly? For instance NFS, SMB, iSCSI,...? Say I copy my ESXi VM files onto my NAS, can I then import from the NAS to the Proxmox server? Reason I ask is that I'm looking at migrating at some point but I don't have a spare server on which I can bare-metal install Proxmox. Ideally I would prefer reusing my current server for Proxmox, if need be with some intermediate steps and without a direct migration as is shown in this video
(Thank you for the video by the way, very interesting and of course the timing is no coincidence. I have high hopes for the growth of Proxmox now that vSphere is off the table for a lot of people)
@BinaryBlueBull I haven't tested all types of datastores myself. However, I don't think that is possible at this point with the migration wizard. You can manually convert the VMDKs to Proxmox disks though using the more traditional command line approach.
非常好，又多一个可以迁移的方案
Does this work with VmWare workstation?
Where is the Hyper-V Import Wizard! =)
The Hyper-V migration strategy is to nuke it from orbit. Preferably twice, just to make sure it's well and truly migrated
(J/k of course, though I've seen a lot of misery in companies that use Hyper-V for anything but a small environment)
Nice
Has anyone migrated vcenter?
COOL
Noice!!!...
One important thing is -no snapshot on ESXI host before clone error:(000001.vmdk': Unsupported reserved bits: 0x0000000000000200 0x0000000000000000 0x00000000000000000x0000000000000000)
Remove first snapshots, then clone VM.
since you did an import of linux, and test the result. Next should have been a Windows 10/11 & server 2019/2022 VM
@fbifido2 thanks for the comment! Check out my blog post. I didn't cover in the video, but did in the written post here: www.virtualizationhowto.com/2024/03/proxmox-new-import-wizard-for-migrating-vmware-esxi-vms/
@@VirtualizationHowto Hi, thanks. For Windows's one have you tried reverting the disk back to SCSI afterward? SATA tends to offer lower performance compared to SCSI.
Companies will move 80% easily. The 20% will take a little longer.
Hehehe i just read "vmware esxit" hehehe
'Promo sm' 👌
Great..I migrated all my VMs from Esxi to Proxmox with Clonezilla source and dest 😂😅
570 Aaliyah Mountain
Thank you fpr this video. But a Linux VM is not a challenge. Migrate an Exchange or MS SQL Server.
I'll be testing in my lab with a 20TB SQL Server in the next hour. I'll post here if there's any issues with that!
@@davidkleegeek How did the migration go?
@@anthonyholmes113 You'd be amazed! IT WORKED without ANY hiccups or drama. Granted, I had the VM shut down, but it really did work great. This definitely goes into the toolbox for many of the things I'm working on.