This trick does work to start the particular VM in question
in this particular use case of shared repo and cloning.
I think we didn't make this change in our ONE3.2 installation because
we had other reasons why we needed the qemu user to run KVM
in other transfer mode situations. Will have to look at all the
other use cases we have to make sure we don't break anything else.
Steve Timm
On Tue, 30 Dec 2014, Daniel Dehennin wrote:
Steven C Timm <t...@fnal.gov> writes:
[root@cloudworker1359 libvirt]# grep -v ^# qemu.conf | grep .
dynamic_ownership = 0
You must set “user” and “group” to “oneadmin” like described in the
documentation[1].
This way the qemu process run as oneadmin and has write access to the images.
Regards.
Footnotes:
[1]
http://docs.opennebula.org/4.10/design_and_installation/quick_starts/qs_ubuntu_kvm.html#configure-qemu
--
Daniel Dehennin
Récupérer ma clef GPG: gpg --recv-keys 0xCC1E9E5B7A6FE2DF
Fingerprint: 3E69 014E 5C23 50E8 9ED6 2AAD CC1E 9E5B 7A6F E2DF
------------------------------------------------------------------
Steven C. Timm, Ph.D (630) 840-8525
t...@fnal.gov http://home.fnal.gov/~timm/
Office: Wilson Hall room 804
Fermilab Scientific Computing Division,
Scientific Computing Facilities Quadrant.,
Experimental Computing Facilities Dept.,
Project Lead for Virtual Facility Project.
_______________________________________________
Users mailing list
Users@lists.opennebula.org
http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
