-
Notifications
You must be signed in to change notification settings - Fork 68
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add Windows 11 arm64 images #414
Comments
@mmatczuk thanks for reaching out, for providing all these details and for your kind words :) I already build VMware and VirtualBox images for amd64, so those would be the best starting points indeed. I cannot promise a timeline for this, first I would need to set up my build environment for Mac, but I was thinking of getting a Mac mini anyway, so this gives some more motivation :) I can also try for some hosted options for the time being. Btw, there was a regression in Vagrant booting Windows boxes in the latest version, you can check here for more details, maybe it solves the problem of booting the other box you found: #404 Thanks again, I will keep you posted. |
Thanks for the heads up. I downgraded Vagrant. The issue seems to be in the image. For reference please find below the details: Vagrantfile
Failed SSH debug logs
|
@mmatczuk thanks for the detailed investigation. SSH is not the default communicator for Windows, but WinRM is, this is maybe indeed an issue with the box's configuration. As a reference, this is my default box configugration for Windows boxes and VMware, can you try maybe merging the relevant sections? You'd probably need to set at least these two vm settings: config.vm.guest = :windows
config.vm.communicator = 'winrm' |
Thanks @gusztavvargadr this seems to help but there is still some networking issue
It seems to hang here, I cannot access any port from host to guest :/ |
@mmatczuk this looks then indeed some issue with the box itself, likely it's not configured properly. If you want to experiment with this further, check out the bootstrapping code that I use when booting all Windows machines for the first time to enable WinRM (and also SSH btw). You can try running the relevant part of that script via the VMware UI, then test if Vagrant can connect to the machine that way. Btw, I am building my amd64 Hyper-V based boxes in Azure now, I will give it a try if I can do there the arm64 too, then I don't need to purchase too much stuff upfront to have at least an experimental image. |
It looks to me like there is a network configuration issue first.
That's awesome! |
This would allow to bridge the gap and run Vagrant with Windows on modern Apple hardware i.e. M1/M2 CPUs.
VirtualBox support for arm64 is available in 7.x BETA. I think it is outside of the scope of this issue, and can be added later when the whole ecosystem matures.
Vagrant has an official VMWare provider. VMware Fusion 12/13 supports arm64. This generally works (with Linux) and is accessible via Personal License for free (thank you VMWare). The process is confirmed by many to work, you can take a look at this gist.
Parallels also support arm64, and have homegrown Vagrant provider but I did not check it. Unlike VMWare there is no free Personal License.
Windows 11 provides arm64 images that can be run on Apple M1/M2 CPUs. At the moment of writing this there is one Windows ARM image for Vagrant see here. This image loads but does work with Vagrant for me, and there is no source.
I think this awesome project is perfectly positioned to address this important issue and allow us to work on Windows on Mac.
The text was updated successfully, but these errors were encountered: