If you want to switch back to the default driver: PS> multipass set local.driver=hyperv You can then open, say, and the service running inside the instance on port 8080 will be exposed. To expose a service running inside the instance on your host, you can use VirtualBox’s port forwarding feature, for example: PS> & $env:USERPROFILE\Downloads\PSTools\PsExec.exe -s $env:VBOX_MSI_INSTALL_PATH\VBoxManage.exe controlvm "primary" natpf1 "myservice,tcp,8080,8081" They may not be represented in Multipass commands such as multipass info, though. NOTE: You can still use the multipass client and the system menu icon, and any changes you make to the configuration of the instances in VirtualBox will be persistent. To list the instances on the command line: PS> & $env:USERPROFILE\Downloads\PSTools\PsExec.exe -s $env:VBOX_MSI_INSTALL_PATH\VBoxManage.exe list vms
Download and unpack PSTools.zip in your Downloads folder, and in an administrative PowerShell, run: PS> & $env:USERPROFILE\Downloads\PSTools\PsExec.exe -s -i $env:VBOX_MSI_INSTALL_PATH\VirtualBox.exe Multipass runs as the System account, so to see the instances in VirtualBox, or through the VBoxManage command, you have to run those as that user via PsExec -s. Finding Multipass instances in VirtualBox You can then tell Multipass to use it (also with Administrator privileges): PS> multipass set local.driver=virtualboxįrom then on, all instances started with multipass launch will use VirtualBox behind the scenes.
You may find that you need to run the VirtualBox installer as administrator.
#Virtualbox windows install
To that end, install VirtualBox, if you haven’t yet. If you want to (or have to), you can change the hypervisor that Multipass uses to VirtualBox.