> The IP address stays with the vm for the entire life cycle, till it's > expunged.
I hope I misunderstood what you meant by "expunged". > * Change the record in nics table for all vms nics to have new ip address > * restart the guest network > * stop/start ALL user vms in network Talk about "doing it wrong". It's a simple NAT rule. Just modify the ruleset and reload it at the router. The guest doesn't care what it's public IP is. Rebooting guests is uncalled for. If you're talking about changing the private/internal IP|VLAN of a guest, at most you rewrite the .VMX or it's equivalent and poweroff/on (or in kvm/xen "how-badly-can-we-misname-a-function speak" destroy/create) the VM. I can edit a guest's network setting all day long in VMware with the VM live, no less and replumb (move the interface from one port group to another) while I'm at it. I realize KVM/Xen are inferior hypervisors, but CS shouldn't introduce unnecessary disruption.
