Re: [libvirt] [PATCH v3 0/5] RFC: grant KVM guests retain arbitrary capabilities

On Thu, Jan 12, 2012 at 04:25:27PM +0900, Taku Izumi wrote: Can you give me a little more detail on why you need to make KVM keep certain capabilities. In your first message you mention that you need to have 'rawio' for QEMU ? I am now wondering if we should do this in a different way. ie if there is some XML configuration parameter for the <disk> that indicates the need for rawio, then libvirt could automatically ensures that we add CAP_SYS_RAWIO when starting QEMU. Likewise with type=ethernet, we could probably give QEMU the CAP_SYS_NETADMIN capability. To me this feels nicer directly exposing capabilities in the XML, since these are really an internal impl detail, not a guest configuration thing. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|