Hello,
jstanek pinged me today with some weird errors :) so I got tempted to ask:
Is anyone else experiencing some Vagrant-related issues?
Most probable cause:
- there was a Change, in which `qemu://session` (user session) is used by default. That
means root privilleges are not required anymore for vagrant+libvirt
But:
- some network settings are currently limited (f.e. IP change)
- the location of the VM images, even the base one, was moved to home directory
(`~/.local/share/libvirt/images/` instead of `/var/lib/libvirt/images`)
- flipping the option back to `qemu://system` disrupts halted machines (no images-moving
magic is there)
If you wan't just the IP of the machine, you can simply `vagrant ssh-config`.
If you really need to use some custom networking setup (or need to access your existing
box), you can change the libvirt provider's option `qemu_use_session`.
- To change it for one guest, you need to add to your Vagrantfile (where it fits):
```
config.vm.provider :libvirt do |libvirt|
libvirt.qemu_use_session = false
end
```
- To change it for all user's instances, you can add the setting above to
`~/.vagrant.d/Vagrantfile` (or create the file). Then you can set it back to `true` on
per-guest basis as needed.
Note:
- prior to flipping the setting, `destroy` the instance(s) it affects (`vagrant
global-status`)
- to remove base image from libvirt storage, use always:
`sudo virsh vol-list --pool default`
to list images and
`sudo virsh vol-delete --pool default
fedora-VAGRANTSLASH-29-cloud-base_vagrant_box_image_29.20181024.1.img`
or similar to remove them (without `sudo` for `qemu://session`).
You can read more on the change here:
https://fedoraproject.org/wiki/Changes/Vagrant_2.2_with_QEMU_Session
If you encounter any issues, please ping me (pvalena on #fedora-devel) or create a bug
(
http://bugzilla.redhat.com/).
Cheers,
Pavel