ppggff / vagrant-qemu

Use Vagrant to manage machines using QEMU. Test with Apple Silicon / M1 and CentOS aarch64 image
MIT License
408 stars 32 forks source link

Use an incomplete Vagrantfile failed #44

Open Obasoro opened 1 year ago

Obasoro commented 1 year ago

I copied one of the vagrant config

the machine type is macos M1 chip...I have UTM installed and qemu.

# Basic Vagrant config (API version 2)
Vagrant.configure(2) do |config|
  # ... other stuff

  config.vm.provider "qemu" do |qe|
    qe.memory = "8G"
  end
end

After running vagrant up I get the below error

The box you're using with the QEMU provider ('default')
is invalid.

Error: Invalid box image path:
ppggff commented 1 year ago

Sorry, this configuration is incomplete and is only used to illustrate the usage of the plugin parameters. (I will try to complete all the examples later)

Please try

vagrant init ppggff/centos-7-aarch64-2009-4K
vagrant up --provider qemu

to run a centos vm.

Obasoro commented 1 year ago

Thanks for the reply

Vagrant SMB synced folders require the account password to be stored
in an NT compatible format. Please update your sharing settings to
enable a Windows compatible password and try again.

I got the above error.

What is the username and password for the vm?

ppggff commented 1 year ago

The username and password is required by vagrant for shared folder, from readme:

may need password to setup SMB on Mac, see vagrant doc for details need username/password to access shared folder

Obasoro commented 1 year ago

Thanks for sharing the documents. When working with Virtual Box and I use Vagrant to spin web, db, and backend servers, but finding it difficult using qemu/UTM...I can't see the server coming up on UTM

unixerius commented 5 months ago

When working with Virtual Box and I use Vagrant to spin web, db, and backend servers, but finding it difficult using qemu/UTM...I can't see the server coming up on UTM

That is because Vagrant does not control UTM. Vagrant is talking directly to Qemu.

If you're coming from VirtualBox I understand why this is confusing. With VirtualBox, Vagrant does the configuration and operations through VirtualBox. But the plugin you're using now is not a UTM-controller, it controls Qemu.

It would be lovely if UTM were adjusted to automatically detect new VMs on Qemu. But that's outside the scope of this project.

On the other hand there are multiple requests to both the Vagrant team and the UTM team to create a Vagrant plugin for UTM. You will find those discussions if you search for "vagrant" "utm" on Google.

@ppggff feel free to close this issue. :)

darkn3rd commented 1 month ago

Could we change the title of this issue?!?