vagrant-qemu icon indicating copy to clipboard operation
vagrant-qemu copied to clipboard

Simplest configuration to run on AMD64 Mac with QEMU

Open torenware opened this issue 2 years ago • 5 comments

I'm having trouble getting the plugin to work on an Intel Mac (Big Sur); it appears that ARM64 is hard wired somewhere.

I've found that I can point to my homebrew installed copy of QEMU by doing:

  config.vm.provider "qemu" do |qe|
    #qe.machine = "virt,accel=hvf,highmem=off"
    #qe.cpu = "cortex-a72"
    qe.qemu_dir = "/usr/local/share/qemu"
  end

My sense is that I need to change qe.machine and q3.cpu to something else to work on AMD64, but what exactly?

torenware avatar Aug 04 '23 22:08 torenware

Please try the example "Work with a x86_64 box (basic config)" or "Force Multicore (x86)" in the readme.

ppggff avatar Aug 07 '23 03:08 ppggff

With the addition off the line qe.qemu_dir = "/usr/local/share/qemu", it comes up; arguably this needs to be added to the README.

Is it possible to create a bridge type network connection. I see the following message when I start up the virtual:

==> default: Warning! The QEMU provider doesn't support any of the Vagrant
==> default: high-level network configurations (`config.vm.network`). They
==> default: will be silently ignored.

torenware avatar Aug 07 '23 03:08 torenware

Bridge type network is not supported right now. See #40 for details.

ppggff avatar Aug 07 '23 03:08 ppggff

Thanks for your quick reply. I looked at #40. I know that the minikube people have recently made some progress using socket_vmnet. I'm not sure what they did, but they can bring up their virtual now using the socket_vmnet service that homebrew can bring up.

How compatible their solution would be in vagrant's source base, I have absolutely no idea.

torenware avatar Aug 07 '23 03:08 torenware

I've been looking into vmnet as well, so I'll hop into #40 . :)

unixerius avatar Feb 02 '24 09:02 unixerius