However, the virtual machine mimics the workings of a PC, allowing you to install Windows on the virtual machine, and then install any Windows apps that you need to run as well. The virtual machine (VM) is simply an app that runs on the Mac just like any other Mac app. VMware Fusion to create a ‘virtual machine’ that runs within macOS itself. Instead of splitting your hard drive into separate partitions for macOS and Windows, you use a virtualisation program such as This is where the other option, known as virtualisation, can come in handy. You can either rename the Boot Camp VM back to "Boot Camp", or simply drag it into the Fusion VM Library under the name you gave it.The only disadvantage of Boot Camp is that you lose access to all your normal Mac apps while you’re running Windows, which means you have to shut down Windows and boot back into macOS if you want to use Mac apps such as Apple Mail or Photos. Rename the Boot Camp VM bundle, which will prevent Fusion from deleting it as a failure, then acknowledge the alert panel. If you'd like to do the renaming via Finder, open a Terminal window and enter the command "open ~/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp" and Finder will open the ordinarily hidden folder for you. Note that the ~/Library folder is hidden by default under OS X Lion and Mountain Lion, so the simplest way to get to this folder might be from Terminal, not Finder. You'll find the Boot Camp VM in your home folder, under ~/Library/Application Support/VMware Fusion/Virtual Machines/Boot Camp. We'll do it by renaming the VM.ħ) While the error alert panel is showing, use Terminal or Finder to rename the VM. What we do need to do is prevent Fusion from deleting the VM when you acknowledge the failure. We'll want this file from Windows.ģ) Restart your Mac under native Boot Camp.Ĥ) From Windows, find the file bootcamp.reg where you saved it, and double-click to add those settings to the Registry.ĥ) Restart your Mac under OS X, start Fusion, and recreate the Boot Camp virtual machine.Ħ) It's likely that it will fail again at the "preparing your virtual machine" stage, but that's no longer critical since the necessary settings have been added to the registry already. They don't interfere with using Boot Camp natively.ġ) Find the file /Applications/VMware Fusion.app/Contents/Resources/naos-1.0.vmwarevm/reconfig.iso and open it under OS X, which will mount the ISO.Ģ) Copy the file "bootcamp.reg" on the ISO and copy it to some folder on your Mac, or to a USB drive. As a workaround, you can add those keys and driver enablings (!) manually, under Boot Camp itself. Fusion is attempting to insert registry keys and enable drivers for the boot device, and in certain situations it's unable to do so. The problem occurs after the Boot Camp VM has been set up, but before it's powered on for the first time as a virtual machine. While I don't have a fix for that right now (we have a bug filed, and are working on it), I do have a workaround. The problem I think you saw, a failure at the point of "VMware Fusion is preparing to run as a virtual machine" can be caused by the state of the Windows registry.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |