2003R2 image Live Migration Help

[dal.01]

Hello. I have used Proxmox on and off in personal use and have loved it for what it has done for me in that regards. My question is this.

I have done a live migration of a Windows Server 2003 R2 to a KVM container in Proxmox. I followed the steps that was in the wiki for the Physical (running) server to Proxmox VE (KVM) using SelfImage. Everything seems to have gone alright for me, except for a couple of errors that then resulted in chdsk running. After bootup, I was able to log into the server but was greeted with a message saying that my version of windows in not valid? I thought doing a live migration ment that everything went over as is?

I am redoing the server but cannot afford to have any downtime, thus this process of cloning so people have something to log into.

My question is, have I done something wrong, or is it something that I am going to have to call M$ on?

 

[mmenaz]

You have misunderstood what a "live migration" is. You have done a physical to virtual migration (p2v). Since the "virtual hardware" is different from the physical one (different chipset, mac address of the nic, nic types, etc.) and since M$ "copy protection" checks for those differences to detect if you are running the OS in a different hardware, the copy protection has been triggered. Probably is just a matter of re-registering the product or call M$ and explain the situation asking for a new activation.
Live migration is when you have a KVM VM (KVM is not a "container", OpenVZ are "containers", KVM is full virtualization) and move from one clustered server to another. Is "live" since, from the user point of view, the movement is so smooth that comes unnoticed, with the KVM that is kept "alive" during moving.

 

[dal.01]

Thanks for the reply. I kinda figured as such. Thank you also for the clarification on the live migration.