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

Asking for password during vagrant up #27

Open
jennydaman opened this issue Aug 9, 2023 · 1 comment
Open

Asking for password during vagrant up #27

jennydaman opened this issue Aug 9, 2023 · 1 comment

Comments

@jennydaman
Copy link

When I run vagrant up It asks me for a password:

==> default: Domain launching with graphics connection settings...
==> default:  -- Graphics Port:      5901
==> default:  -- Graphics IP:        127.0.0.1
==> default:  -- Graphics Password:  Not defined
==> default:  -- Graphics Websocket: 5701
==> default: Waiting for domain to get an IP address...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 192.168.121.88:22
    default: SSH username: clear
    default: SSH auth method: private key
Password:     default: Warning: Connection timeout. Retrying...
Password:     default: Warning: Connection timeout. Retrying...
Password:

I don't know what password to supply (neither do I want to give it a password).

Vagrantfile:

Vagrant.configure("2") do |config|
  config.vm.box = "AntonioMeireles/ClearLinux"

  config.vm.provider :libvirt do |libvirt|
    libvirt.memory = '4192'
    libvirt.cpus = '2'
    libvirt.machine_virtual_size = 60
  end

  # workaround for Arch Linux host
  config.vm.provider :libvirt do |libvirt, override|
    libvirt.loader = '/usr/share/edk2-ovmf/x64/OVMF.fd'
  end

  config.vm.synced_folder ".", "/vagrant", disabled: true
end

Vagrant version: 2.3.6

vagrant plugin list:

vagrant-guests-clearlinux (1.2.4, global)
vagrant-libvirt (0.12.2, global)
@AntonioMeireles
Copy link
Owner

Hi,

Thanks for reporting! Sorry for the lag! (was AFK on vacation)

AFAICT, this was due to a Vagrant issue that got fixed in vagrant-2.3.7.

So, can you upgrade Vagrant and confirm that the issue is gone?

Also, FWIW (from here) the default password of the default user (clear) is V@grant!.

Thanks again!

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

2 participants