Fusion

 View Only
  • 1.  One separate copy of VMware Fusion per User

    Posted May 26, 2010 09:03 PM

    Hi,

    I have a Mac Pro where I want two independent copies of VMware Fusion to be running. I was thinking of having two users on with Admin priveledges and each with a vmware fusion installation of their own.

    The one will host services which need to be online all the time.

    And the other one will be used for testing and since VMWare fusion doesn't allow revertToSnapshot operation while fusion is on, it will need to turn it off (at least) before the revertToSnapshot is executed. Thus I can't have all my servers and testing VMs running on the same VMware Fusion copy. (Please let me know if I'm wrong and there is a work around that will allow that everything on one VMWare fusion copy only.)

    So in case, I do need two copies, VMWare seems to install so that it is available for all the users on the same machine. And it doesn't seem to be a simple install and uninstall process. So I was thinking (naively) that I could just pull VMWare Fusion package out from the Applications folder and put it in say the Desktop. And then I can do that again for the other user.

    Will that work?

    Thanks



  • 2.  RE: One separate copy of VMware Fusion per User
    Best Answer

    Posted May 26, 2010 09:27 PM

    I have a Mac Pro where I want two independent copies of VMware Fusion to be running. I was thinking of having two users on with Admin priveledges and each with a vmware fusion installation of their own.

    To be clear, there's only one Fusion install per machine (for various security reasons). Each user can have their own set of virtual machines.

    And the other one will be used for testing and since VMWare fusion doesn't allow revertToSnapshot operation while fusion is on

    I believe the check is actually whether there's a lock file, not whether any instance of Fusion is running. If user A is running virtual machine X and user B wants to revert virtual machine Y, it should work fine (as long as Y is not in A's virtual machine library, but that would cause other problems anyway).

    My understanding is that older versions of vmrun incorrectly ignored the lock file, so while you could revertToSnapshot with Fusion running, there was a small chance of corruption.