VM moved from VirtualBox will not start in Fusion on an M4 Mac mini
An was running as a in VirtualBox. The setup used the `haos_generic-aarch64-17.2` image, which appeared as ARM 64-bit Oracle Linux and ran normally on the ARM-based Mac.
Because the problems seemed tied to VirtualBox rather than itself, the same was exported from VirtualBox as an `.ova` file and imported into VMware Fusion Pro 26H1. The import appeared to work.
When started, VMware Fusion refused to power it on and said the requires the X86 machine , which does not match the ARM host. The confusing part is that the original image was ARM 64-bit, but Fusion treated the imported machine as if it needed X86.
Key points
- was running in VirtualBox on an .
- The image used was `haos_generic-aarch64-17.2`, shown as ARM 64-bit Oracle Linux.
- The was exported from VirtualBox as an `.ova` file and imported into VMware Fusion Pro 26H1.
- Fusion imported the file but would not start it because it believed the machine required X86.
- Moving between apps on can fail because settings may not carry over correctly.