Having migrated many servers to proxmox so far I applaud the new tools

We have been using Proxmox+Ceph in production for over 7 years now. While the older versions were definitely a touch unstable everything 6 and up seems to work perfectly alright. We're in the process of migrating to a new 9-node cluster and right now it's running smoothly.

Great video and you're absolutely correct about about the loss of skills in VMWare over time due to people not being able to play with stuff at home.

Well done, and a great understanding of who and who will not migrate from vmware...and the reasons for doing so. But I will tell you, large corporate environments? We are looking, because while immediately there are no plans, we are definately risk averse and broadcom is a risk. If enough companies start offering support? I expect proxmox will grow as an alternative. Right now most of the companies that move will go to nutanix or microsoft....both of which are costly, but have good support structure in place.

A really nice video by a very, very knowledgeable man. This VMware conversion utility will encourage small companies to move to Proxmox because it will be relatively easy. One question, do the easy migrations work with all recent versions of ESXi 5, 6, 7 and 8?

@ElectronicsWizardry

2 ай бұрын

Proxmox says they have tested this tool with esxi 6.5 and onwards. Earlier versions may work but I believe they have also gone eol a bit ago so I hope not too many companies are still running the older version.

@allanzfs

2 ай бұрын

You would be surprised. I run into many instances of versions 6.0 and they like it, but they like free better.

Thank you.

11:21 I see one of the config values pulled by the Proxmox import process is the SMBIOS UUID, seen as smbios1 in the video. Since by default it copies the MAC address of the network interface and the SMBIOS UUID, it would be interesting to see how Windows Activation reacts to booting on another hypervisor after migration with those values, if it asks for reactivation or not. I'm assuming its still will ask for activation, even with CPU set as "host"

@ElectronicsWizardry

Ай бұрын

Windows activation is a important point that I didn't test in this video, so I'm not really sure what would happen here. From what I understand with Windows server licensing is its often tied to the hypervisor, so even if a VM says its activated after a migration it may not be licensed correctly, so check what the license says to be sure.

@nelsone.hernandez6654

Ай бұрын

@@ElectronicsWizardry Thank you for your response. Yes, a hypervisor is like the motherboard of a VM, so that’s why I’m expecting reactivation. Those running Windows Server with a volume license should have no issues (it should activate again) unless the key has been activated so many times

Awesome video. Know of an esay way to go from XCP-NG to proxmox other than what is already posted on the forums?

@ElectronicsWizardry

2 ай бұрын

I don’t know of a super easy xcp-ng migration tool like this. You’re probably going to have to manually copy over all the virtual disks and recreate the config. You could make a script but unless you have hundreds or thousands of VMs I doubt a script is saving you time.

Can you choose what storage the VMs get migrated to? I feel like I've missed something.

Have you tried vcenter? I tried to move it to synology vmm but it had like 14 vdisks or partitions way more than synology would support

Im curious how it would handle an older Windows like 2008 or even 2003 since they historically have caused alot of boot errors on KVM without the virtio drivers

If you “needed” a menu to get this done… You do have bigger problems.