use libvirt system vs sessions to enable vm reboots and easier console access

[wes hayutin]

use libvirt system vs sessions to enable vm reboots and easier console access

I did not find any related user bugs on this topic, however the feedback from several folks at the ptg has been that using libvirt system with root privileges is actually preferred over user sessions.

Both work atm, however I'm looking for feedback with regards to the default.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/549268

[John Trowbridge (trown)]

I never had a super strong opinion on it. The main reason to use unprivileged libvirt is if you dont trust quickstart not to hose your system. Perhaps we have outgrown the need for that to be the default.

[Raoul Scarazzini (rasca)]

I'm for the root privileges mostly because every time I made a virsh list in the past that was not showing anything I needed to realize "Oh yes, you need to be stack!" :)
Jokes apart, I think that since quickstart's virthosts are created almost always from scratch the security reasons behind executing everything as user stack are less critical. Having everything managed by root, eliminating the limitations (VM reboots and console access), it's an improvement at zero cost.
So, for what it worths, +1 on the root side for me.

[Jason E. Rist (jason-rist)]

I guess I could go either way. I'm happy to see the priv mode passed in as an alternative.

[Dmitry Tantsur (divius)]

A big advantage of running it as root is that virt-manager (libvirt GUI) will work with such installations (it has some weird problems with libvirt running as non-root).

[OpenStack Infra (hudson-openstack)]

Change abandoned by wes hayutin (<email address hidden>) on branch: master
Review: https://review.openstack.org/549268