You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi @Fred78290, the macOS specifics are not open at the moment, so you could not succeed building. That is something we intend to finally change in the next few months though.
That said, at this point we are actually trying to reduce the number of drivers that we have. If we ever considered this, it would be to replace QEMU entirely, and it would have to be very good and offer clear advantages.
For our understanding, could you please explain a little the motivation behind your proposal? What benefits do you think this could bring?
@ricab Thank you for reply. Effectivly, I readed on discource.ubuntu.com that macos and windows code/build aren't public.
I understand that you don't want tons of driver to support but on MacOS X plateform you migrated from hyperkit to qemu but it still the same problem when a new Mac OS major release is available you need urge to fix problems on the new MacOS release.
For your information the project lima have included nested virtualization in the next release
So I think that replace QEMU on MacOS by VZ you will have less problem on new MacOS release.
to convince you of need of nested virtualization, google will be your friend by querying "nested virtualization macos" and finally Apple permit nested virtualization since M3 + MacOS 15
So It will be nice that MAcOS developers could build multipass on MacOS.
What are you trying to do?
Since MacOS 15 Apple silicon M3 support nested virtualization and more enhancements.
What's your proposed solution?
Replace QEMU by Apple VZ or add a new driver using VZ.
Additional context
As mac developer I can do it but I never successful build on Mac, maybe missing some tips.
The text was updated successfully, but these errors were encountered: