There are some processes that run whenever vmware is not directly in use. VMWare creates virtual interfaces on your system so that it can do NIC bridging for multiple virtual machines all at once. The three that I have noticed are
vmount2.exe, vmware-authd.exe, and vmnat.exe.
VMount2.exe - This is used as part of the importer in the software, it is used to mount the images so that they can be imported into the virtual machine.
VMware-authd.exe
- This is used for authenticating local or remote users to vmware.
VMnat.exe - This is used for setting up NAT between your virtual VMWare network and your physical network.
On 6/26/06, Phil Schaffner <Philip.R.Schaffner@nasa.gov> wrote:
On Mon, 2006-06-26 at 09:56 -0700, Mike wrote:
> That's an interesting idea, but I'm not sure I want to fork out $200
> for vmware workstation. Do you know if vmware player would be
> sufficient?
Have seen procedures for using VMware Player to install a new system
over an existing downloaded image. Can't create a new VM from scratch.
> I'm also wondering, if vmware is installed does it add yet another
> constant process even when "not" in use?
Can't answer that one definitively, but I know VMware Workstation under
Linux does have some overhead with the services it starts, so I'd guess
that there would be something similar running for XP VMware Player.
Phil
_______________________________________________
CentOS mailing list
CentOS@centos.org
http://lists.centos.org/mailman/listinfo/centos
--
Thx
Joshua Gimer