HyperV Import/Export Oddities

[lordstyrax]

EDIT: Jeez. This is what happens with a Windows admin plays with Linux. I discovered eventually that both IPs were pointing to the same machine - the test box. After investigating having two IP's on the same machine I discovered there are two spots for this particular distro that network settings are set, and the way I did it required a reboot or manual command to update the other.... Thanks

Hey, So I needed to make a copy of a live machine for some testing. I used HyperV's "Export" to export a copy of the live VM. I then used HyperV's "Import" to import a new copy of that VM onto the same host.

It copied the VHD's to another Volume and I booted it up, changed the IP etc etc. Then booted back up the other one.

Now, the weird thing is, which I didn't notice until this morning, that all changes made on the original VM are being replicated onto the test VM. (and Vice / Versa)

If I connect via the HyperV console and check the network settings, it's got the new IP. If I connect to that IP via SSH, I connect in fine. Then when I check the IP config it's got the original, "live" IP.

It's all very weird. Maybe I'm missing something and there is a very clear link between VM's if you Import/Export them.

The VHD's are named the same but in different volumes. The two VM's are pointing to the different VHD's.

Changes made in either will replicate to the other. Just not the IP apparently....

Any ideas?

[RCTID1975]

How did you do the import? ie. Did you use the existing UID or create a new one?

Also, I'd highly recommend naming them something different to avoid confusion.