Skip to content
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

Use an incomplete Vagrantfile failed #44

Open
Obasoro opened this issue Jun 15, 2023 · 6 comments
Open

Use an incomplete Vagrantfile failed #44

Obasoro opened this issue Jun 15, 2023 · 6 comments

Comments

@Obasoro
Copy link

Obasoro commented Jun 15, 2023

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
Copy link
Owner

ppggff commented Jun 16, 2023

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
Copy link
Author

Obasoro commented Jun 16, 2023

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
Copy link
Owner

ppggff commented Jun 19, 2023

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
Copy link
Author

Obasoro commented Jun 22, 2023

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
Copy link

unixerius commented Feb 2, 2024

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
Copy link

Could we change the title of this issue?!?

@ppggff ppggff changed the title I Use an incomplete Vagrantfile failed May 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants