7/16/2023 0 Comments Vmware fusion ubuntu m1Please retry after updating the indexes of available packages, if that does not work then remove related third party packages and try again. UnreportableReason: This does not seem to be an official Ubuntu package. Tags: jammy uec-images third-party- packages InstallationMedia: Ubuntu-Server 21.10 "Impish Indri" - Release arm64 (20211013) InstallationDate: Installed on (26 days ago) Please let me know what other information I can provide to help diagnose this issue. Given that I can't boot using the 5.15.7 and 5.16-rc4 kernels, I can't provide the output from: com/t5/ Fusion- for-Apple- Silicon- Tech/Anyone- have-any- luck-with- Ubuntu- 5-15-kernels/ m-p/2880362 I see the same "hang" for both 5.15.7 and 5.16-rc4.įYI this has also been reported by others who note that the problem appears to be specific to Ubuntu: However whenever I try to upgrade to either the 5.15 or 5.16 series my VM hangs at boot time after:ĮFI stub: ERROR: FIRMWARE BUG: kernel image not aligned on 64k boundaryĮFI stub: ERROR: FIRMWARE BUG: Image BSS overlaps adjacent EFI memory regionĮFI stub: Using DIB from configuration table I am successfully using the 5.14 kernel series (currently 5.14.21- 051421- generic) but note this is now EOL. com/teamfusion/ 2021/09/ fusion- for-m1- public- tech-preview- now-available. **Describe alternatives you've considered**Ĭlear documentation mentioning the architecture issues.I am using VMWare Fusion Tech Preview on an Apple M1 Max MacBook Pro per: When specifying `bionic64` in your Vagrantfile, and that box does not exist for _your_ architecture, you should be told through an error message. (from a list of enums) when searching for images. Vagrant Cloud should require an `architecture` field for new boxes and let users filter on `amd64` (`x86`?), `arm64`, etc. You cannot filter boxes on Vagrant Cloud by architecture, nor will you get a good error message if one does not run on your provider due to architecture mismatch. Even if they should be able to to get VMWare Fusion playing nicely with Vagrant, the issue of finding boxes that runs on the right provider is left missing. **Is your feature request related to a problem? Please describe.**Ī lot of dev … elopers are now on ARM architectures. can be found in the issue, if deemed relevant. I have no idea how running (a presumed) x86-64 image on ARM would work (if at all), or if Fusion on ARM is only capable of running ARM images on ARM.Īnyone had success with this or has any knowledge to share? This could of course be because almost every bit in this equation is bleeding edge (or at least pretty fresh):īut it could also be that I simply don’t know how one would use Vagrant on vmware. Vagrant encountered an unexpected communications error with the So I installed Vagrant, the VMWare utilities, the provider and whatnot and could see something happening, but ultimately failing (resulting in this bug report). Unfortunately, Virtualbox does not run on Apple Silicon (the M1 Macbook), so I thought I was out of luck, until I read that VMWare has its own provider and they just (September) released a Tech Preview of Fusion that runs on Apple Silicon! After seeing the abysmal I/O performance of Docker up close on macOS I decided to give Vagrant a go.
0 Comments
Leave a Reply. |