![]() NOTE: There is another, experimental way to achieve the same goal and potentially with better performance. Once installation is complete, reboot your VM for the changes to take effect.Īfter the reboot, the installation of Ubuntu (the default distribution used by WSL) continuesĮt voilà! MacOS running VMware Fusion running Windows 11 running Hyper-v running Ubuntu Linux In Windows Terminal (you are in the Windows Powershell shell by default) type To install WSL, right click the start button and select 'Windows Terminal (Admin)' After the wizard finishes you need to restart the VM.Īfter the reboot you can enjoy a more appropriate resolution. Click on 'Virtual Machine' -> 'Install VMware Tools'ĭoubleclick 'setup64' to install VMware Tools and run through the installation wizard. Once you are done with setup you can install VMware Tools to add to relevant drivers to Windows 11. If you are happy with your settings go ahead and boot the VM and follow the Windows installation steps. Now you can change the amount of virtual CPU and Memory that is allocated to the VM, you can also opt to enable hypervisor applications in the VM if you want to make use of WSL 2 (Windows Subsystem for Linux), which uses Hyper-V to run a Linux distribution on Windows 11. You do this by selecting 'Advanced'Ĭlick the 'Disable Side Channel Mitigations' checkbox Optionally you can disable side channel mitigations to improve the performance (but obviously lower its security posture) of the VM. Select 'Trusted Platform Module' and click 'Add.'Īcknowledge the information pane and click on 'Show All' You can do this by going back to all settings and clicking ' Add Device.' on the top right Next we need to add a Trusted Platform Module as that is a prerequisite for Windows 11. ![]() Next click on 'Encryption' and enter a password of your choice Instead of selecting Finish, go ahead and click Customize Settings if you want to change the name of the VM or the location of the files, if not, click Finish. Select UEFI and optionally UEFI Secure Boot Next we run Fusion and create a new VM using the "install from disc or image" option. Follow the steps below to avoid the dreaded "this machine is not compatible with Windows 11" message because a (v)TPM is missing by default.įirst step is to acquire an ISO image which you can find here: When that happens, you're performing the raw disk setup again before powering on the VM.I needed a Windows 11 VM to do some testing and since I currently don't have any Windows hardware anymore I decided to use VMware Fusion on my (intel) mac instead. ![]() Each time the OS boots it's a crap shoot as to what device name will be chosen for your non-boot disk (it's somewhat but not entirely dependent on when the device is recognized by macOS). The big problem is that macOS does not persistently name disk devices at the OS level. It requires use of a poorly documented command line utility (at least for Fusion it's poorly documented) and enabling a Fusion component for full disk access (also not well documented). The best and easiest way is to format that drive as APFS, then create a normal virtual machine with the files hosted on it.Īgreed that raw disk mode is a PITA. The first one requires raw disk mode, which is a PITA to setup and unless you have very specific needs, I'd avoid it at all costs and do one of the other options. You trying to install Windows directly on the drive, as a bootcamp install, or as a virtual machine where the files live on the drive?
0 Comments
Leave a Reply. |