Instructions for enabling & disabling VirtualBox support on Windows and MacOS

We added support for VirtualBox, primarily to lower the requirements of Multipass on Windows. Now anywhere VirtualBox runs, Multipass will, too.

It’s a separate environment so your instances from Hyper-V or HyperKit (the default backends on Windows and macOS, respectively) will not move over, but you can switch between the backends freely.

To enable the preview VirtualBox support, follow the steps below:

  • Windows

    • ensure Hyper-V is disabled in Windows Features
    • install Multipass and VirtualBox
    • in Admin Powershell:
       multipass set local.driver=virtualbox
      
    • reboot
  • MacOS

    • install Multipass and VirtualBox
    • in Terminal:
      sudo multipass set local.driver=virtualbox
      

To go back to the default backend:

  • Windows

    • in Admin Powershell:
      multipass set local.driver=hyperv
      
    • enable Hyper-V in Windows Features
    • reboot
  • MacOS

    • in Terminal:
      sudo multipass set local.driver=hyperkit
      

Please let us know any successes (and failures, too) :slight_smile:

Any pros/cons feature wise running Multipass in Windows with Hyper-V versus Virtualbox? Any differences in performance? (I think virtualbox can use the Hyper-V core anyway?).

Hyper-V isn’t an option in Windows 10 Home, but VirtualBox works there. Performance isn’t all that great without Hyper-V.