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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxx    +1-919-301-3266
Libvirt virtualization library http://libvirt.org

Attachment: signature.asc
Description: OpenPGP digital signature

--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list

[Index of Archives]     [Virt Tools]     [Libvirt Users]     [Lib OS Info]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]     [Fedora Tools]