On Wed, Jul 22, 2009 at 10:33:19AM -0400, Juan Miscaro wrote: Options 1, 3 & 4 pretty much all say that you should just have each user using 'qemu:///session' URIs. This casues a 'libvirtd' process to be spawned for each user, and are completely indepedant accessible only to that user, though with a suitable libvirtd.conf they could allow read-only access to other users The only trouble is that they can't then use bridging :-( Only the privileged qemu://system instance allows use of bridging and we don't yet have fine grained access control on that, so anyone accessing it can use any VM present. So we don't really have a perfect solution for you that meets all these requirements. Daniel -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|