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

[Eric Blake]

On 01/18/2012 12:38 AM, Taku Izumi wrote:
>> 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.
> 
>    I see.
>    You say if a guest has the following XML configuration,
>    "CAP_SYS_RAWIO" capability is automatically added to it, right?
>   
>      <disk type='block' device='lun'>

Yes, that actually seems reasonable, especially since device='lun' is
brand new, and so far, is really the only reason that we'd need
CAP_SYS_RAWIO.

-- 
Eric Blake   eblake at redhat.com    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 620 bytes
Desc: OpenPGP digital signature
URL: <http://listman.redhat.com/archives/libvir-list/attachments/20120119/494d50e6/attachment-0001.sig>