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
Describe the issue
I couldn't locate the root password, and after using single-user mode to change the root password, which indicated success, I rebooted and attempted to log in: it returned an error.
A clear and concise description of what the issue is.
Explain what commands you ran, what you expected to happen and what actually happened.
Environment (please complete the following information):
Host OS: [e.g. Oracle Linux 8, macOS 10.14.6, Windows 10 Pro, ...]
Kernel version (for Linux host): [run uname -a]
Vagrant version: [e.g. 2.2.9]
Vagrant provider:
For VirtualBox:
VirtualBox version: [e.g. 6.1.8r137981 -- run vboxmanage -v]
For libvirt:
Vagrant-libvirt plugin version: [e.g. 0.1.2 -- run vagrant plugin list]
QEMU and libvirt version:
If you have virsh installed run virsh -c qemu:///system version --daemon
Alternatively query your package manager with e.g. rpm -q qemu-kvm libvirt, dpkg -l qemu-kvm libvirt\* | grep ^ii, ...
Root account is locked on all vagrant boxes.
After login with the vagrant user (with vagrant ssh) you can use sudo to get root privileges and set a password from there if required.
Describe the issue
I couldn't locate the root password, and after using single-user mode to change the root password, which indicated success, I rebooted and attempted to log in: it returned an error.
A clear and concise description of what the issue is.
Explain what commands you ran, what you expected to happen and what actually happened.
Environment (please complete the following information):
uname -a
]vboxmanage -v
]vagrant plugin list
]If you have
virsh
installed runvirsh -c qemu:///system version --daemon
Alternatively query your package manager with e.g.
rpm -q qemu-kvm libvirt
,dpkg -l qemu-kvm libvirt\* | grep ^ii
, ...Additional information
Add any other information about the issue here (console log, ...).
The text was updated successfully, but these errors were encountered: