If you need a Windows VM you need to run a suitable version of VMware on an x86 platform, meaning Intel or AMD processor. open-vm-tools is available through most package managers in these Linux distributions and is usually installed by default when installing a Linux OS in a VM. Linux has been supporting ARM for several years, so ARM support in modern Linux distributions is very good. What you can do is run Linux VMs, such as Ubuntu and Fedora, that are available for ARM. If Microsoft were to make a suitable license available I'm sure the VMware Fusion guys will support it eventually, but for now there are no VMware Tools available for Windows on ARM, and any methods to install it anyways are unsupported and most likely won't work well if at all. There are some ways to do it, but they don't work well and since there is no way to get a license VMware does not make any effort to support Windows on ARM. Are you saying that the preview version should work if and only if I use VMWare tools? If so, where can I get the explain-it-like-I'm-5 version of how to install VMWare tools, including which version to use (Mac, Windows?) and how I make the disk image available to VMWare Fusion in the right way?īasically, as things are right now you can not run Windows in VMware on Apple Silicon. I downloaded the preview version for free to run on my new MacBook Pro, which uses an M1 chip. I am a web developer but I am very new to running virtual machines, so you might need to explain things to me slowly, with all the jargon defined. But note that it's unsupported, and without VMWare tools has significant limitations. Some folks have gotten it to work (see other threads here in the forum for tips). > Due to microsoft licensing restrictions there is currently no support for running Windows ARM on an M1 machine. There is NO way to run Intel guests on an M1 machine (period, full stop - if you need Intel guests, run an intel machine). The preview version will run ARM guests only. The network will be found (you will know because Windows won't ask you about a network and will instead say 'Checking for Updates'.> There is a preview version (that's the forum you actually posted the question in). The VM will reboot and Windows will restart the setup process. When the installation finished, type the following command in the PowerShell prompt: shutdown /r /t 0 The VM's screen may blank momentarily while this happens. The vmxnet3 network driver and the VMware SVGA video drivers will be installed. Once in Powershell, type the following d: The purpose of this command is to switch from the cmd.exe to PowerShell. Wait a few seconds for the D drive to attach, and issue the following commands in the command line prompt: powershell

The ISO will be available in the VM as the D drive. use the Fusion menu to attach the VMware Tools ISO to the VM Virtual Machine > ReInstall VMware Tools. vmdk can now be used to create a Custom VM'.Īt the first screen, instead of answering the question about the country, type shift-fn-F10 to bring up a Command prompt.Īt this point. I created a new virtual machine according to the steps in the Tech Preview Testing Guide, page 22, starting the steps after 'This. I downloaded that same VM and converted it to vmdk using: qemu-img convert -p -O vmdk Windows11_InsiderPreview_Client_ARM64_en-us_25158.VHDX Windows11_InsiderPreview_Client_ARM64_en-us_25158.vmdk I have no idea what may have been done to it.

If you find a problem running on Ventura I suggest you try it on Monterey to see if it exists there.Īs a matter of security, I do not trust any OS installer obtained from sources other than the manufacturer/distributor/author. You are asking for trouble - it's unlikely that even VMware had the chance to do any testing with it on Ventura before releasing it to us. My preference would be NOT to run this Fusion tech preview on pre-releases of Ventura. The utilities that uses to build the ISO on Linux are typically found in the repos of many Linux distributions. You can run the download/build from within a Linux VM. If you can't install homebrew on Ventura, you can't easily get the open source apps needed by the scripts. They use open source applications which is why homebrew is needed to install them. The converters on macOS do not use Windows apps. It would not be surprising that homebrew does not yet support an pre-release, beta version of macOS.

Vmware fusion m1 processor