
VMware Fusion and Parallels Desktop don't have a good command-line interface to create and manipulate virtual machines, whereas VirtualBox has it out of the box, which is pretty good." "The solution has high performance and is easy to use." "Technical support is good." "It's a pretty good product in terms of monitoring." "This product is very user-friendly and easy to use." It's something that some other products on the desktop side do not have. You can create and manipulate virtual machines from the command line, which is also very important. So, if you need to do any modifications for your own purposes, you can just download the source, modify it, and deploy it in your environment. The other thing that is good about VirtualBox is that it is open source. These kinds of operating systems are also supported by VirtualBox. It even runs on some of the commercial operating systems that are not mainstream, such as Solaris and BSD. You can switch it over to Linux or Mac OS and see if you can run the VirtualBox on those particular machines.

For example, if you are on Windows and you create this virtual machine, you can actually go ahead and change the operating system. Once you create a virtual machine in one particular environment, you can switch over to see if you can run it in other environments. I am able to perform small developing tests." "The snapshot feature is very powerful it protects us from disaster." "The good thing is that it is multi-platform. I am quite new Workstation user too, so I have not looked much at it, but it is kind of confusing."The installation is easy." "I like that it is free and runs on Linux/Ubuntu - I wouldn't use any other solution. For me it is very very vague what the VMNETx represent and the difference between them. I do not understand the networking in Workstation. I do not understand the Workstation networking! I have been working a lot with physical switches, all kind of Cisco and HP devices with VLANs, spanning tree and similar, and also know the vSphere vSwitches (standard and distributed) well, but. Thats very vague - this is not a device - vmnet1 and vmnet8 use the same virtual adapter + for vmnet8 your host runs an additional NAT-service which is not too rock solid

So the NAT service is not suitable for high loads, but if wanting to run high network loads internal to the workstation and just be able to download updates or similar, it should work?

But that only happens if you have very busy VMs - for example when the VMs run p2p software like emule or stuff like that
