I have a question about Proxmox Live Migration. I've tried it several times, and it seems to work fine, importing correctly into Proxmox. However, I'm having a problem with the imported machine, whether it's a Windows Server 2016 or a Windows Server 2022. The network adapter on the source machine has a static IP address assigned and configured, but the machine in Proxmox always ends up configuring itself to obtain an IP address via DHCP. Is there something I'm doing wrong, or is this normal behavior? Can I change it? Is there a workaround to fix this problem? Thank you very much.
Proxmox Live-migration
- Thread starter ecraul
- Start date
Are you really talking about live-migration? That would be when you move a running VM from one node in a cluster to another node.
Or are you importing a VM from another virtualization solution to Proxmox VE? Possibly from VMware with the import tool and the "Live import" option?
If you mean the latter, then this is somewhat expected. The underlying hardware will change for the guest OS. So a new NIC will show up, which might be using DHCP as default.
See https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Preparation
Last edited:
Thank you, Aaron.
That's correct, I'm importing from VMware ESXi 8, and I understand that the network device changes during migration, so it's configured to obtain an IP address from DHCP. But perhaps there's a configuration or script that, when the VM starts for the first time in Proxmox, during the Live Import process, executes that script and assigns the IP address of the source VM? This is desirable because we want to minimize downtime as much as possible.
That's correct, I'm importing from VMware ESXi 8, and I understand that the network device changes during migration, so it's configured to obtain an IP address from DHCP. But perhaps there's a configuration or script that, when the VM starts for the first time in Proxmox, during the Live Import process, executes that script and assigns the IP address of the source VM? This is desirable because we want to minimize downtime as much as possible.
I am not aware of anything that would reconfigure the new NIC with the static IPs of the old one. But someone else might be.
With some powershell magic that is deployed to the guest before the migration, something is surely possible. But my powershell skills are way too limited to give any more hints than that.
If you use DHCP overall with reservations, you can assign the old MAC address during the import. Then the old reservations wlll still be valid.
With some powershell magic that is deployed to the guest before the migration, something is surely possible. But my powershell skills are way too limited to give any more hints than that.
If you use DHCP overall with reservations, you can assign the old MAC address during the import. Then the old reservations wlll still be valid.