WoodyZ's Posts

You do not need any previous version of VMware Fusion installed to upgrade to a later version.  Simply download the latest release directly from VMware's website and install it.  Then copy/move the Virtual Machine Package from its current location to the new Mac by one manner or another.  Then either use VMware Fusion > File > Open... or double-click the Virtual Machine Package in Finder. Either will then populate an entry on the Virtual Machine Library window for ongoing access.  You can choose to upgrade the virtual hardware, if not prompted, via Compatibility in the VM's Settings.  Also, don't forget to upgrade VMware Tools within the Guest OS if it doesn't happen automatically.

VMware does not support the running of OS X under VMware Player/Workstation!  Also, running legally virtualizable versions of OS X in a Virtual Machine may only be done when done on Apple-branded hardware and when done while running under OS X and for that you need VMware Fusion not VMware Player/Workstation, otherwise you're violating the Apple SLA for that product.  Therefore no help can be provided to you for OS X in this use case scenario as it would violate VMware Community Terms of Use to do so.

HuanguoZhong wrote: I'll have a try. And I think you can try to add the whole disk instead of a specific partition Are you seriously!?...  From the information presented by Lixw668 it appears that there is only one physical disk and as such one cannot add the entire disk when one is trying to boot an OS installed on a different partition of the same physical disk that the Host OS is also running from!

Wow, I already knew that however I was hoping you'd expound on it!   I'm assuming, since you said "I am in search of a C++ solution", you're a programmer and as such you can just as easily as I review the VIX API Documentation, specifically the VIX API Reference Function Support Matrix at VMware's website.  I did take a quick look and saw nothing relevant however if you're doing the programming then I'd suggest you review it too. Without knowing more then you said so far, I'll just have to say that my first reply covers it.

VMware does not support the running of OS X under VMware Player/Workstation!  Also, running legally virtualizable versions of OS X in a Virtual Machine may only be done when done on Apple-branded hardware and when done while running under OS X and for that you need VMware Fusion not VMware Player/Workstation, otherwise you're violating the Apple SLA for that product.  Therefore no help can be provided to you for OS X in this use case scenario as it would violate VMware Community Terms of Use to do so.

d0galbreath wrote: I'm brand new to VMware Workstation. Given this setup, is there any way that I can set up my VMs in their own subnet so I can do my testing without messing up the physical network? If so, what is that way? I'd appreciate any help you guys and gals could give me. I strongly suggest you start by reading the documentation!   In particular chapter 5, "Configuring Network Connections" in Using VMware Workstation (PDF) so as to have a better understanding of the VMware Virtual Network Infrastructure Also have a look at: Understanding networking types in hosted products (1006480)

The vmrun utility does not have the capability to list VM's that are not running. Your options are to parse the various files that VMware Workstation stores VM information that it knows about and or search the file system for .vmx configuration files.  Although the latter does not necessarily mean it a complete and or functioning VM.  I guess it really depends on the total scope of the goal how much coding will need to be done.

@vmxmr, without quoting what's technically not totally true in your reply let me just say the following... There is a big difference between trying to input an OEM Product Key in a Windows 180 Trial version on a physical machine or in a virtual machine and inputting an OEM Product Key in an OEM Windows version on a physical machine or in a virtual machine! 1. Providing the OEM Disc is not locked, in the various ways it can be with some Manufacture Branded OEM Discs, then there is absolutely no technical reason whatsoever why an OEM version cannot be installed, activated and run in a Virtual Machine! 2. While it is absolutely possible to install, activate and run some Windows OEM versions in a Virtual Machine nonetheless one must conform to the products EULA and in the case of Windows 7 OEM version, to my knowledge, none of them allow for use in virtualization.  That said the Windows 8 OEM System Builder EULA has a Personal User clause that absolutely allows for it to be virtualized! 3. As a proof of concept I took a Dell branded Windows 7 OEM Disc and install, activated and ran it in a Virtual Machine.  It did so without any issues whatsoever!  Nonetheless this is not permitted by its EULA and as such I'll delete the Windows 7 OEM version Virtual Machine as it was done simply as a proof of concept. @Radcon So there you have the truth, which is while it's technically doable with a non-locked OEM discs nonetheless one must conform to the products EULA and to my knowledge none of the Windows 7 OEM versions allow for use in virtualization by its EULA.  Therefore either purchase a Windows 7 Retail Package or a Windows 8 OEM System Builder Package which allows for Personal Use and can be installed in a virtualized environment by its EULA.

@avanish321 If as you said "I believe the networking file has retained some sort of locking." then to first suggest deleting the "/Library/Preferences/VMware Fusion" directory is a bit of an overkill without first investigating a permissions issue and also using First Aid in Disk Utility to verify permissions and the disk too!

Time Machine is not the *proper way to backup Virtual Machines! *It is a known fact that Time Machine is not 100% reliable backing up/restoring Virtual Machines under all circumstances/conditions.  Also backing up Virtual Machines via Time Machine is disk/time intensive and wastes a tremendous amount of space for something that may be corrupt and worthless come time to restore it.  At a minimum I would exclude Virtual Machines from Time Machine and with the Virtual Machines shutdown, not suspended, and VMware Fusion closed then manually copy the Virtual Machines Package(s) to an alternate location, preferably on to a different physical hard disk.  Then keep the User Data that is stored within the Virtual Machine backed up off of the Virtual Machine on a regular basis so as to always have a current User Data Backup.  If you have to restore a properly backed up Virtual Machine that is not as current at least you'll have a working Virtual Machine and current User Data to go forward with when you find out your Time Machine Backup of the Virtual Machine fails. Also have a look at: Best Practices for virtual machine backup (programs and data) in VMware Fusion (1013628)

You can configure the Virtual Network Adapter to use either NAT, the default, or Bridged for it to have connectivity beyond the Host however I suspect your issue might be relevant to this reply: Re: No network connection running VMware Player 7 on Windows 10 Tech Prev Enterprise