So I've been using Proxmox at home for a number of years now and have been very happy with it.
I and another team member have (finally) been able to persuade our employer to get off a bunch of end of life Esxi hypervisors and move to Proxmox instead
.
In general the migration has been going well (6 vm's done) but now I'm down to the last VM, the Domain Controller and this is not going so well.
I'm using clonezilla for the migration. I am able to set the cores and ram and disk size to be the same as the original though the CPU itself is different.
What I *think* is triggering the asking for activation on first boot is the NIC. Esxi sees it as an Intel E1000 but the VM itself sees it as an Intel 82574L.
I've also set Proxmox to use the E1000.
The OS is also Windows 2012R2 DataCenter.
I do have the original activation key but the vm (on Proxmox)_does not accept it.
We are planning to deactivate this vm in a few weeks time but we have some other work to complete before that can be done so we need it for a little while still.
Would setting the MAC address on the NIC to be same on source and destination for first boot after the migration help here?
I and another team member have (finally) been able to persuade our employer to get off a bunch of end of life Esxi hypervisors and move to Proxmox instead
.
In general the migration has been going well (6 vm's done) but now I'm down to the last VM, the Domain Controller and this is not going so well.
I'm using clonezilla for the migration. I am able to set the cores and ram and disk size to be the same as the original though the CPU itself is different.
What I *think* is triggering the asking for activation on first boot is the NIC. Esxi sees it as an Intel E1000 but the VM itself sees it as an Intel 82574L.
I've also set Proxmox to use the E1000.
The OS is also Windows 2012R2 DataCenter.
I do have the original activation key but the vm (on Proxmox)_does not accept it.
We are planning to deactivate this vm in a few weeks time but we have some other work to complete before that can be done so we need it for a little while still.
Would setting the MAC address on the NIC to be same on source and destination for first boot after the migration help here?
