When you move or copy a VM and open it, VMware asks you if you've copied or moved it, so it can do some configuration. Does anybody know what it does exactly? And can you tell it (programatically) which is the case?
For example, if it only changes something in the .vmx file, then, after I copy a VM, i can use a script to edit the .vmx exactly how VMware would do it if I choose "I copied it". That way, when I actually open the VM, it won't ask me.
read http://sanbarrow.com/vmx/vmx-advanced.html#uuid
___________________________________
VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay
When you move or copy a VM and open it, VMware asks you if you've copied or moved it, so it can do some configuration. Does anybody know what it does exactly?
When you choose "copied" the guest ID and MAC address is changed so you do not have two guests with the same UUID and MAC address in the network.
When you choose moved they stay the same.
AWo
VCP 3 & 4
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=
read http://sanbarrow.com/vmx/vmx-advanced.html#uuid
___________________________________
VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay
Excellent! Great resource.
I can just write uuid.action = "create" into the .vmx and that's it.
uuid.action = "create"
is not the option I would use - you probably want "keep" = I moved the VM
"create" means the VM will create a new UUID / MAC and that may mess up your network configuration on Windows or Linux with udev.
uuid.action = "create" is good to create full clones from a batch - but it is NOT a setting you want to keep in the vmx-file for continuos use of that VM.
uuid.action = "move" on the other hand is an option that is harmless - you can keep this inside the vmx-file for continous use.
___________________________________
VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay
Why would it mess up? The scenario is copying some VMs from DVD, or similar.
if you change the MAC address of a Windows or Linux VM with udev the system thinks the old ethernetcard is out to lunch but may come back in a while.
So it reserves the old network configuration for this "temporarily absent" network card.
And it creates a new configuration for the "new" network-card.
If you had a fixed IP configured - this IP will be no longer available after you change the MAC.
___________________________________
VMX-parameters- Workstation FAQ -[ MOA-liveCD|http://sanbarrow.com/moa241.html] - VM-Sickbay
...the system thinks the old ethernetcard is out to lunch but may come back in a while.
</div>
:smileylaugh: Now I know why mine got so fat and slow!!!!!
AWo
VCP 3 & 4
\[:o]===\[o:]
=Would you like to have this posting as a ringtone on your cell phone?=
=Send "Posting" to 911 for only $999999,99!=