When I try to utilize the virtual network manager on 'full' clones or an original VM, any changes in the port configuration of one of the clones or the original VM change them all to the exact same settings. Is this normal. I would like to have different port assignments for each of the clone's host. Is this possible? Any help is appreciated.
Also, when creating a VM, the memory slider does not adjust the numeric value in the upper right box. However, if you input a numeric value, the slider automatically adjusts. Just thought you'd like to know.
-Mark
Hi,
The clones are linked clone or Full Clone?
They are full clones. I've replicated this problem quite a few times. It seems like I should be able to modify each of the clones individually. But I could be wrong. I know the free competitor VB can do it with ease. Thanks for the quick reply.
-Mark
Hi,
If not much of trouble, could you list out the steps of the issue re-production, would love to replicate at my end. ![]()
I could be all wrong about this, but it's quite simple really. Clone any VM so that you have two copies of the same VM. Go into the first one via the network editor and add a port forwarding rule with say the host being port 2222. Example "Rule 1 127.0.0.1 2222 10.0...2.15 22. Close that one out and go into the cloned version and do the same except make the local host's port address 2223 and close that one out. Now in my case, if I go back to the original and check the port number, it has changed along with the clones new host port assignment to 2223. In other words, both versions have identical port forwarding rules with the host port assignment of 2223. Say you put a unique description for the port forwarding rule in each VM , they will also change so that both versions have the same description. All I'm trying to do is make unique port forwarding rules for each VM.
The clones in my case are not linked, they were set up as full clones. I've tried different variations always ending up with the same result. Two versions of a VM with identical port assignment rules.
I hope I'm not confusing anyone, It could be that I'm just doing something wrong or maybe this is the way WorkStation 15 is supposed to function. Thanks again for the help.
-Mark
Thank You Mark, I would test and let you know.
port forwarding rule is a global configuration for all the NAT VMs, you can try to add multiple port forwarding rules, ie, rule1 for the original VM, rule1 for clone VM1, rule3 for clone VM2. Note that you'd better configure the different port forwarding rules with different host ip and VM ip, so changing your clone VM's ip address to distinguishable ones should be best practice.
sorry, i mean configure different port porfowrding rules with different host port number, host ip should be same
Hi Yawn,
Its not related to the current question, but, could you please let me know if there would be any messages that would be logged by a failed attempt to create an installation medium and that *don't* contain the name of the VM to be created?
Background:- Tried to create a Mac Mojave VM using the "Install Mac Os Mojave" but it yielded in "unable to create an installation medium".
Hi yanw,
Thanks for your reply. I understand what you are saying about the editor being global, and your solution of additional rules for my cloned VMs is acceptable. But that brings up another question. Will all my VMs in the Work Station's list of available VMs clone or not be affected also? In other words, if I have an VM of CentOS, a VM of Fedora, a Kali VM with three clones, are all VMs and clones going to be affected if I add a port forwarding rule to one of them? I would think that you would want to manipulate each VM individually unless you want them linked. Sorry for taking up your time, but I'm just curious and want to fully understand the functionality of the network management editor. Your time is much appreciated.
-Mark
