It’s best if the VM was never encrypted in the first place, but if it is encrypted, it will work if you decrypt it. Once the VM is powered off, we need to adjust some of its settings while it’s still in Fusion to remove the components, which won’t work in the cloud. So, here’s my VM, with Tools installed, running in Fusion.įirst thing we do is power the VM off.
I was sure to install VMware Tools while it’s still in Fusion, as Tools is the same regardless of what the host is, just some features are enabled or deactivate depending on that host. In this case it was a simple Ubuntu 12.04 LTS VM after a fresh install. To start off I created a VM using Fusion. As you can see, there are many reasons why you would want to migrate a Fusion VM to the cloud. Maybe you create a standard template and then just clone it in the Cloud. Maybe you want a cloud-backup of an important VM. Develop an app locally, and then push to the cloud to make it public. In this post, I’ll show the process to migrate a VMware Fusion based Virtual Machine to vCloud Hybrid Service (‘vCHS’ for short). There are some subtle differences between how a Fusion VM works and how a VM that’s living in vCHS needs to behave. In that vein, the service supports any workload that runs on VMware hypervisor technology, from ESXi/vSphere, all the way up to Fusion and Workstation, making it pretty easy to build a VM locally and then ‘push’ that to the Cloud with minimal tweaking.
So, you may have heard that my team at VMware launched the ‘vCloud Hybrid Service.’ It’s pretty exciting, and the way we built it gives instant value to existing VMware customers by allowing them to easily migrate their VMs to the cloud without having to completely rebuild them, or learn a whole new paradigm of how to do IT and deliver infrastructure. This post is a repost from Mike’s personal blog,. Please see below for what the process of booting from the Boot Manager to the macOS installer’s Recovery environment should look like.By: Mike Roy, Technical Marketing Manager at VMware Note: This Recovery environment is separate from the Recovery on your virtual machine’s regular boot drive, but as long as the OS versions match between the VM and the disk image, it shouldn’t matter which disk’s Recovery environment that you’re actually in. The virtual machine should now boot to the macOS installer’s Recovery environment. Once booted to the Boot Manager screen, use the arrow keys on your keyboard to select the CDROM option. Under the Virtual Machine menu, select Power on to Firmware.Ĥ. Connect the disk image of the macOS installer to the virtual machine’s CD/DVD drive.ģ. If necessary, add a CD/DVD to your virtual machine.Ģ. Once you have the disk image built, use the procedure below to connect the disk image to the virtual machine and boot from it.ġ. You can create this disk image using a tool I’ve written: So your first step is to create a disk image of the macOS installer for the OS version you want. This method relies on VMware Fusion being able to boot a virtual machine from a disk image. For more details, please see below the jump. This is the same keyboard shortcut as booting to macOS Recovery for Intel Macs so if you’re not very fast, or you don’t have the virtual machine window selected correctly, you may be looking at an unwanted request to restore a snapshot instead of macOS Recovery.įortunately, there’s a workaround for this behavior which will reliably get you into macOS Recovery. Booting a VMware Fusion virtual machine to the macOS Recovery environment can be challenging, as Fusion uses Command-R as a keyboard shortcut for restoring snapshots.