- Package:
- vagrant-libvirt
- Source:
- vagrant-libvirt
- Submitter:
- Gabriel Filion
- Date:
- 2022-06-07 21:12:03 UTC
- Severity:
- important
Hello,
With the new version of vagrant-libvirt I'm unable to bring up a VM that uses a
private network. I'm getting an error about creating the network:
==> pc_bullseye: Removing domain...
==> pc_bullseye: Deleting the machine folder
Error occurred while creating new network: {:iface_type=>:private_network, :netmask=>"255.255.255.0", :dhcp_enabled=>true, :forward_mode=>"nat", :always_destroy=>true, :ip=>nil, :protocol=>"tcp", :id=>"ed52b838-7408-449a-911e-04c56d913b97"}.
I'm attaching the debug output for the "vagrant up" command that's producing
the error.
My user is part of the kvm and libvirt groups, so presumably it should have
access to contacting libvirt.
Also, just to make sure that it's not linked to another plugin I've removed all
plugins but vagrant-libvirt and tried again, and the same thing is happening.
Hrm... I think I might have sent the bug report too quickly. I tried downgrading to vagrant-libvirt 0.8.0 after sending the report and the problem did not go away (0.8.0 used to work for me). I first tried creating the networks manually in virt-manager, but that didn't help. Then I tried clearing out networks in virt-manager and removing the .vagrant cache directory in my vagrant project, but I'm still getting the issue, so vagrant is not able to recreate networks. So something else has changed in my local setup that causes this issue. I don't see a recent upgrade to vagrant itself in the dpkg log. However, I can see that a couple of libvirt-daemon-* packages were upgraded on june 3rd. I just tried to downgrade libvirt* packages to 8.4.0-1 but that did not fix the problem either. Now I'm not sure what more I could look into for this issue :(
Oohh .. I think I just found my issue, and it doesn't seem to be related to a bug in the software, but rather in my Vagrantfile. from what I can see the variable that's used as the IP address for the private network is not getting me the value that it should. so now I plunge into ruby debugging. I'll close this bug report since it's not linked to the package. sorry for the noise about this.