Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

LIBVIRT_URI not being used, hardcoded `qemu:///system` instead.

See original GitHub issue

Libvirt uri seems to be hardcoded and not being readed from the sourced env var at /var/lib/one/remotes/etc/vmm/kvm/kvmrc : export LIBVIRT_URI=qemu+tcp://localhost/system

this is not working then. http://docs.opennebula.org/5.8/deployment/open_cloud_host_setup/kvm_driver.html#opennebula-configuration

https://github.com/OpenNebula/one/blob/def9661b4aa7c708d51679eb051ce8bebce09d80/src/im_mad/remotes/kvm-probes.d/machines-models.rb#L33

https://github.com/OpenNebula/one/blob/def9661b4aa7c708d51679eb051ce8bebce09d80/src/im_mad/remotes/kvm-probes.d/machines-models.rb#L92

https://github.com/OpenNebula/one/blob/441cf1f7f9e726cb5f200d661d50e92a4042fff7/src/im_mad/remotes/kvm-probes.d/kvm.rb#L32

Progress Status

Branch created
Code committed to development branch
Testing - QA
Documentation
Release notes - resolved issues, compatibility, known issues
Code committed to upstream release/hotfix branches
Documentation committed to upstream release/hotfix branches

Issue Analytics

State:
Created 4 years ago
Comments:5 (5 by maintainers)

Top GitHub Comments

4reactions

astevencommented, Sep 26, 2019

FTR: I’m working on a PR. Seems to work so far, but want to test some more before submitting it.

0reactions

astevencommented, Dec 6, 2019

Then call the script one-virsh or whatever. Why would you want to depend on a env variable that is defined in some shell script/rc file in one mad from all others. And read/parse that variable from every script/shell/ruby/executable again and again.

Anyway. Upstream does not seem to be interested. I’m not working on this. Feel free to PR with your preferred solution.