Open prologic opened 5 years ago
According to this (rather random unrelated find) unrelated issue it might be that libvirt
isn't compiled with --with-virt-network
-- So I'm giving that a go to see if that helps.
Re-installed the provider and added --with-virt-network
to libvirt and built form source.
$ terraform-provider-libvirt --version
terraform-provider-libvirt fc4f30356f23f52f8a5766abea327e61d90e08e3-dirty
Compiled against library: libvirt 5.7.0
Using library: libvirt 5.7.0
Running hypervisor: QEMU 4.1.0
Running against daemon: 5.7.0
Probably helpful to know that virsh -V
only reports "Remote Bridging" as a supported networking driver:
$ virsh -V
Virsh command line tool of libvirt 5.7.0
See web site at https://libvirt.org/
Compiled with support for:
Hypervisors: QEMU/KVM VMware VirtualBox ESX Test
Networking: Remote Bridging
Storage: Dir
Miscellaneous: Daemon Secrets Debug
I'm having the exact same issue, some relevant things:
Output of virsh -V
:
Virsh command line tool of libvirt 5.7.0
See web site at https://libvirt.org/
Compiled with support for:
Hypervisors: QEMU/KVM VMware VirtualBox ESX Test
Networking: Remote Bridging
Storage: Dir
Miscellaneous: Daemon Secrets Debug
Output of ll /Users/stevejobs/.cache/libvirt/
:
total 0
drwx------ 2 stevejobs staff 64B 30 Sep 17:30 hostdevmgr
drwxr-xr-x 5 stevejobs staff 160B 30 Sep 19:09 qemu
drwx------ 3 stevejobs staff 96B 30 Sep 17:30 secrets
drwxr-xr-x 3 stevejobs staff 96B 30 Sep 17:30 storage
srwx------ 1 stevejobs staff 0B 1 Oct 17:16 virtlogd-admin-sock
srwx------ 1 stevejobs staff 0B 1 Oct 17:16 virtlogd-sock
No virtnetworkd-sock
file.
I have encountered the same issue. After some digging, I found that there is a description in libvirt configure .ac
dnl Make some notes about which OS we're compiling for, as the lxc and qemu
dnl drivers require linux headers, and storage_mpath, dtrace, and nwfilter
dnl are also linux specific. The "network" and storage_fs drivers are known
dnl to not work on macOS presently, so we also make a note if compiling
dnl for that
Hi, does this still happen with latest version?
System Information
Linux distribution
N/A
I am running macOS Mojave 10.14.5 along with Homebrew
Terraform version
Provider and libvirt versions
If that gives you "was not built correctly", get the Git commit hash from your local provider repository:
Checklist
[ ] Is your issue/contribution related with enabling some setting/option exposed by libvirt that the plugin does not yet support, or requires changing/extending the provider terraform schema?
[ ] Is it a bug or something that does not work as expected? Please make sure you fill the version information below:
Description of Issue/Question
Setup
I am following this blog post and adapting it to my enviornment (macOS + libvirt).
Here are my files as they are laid out in
~/tmp/terraform
:cloud_init.cfg
:main.tf
:network_config.cfg
:NB: When initially installing
libvirt
withbrew install libvirt
I had to also create a volume to store images. The Brew formula for libvirt on macOS doesn't create any volumes by default.images-pool.xml
:Steps to Reproduce Issue
images
volume:terraform init
terraform apply
:After some time creating the cloudinit images you get the following error:
Additional information:
Do you have SELinux or Apparmor/Firewall enabled? Some special configuration? Have you tried to reproduce the issue without them enabled?
No, no and no.