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
german@german-HP-ProDesk:~/vagrant/nop$ vagrant sandbox on
Error while connecting to libvirt: Error making a connection to libvirt URI qemu://localhost/system?no_verify=1&keyfile=/home/german/.ssh/id_rsa:
Call to virConnectOpen failed: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
Only if I set :
config.vm.provider :libvirt do |libvirt|
libvirt.driver = "kvm"
libvirt.host = ''
config.vm.provider :libvirt do |libvirt|
libvirt.driver = "kvm"
libvirt.uri = "qemu:///system"
german@german-HP-ProDesk:~/vagrant/nop$ vagrant sandbox on
Error while connecting to libvirt: Error making a connection to libvirt URI qemu://localhost/system?no_verify=1&keyfile=/home/german/.ssh/id_rsa:
Call to virConnectOpen failed: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
The text was updated successfully, but these errors were encountered:
german@german-HP-ProDesk:~/vagrant/nop$ vagrant sandbox on
Error while connecting to libvirt: Error making a connection to libvirt URI qemu://localhost/system?no_verify=1&keyfile=/home/german/.ssh/id_rsa:
Call to virConnectOpen failed: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
Only if I set :
in Vagrantfile ,it works for me.
Perhaps it's worth adding the ** uri ** option from the vagrant-libvirt provider for an accurate definition :
libvirt https://github.com/vagrant-libvirt/vagrant-libvirt#provider-options
Now the option has no effect :
german@german-HP-ProDesk:~/vagrant/nop$ vagrant sandbox on
Error while connecting to libvirt: Error making a connection to libvirt URI qemu://localhost/system?no_verify=1&keyfile=/home/german/.ssh/id_rsa:
Call to virConnectOpen failed: Cannot read CA certificate '/etc/pki/CA/cacert.pem': No such file or directory
The text was updated successfully, but these errors were encountered: